From: "Theodore Ts'o" <tytso@mit.edu>
To: linux-ext4@vger.kernel.org
Subject: Rare xfsqa test failure
Date: Tue, 18 Aug 2009 07:57:42 -0400 [thread overview]
Message-ID: <E1MdNJu-0006uc-GX@closure.thunk.org> (raw)
As a heads up, I'm seeing a rare xfsqa test failure with the stable
portion of the ext4 patch queue; it doesn't hit all the time, but when
it does, i_size is corrupted:
Inode 22047, i_size is 922788, should be 942080. Fix?
922788/4096 is 225 plus a fraction, while 942080/4096 is 230. The
debugfs information is as follows:
debugfs: stat <22047>
Inode: 22047 Type: regular Mode: 0666 Flags: 0x80000
Generation: 3536075281 Version: 0x00000000:00000001
User: 0 Group: 0 Size: 922788
File ACL: 0 Directory ACL: 0
Links: 1 Blockcount: 1320
Fragment: Address: 0 Number: 0 Size: 0
ctime: 0x4a8a953b:546bc3d4 -- Tue Aug 18 07:49:15 2009
atime: 0x4a8a953b:29927210 -- Tue Aug 18 07:49:15 2009
mtime: 0x4a8a953b:546bc3d4 -- Tue Aug 18 07:49:15 2009
crtime: 0x4a8a951c:5ac789dc -- Tue Aug 18 07:48:44 2009
Size of extra inode fields: 28
EXTENTS:
(65-80): 60720-60735, (81-222 [uninit]): 1181574-1181715, (223-229): 1181716-118
1722
debugfs:
So it looks like there's a race which can cause ext4 to somehow miss an
i_size update.
- Ted
next reply other threads:[~2009-08-18 11:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-18 11:57 Theodore Ts'o [this message]
2009-08-18 14:56 ` Rare xfsqa test failure Theodore Tso
2009-08-18 17:07 ` Andreas Dilger
2009-08-18 21:42 ` Theodore Tso
2009-08-19 15:28 ` Eric Sandeen
2009-08-19 16:40 ` Christoph Hellwig
2009-08-19 16:51 ` Eric Sandeen
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=E1MdNJu-0006uc-GX@closure.thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).