From: David Chinner <dgc@sgi.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: David Chinner <dgc@sgi.com>,
Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
xfs-masters@oss.sgi.com
Subject: Re: [2/3] 2.6.22-rc1: known regressions v2 - XFS
Date: Thu, 17 May 2007 09:57:31 +1000 [thread overview]
Message-ID: <20070516235731.GR85884050@sgi.com> (raw)
In-Reply-To: <464B9664.2040200@goop.org>
On Wed, May 16, 2007 at 04:40:20PM -0700, Jeremy Fitzhardinge wrote:
> David Chinner wrote:
> > Jeremy has tentatively indicated that the patch has fixed the problem.
> > Have you seen any more problems since applying the patch, Jeremy?
> >
>
> No, it continues to seem sound with casual use; I would have expected to
> see the problem reoccur by now. I'd like to rerun the full set of tests
> I did before to be sure, but so far so good. No other apparent
> regressions either.
Good to here. I think the problem is fixed, then.
> Also, the match between the observed symptoms and the bugfix is very
> good, which adds confidence (ie, no element of "it works now but we
> don't know why"). I guess the only remaining concern is whether there
> are any other paths which fail to dirty the inode.
There aren't any that I can see - if more come up we'll deal with
them then.
> Did you manage to repro the problem?
xfs_io is my friend ;)
Without patch:
# touch /mnt/scratch/fred
# xfs_io -c "pwrite 0 5" -c "s" -c "pwrite 5 5" /mnt/scratch/fred
wrote 5/5 bytes at offset 0
5.000000 bytes, 1 ops; 0.0000 sec (78.755 KiB/sec and 16129.0323 ops/sec)
wrote 5/5 bytes at offset 5
5.000000 bytes, 1 ops; 0.0000 sec (542.535 KiB/sec and 111111.1111 ops/sec)
# umount /mnt/scratch; mount /mnt/scratch; ls -l /mnt/scratch/fred
-rw-r--r-- 1 root root 5 May 17 10:04 fred
#
So the second 5 byte write didn't change the file size.
With patch:
# touch /mnt/scratch/fred
# xfs_io -c "pwrite 0 5" -c "s" -c "pwrite 5 5" /mnt/scratch/fred
wrote 5/5 bytes at offset 0
5.000000 bytes, 1 ops; 0.0000 sec (76 KiB/sec and 15625.0000 ops/sec)
wrote 5/5 bytes at offset 5
5.000000 bytes, 1 ops; 0.0000 sec (610 KiB/sec and 125000.0000 ops/sec)
# umount /mnt/scratch; mount /mnt/scratch; ls -l /mnt/scratch/fred
-rw-r--r-- 1 root root 10 May 17 09:53 fred
#
So yes, I've reproduced it and confirmed the patch fixes the problem.
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
next prev parent reply other threads:[~2007-05-16 23:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <464B6743.9000607@googlemail.com>
2007-05-16 20:31 ` [2/3] 2.6.22-rc1: known regressions v2 Michal Piotrowski
2007-05-16 20:33 ` Christoph Lameter
2007-05-16 20:44 ` Linus Torvalds
2007-05-16 23:34 ` [2/3] 2.6.22-rc1: known regressions v2 - XFS David Chinner
2007-05-16 23:40 ` Jeremy Fitzhardinge
2007-05-16 23:57 ` David Chinner [this message]
[not found] ` <464B6895.60806@googlemail.com>
2007-05-16 20:31 ` [3/3] 2.6.22-rc1: known regressions v2 Michal Piotrowski
2007-05-16 20:39 ` Mauro Carvalho Chehab
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=20070516235731.GR85884050@sgi.com \
--to=dgc@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=xfs-masters@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
Powered by JetHome