xfs
[Top] [All Lists]

Re: 2.6.21-git10/11: files getting truncated on xfs? or maybe an nlink p

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: Re: 2.6.21-git10/11: files getting truncated on xfs? or maybe an nlink problem?
From: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>
Date: Sat, 12 May 2007 13:23:27 +0200 (MEST)
Cc: Chuck Ebbert <cebbert@xxxxxxxxxx>, David Chinner <dgc@xxxxxxx>, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, Matt Mackall <mpm@xxxxxxxxxxx>, xfs@xxxxxxxxxxx
In-reply-to: <46439491.9010604@xxxxxxxx>
References: <4642389E.4080804@xxxxxxxx> <20070509231643.GM85884050@xxxxxxx> <4642598E.3000607@xxxxxxxx> <20070510000119.GO85884050@xxxxxxx> <46426194.3040403@xxxxxxxx> <46439185.5060207@xxxxxxxxxx> <464392B4.3070009@xxxxxxxx> <464393E1.3050705@xxxxxxxxxx> <46439491.9010604@xxxxxxxx>
Sender: xfs-bounce@xxxxxxxxxxx
On May 10 2007 14:54, Jeremy Fitzhardinge wrote:
>>>> What CPU architecture is this happening on? Not i686 with PAE by
>>>> any chance?
>>>>       
>>> Yes.  Why?
>>
>> I have a bug report where NFS files are corrupted only with PAE clients.
>> Corruption is at the end of the (newly untarred) files. Doesn't happen
>> without PAE.
>
>Hm, suggestive, but I'm not convinced.  Two differences to this situation:
>
>   1. Immediately after the clone ("untar"), the contents are completely
>      OK; it's only after a umount/mount cycle to problems appear

And if you do a "sync" rather than umount/mount?

>   2. There's no corruption as such; the files are just too short.  And
>      it seems they're at a previously OK length, not some random size.


        Jan
-- 


<Prev in Thread] Current Thread [Next in Thread>