From: Dave Chinner <david@fromorbit.com>
To: Lachlan McIlroy <lachlan@sgi.com>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH] Don't reset di_format in xfs_ifree()
Date: Fri, 13 Feb 2009 09:32:53 +1100 [thread overview]
Message-ID: <20090212223253.GV8830@disturbed> (raw)
In-Reply-To: <49937458.2000500@sgi.com>
On Thu, Feb 12, 2009 at 11:59:04AM +1100, Lachlan McIlroy wrote:
> Dave Chinner wrote:
>> On Wed, Feb 11, 2009 at 11:26:38AM +1100, Lachlan McIlroy wrote:
>>> I hit a panic while flushing a reclaimed inode that is fairly
>>> reproducible under load.
>>>
>>> In xfs_iflush_fork() we're led to believe that there are extents
>>> on this inode but there aren't any. Actually the inode was a
>>> directory. I added some debugging to xfs_ifree() and found
>>> that di_format was XFS_DINODE_FMT_LOCAL and got reset to
>>> XFS_DINODE_FMT_EXTENTS and this has confused the code in
>>> xfs_iflush_fork().
....
>> I think the problem may be that the size of the fork has not been
>> reset to zero, not that format has been changed. If it was in local
>> format, the truncates prior to freeing would not have done anything
>> and the size of the data/attr fork would still be non-zero. Hence
>> if the fork is then changed to extent format, xfs_iextents_copy()
>> will be triggered from xfs_iflush_fork() and you'd see something
>> like the confusion you are seeing.
>>
>> Hence I think we should be ensuring the fork size is set to zero for
>> both the attr/data fork when the format is changed, not removing
>> the change of type....
>
> Yes, I agree. I just don't have the time to hunt it down. I see
> there's a call to xfs_idestroy_fork() in xfs_ireclaim() for directories
> but xfs_ireclaim() gets called after xfs_iflush() in xfs_reclaim_inode().
I suspect it should be in xfs_inactive() if we are in local format.
This is what happens with the attribute fork. I think that is where
we need something like:
if ((ip->i_d.di_mode & S_IFMT) == S_IFDIR &&
ip->i_d.di_nextents == 0)
xfs_idestroy_fork(ip, XFS_DATA_FORK);
> Might also need something like:
>
> @@ -2445,6 +2447,7 @@ xfs_idestroy_fork(
> kmem_free(ifp->if_u1.if_data);
> ifp->if_u1.if_data = NULL;
> ifp->if_real_bytes = 0;
> + ifp->if_bytes = 0;
> }
> } else if ((ifp->if_flags & XFS_IFEXTENTS) &&
> ((ifp->if_flags & XFS_IFEXTIREC) ||
Looking at that, the whole if (local) {} else if (extent/btree)
code could probably be replaced with a single call to
xfs_iext_destroy() as it does the cleanup correctly in both cases,
anyway....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-02-12 22:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 0:26 [PATCH] Don't reset di_format in xfs_ifree() Lachlan McIlroy
2009-02-11 2:21 ` Eric Sandeen
2009-02-11 3:13 ` Lachlan McIlroy
2009-02-11 3:10 ` Eric Sandeen
2009-02-11 3:48 ` Felix Blyakher
2009-02-11 4:15 ` Lachlan McIlroy
2009-02-11 9:20 ` Dave Chinner
2009-02-12 0:59 ` Lachlan McIlroy
2009-02-12 22:32 ` Dave Chinner [this message]
2009-02-15 19:25 ` Christoph Hellwig
2009-02-17 3:03 ` Dave 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=20090212223253.GV8830@disturbed \
--to=david@fromorbit.com \
--cc=lachlan@sgi.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