From: Matt Mackall <mpm@selenic.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
David Chinner <dgc@sgi.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
xfs@oss.sgi.com, michal.k.k.piotrowski@gmail.com
Subject: Re: 2.6.21-git10/11: files getting truncated on xfs? or maybe an nlink problem?
Date: Sat, 12 May 2007 07:46:41 -0500 [thread overview]
Message-ID: <20070512124641.GZ11115@waste.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0705121320240.9570@yvahk01.tjqt.qr>
On Sat, May 12, 2007 at 01:21:41PM +0200, Jan Engelhardt wrote:
>
> 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().
There is no assumption. Mercurial explicitly visits files in
alphabetical order for the above commands.
--
Mathematics is the supreme nostalgia of our time.
next prev parent reply other threads:[~2007-05-12 12:47 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-09 21:09 2.6.21-git10/11: files getting truncated on xfs? or maybe an nlink problem? Jeremy Fitzhardinge
2007-05-09 21:55 ` Matt Mackall
2007-05-09 22:17 ` Jeremy Fitzhardinge
2007-05-09 22:44 ` Matt Mackall
2007-05-09 22:50 ` Jeremy Fitzhardinge
2007-05-09 23:16 ` David Chinner
2007-05-09 23:30 ` Jeremy Fitzhardinge
2007-05-10 0:01 ` David Chinner
2007-05-10 0:04 ` Jeremy Fitzhardinge
2007-05-10 0:49 ` David Chinner
2007-05-10 0:54 ` Jeremy Fitzhardinge
2007-05-10 1:26 ` David Chinner
[not found] ` <46433049.4020003@goop.org>
2007-05-10 15:38 ` Matt Mackall
2007-05-12 11:21 ` Jan Engelhardt
2007-05-12 12:46 ` Matt Mackall [this message]
2007-05-14 20:16 ` Jan Engelhardt
2007-05-14 20:27 ` Jeremy Fitzhardinge
2007-05-10 21:13 ` David Chinner
2007-05-10 21:23 ` Matt Mackall
2007-05-10 21:32 ` Jeremy Fitzhardinge
2007-05-10 21:49 ` Jeremy Fitzhardinge
2007-05-10 21:41 ` Chuck Ebbert
2007-05-10 21:46 ` Jeremy Fitzhardinge
2007-05-10 21:51 ` Chuck Ebbert
2007-05-10 21:54 ` Jeremy Fitzhardinge
2007-05-10 22:58 ` David Chinner
2007-05-10 23:07 ` Jeremy Fitzhardinge
2007-05-10 23:27 ` David Chinner
2007-05-10 23:49 ` Jeremy Fitzhardinge
2007-05-11 0:32 ` David Chinner
2007-05-11 14:48 ` Jeremy Fitzhardinge
2007-05-12 7:56 ` David Chinner
2007-05-12 11:23 ` Jan Engelhardt
2007-05-12 13:51 ` David Chinner
2007-05-12 14:56 ` Jeremy Fitzhardinge
2007-05-15 0:14 ` David Chinner
2007-05-15 19:24 ` Jeremy Fitzhardinge
2007-05-10 23:07 ` David Chinner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070512124641.GZ11115@waste.org \
--to=mpm@selenic.com \
--cc=dgc@sgi.com \
--cc=jengelh@linux01.gwdg.de \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox