xfs
[Top] [All Lists]

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

To: Matt Mackall <mpm@xxxxxxxxxxx>
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:21:41 +0200 (MEST)
Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, David Chinner <dgc@xxxxxxx>, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, xfs@xxxxxxxxxxx, michal.k.k.piotrowski@xxxxxxxxx
In-reply-to: <20070510153832.GQ11115@xxxxxxxxx>
References: <4642389E.4080804@xxxxxxxx> <20070509231643.GM85884050@xxxxxxx> <4642598E.3000607@xxxxxxxx> <20070510000119.GO85884050@xxxxxxx> <46426194.3040403@xxxxxxxx> <20070510004918.GS85884050@xxxxxxx> <46426D31.8070000@xxxxxxxx> <20070510012609.GU85884050@xxxxxxx> <46433049.4020003@xxxxxxxx> <20070510153832.GQ11115@xxxxxxxxx>
Sender: xfs-bounce@xxxxxxxxxxx
On May 10 2007 10:38, Matt Mackall wrote:
>> 
>>     for i in `seq 20`; do
>>      hg clone -U --pull a b-$i
>>      hg verify b-$i          # always OK
>>      umount /home
>>      sleep 5
>>      mount /home
>>      hg verify b-$i          # often found truncated files
>>     done
>>       
[...]
>
>This test looks like it should consist solely of open-for-append and
>write on about 20k files in the target directory. Because of the
>--pull, no hardlinks are involved. It shouldn't be all that different
>from doing tar cf - a | tar xf - b.
>
>The files get visited in alphabetical order, so the start of the
>corruption may be telling.

You should not assume alphabetical order. Filesystems may be free to
reorder things and return them (1) randomly like in a hash (2) by
creation time during readdir().


        Jan
-- 


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