From: Dave Chinner <david@fromorbit.com>
To: Mark Goodwin <markgw@sgi.com>
Cc: xfs@oss.sgi.com, kevin@kevinjamieson.com
Subject: Re: [PATCH] XFS: Account for allocated blocks when expanding directories
Date: Tue, 30 Sep 2008 12:09:34 +1000 [thread overview]
Message-ID: <20080930020934.GC16064@disturbed> (raw)
In-Reply-To: <48E184E0.4020301@sgi.com>
On Tue, Sep 30, 2008 at 11:46:08AM +1000, Mark Goodwin wrote:
> Hi Dave,
>
> by the looks of it, this is a proposed fix for the bug reported
> by Kevin Jamieson (and others in the past) :
>
> "xfs_trans_cancel at line 1138 of file fs/xfs/xfs_trans.c"
Yes, it's the main fix needed.
> Do you (or Kevin or anyone) have a reliable test case to reproduce
> this?
Sure - the metadump image that Kevin sent us a pointer to reproduces
it precisely. i.e:
# echo 255 > /proc/sys/fs/xfs/panic_mask
# mount /dev/ubd/5 /mnt/xfs
# cd /mnt/xfs/*/nerd/run1/*5st1\-
# touch aaaaaaaa
<shutdown>
With the patch I posted, it doesn't shut down any more and the
create succeeds. The patch has passed through xfsqa a couple of
times now....
Of the list of things I posted after analysing the problem,
this patch addresses item 1, via the indirect method noted in
item 2, and I've covered all the expansion cases (I think) in the
directory code (item 3).
Item 4 and 5 are less critical given that I don't think they can
cause shutdowns now that the directory reserved block accounting
is correct.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2008-09-30 2:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-30 1:25 [PATCH] XFS: Account for allocated blocks when expanding directories Dave Chinner
2008-09-30 1:46 ` Mark Goodwin
2008-09-30 2:09 ` Dave Chinner [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-10-07 21:58 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=20080930020934.GC16064@disturbed \
--to=david@fromorbit.com \
--cc=kevin@kevinjamieson.com \
--cc=markgw@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