linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Theodore Tso <tytso@mit.edu>
Cc: Andreas Dilger <adilger@sun.com>, linux-ext4@vger.kernel.org
Subject: Re: Rare xfsqa test failure
Date: Wed, 19 Aug 2009 10:28:04 -0500	[thread overview]
Message-ID: <4A8C1A04.1090501@redhat.com> (raw)
In-Reply-To: <20090818214218.GK28560@mit.edu>

Theodore Tso wrote:
> On Tue, Aug 18, 2009 at 11:07:05AM -0600, Andreas Dilger wrote:
>>> 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.
>> Are you sure it is a failure to update i_size, or is it possibly an
>> fallocate that extends the block count beyond i_size?
> 
> Look at the EXTENTS report from debugfs; blocks 81-222 are
> uninitialized from an fallocate, but block 223-229 are initialized.
> 
> 	      	      		     	   - Ted

This was from test 013?

If so, that calls ltp's fsstress, which does not call fallocate nor
posix_fallocate.  It only does preallocation on xfs via the old
xfs-specific ioctl (though I suppose we should add it...)

-Eric

  reply	other threads:[~2009-08-19 15:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-18 11:57 Rare xfsqa test failure Theodore Ts'o
2009-08-18 14:56 ` Theodore Tso
2009-08-18 17:07 ` Andreas Dilger
2009-08-18 21:42   ` Theodore Tso
2009-08-19 15:28     ` Eric Sandeen [this message]
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=4A8C1A04.1090501@redhat.com \
    --to=sandeen@redhat.com \
    --cc=adilger@sun.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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).