From: Christoph Hellwig <hch@infradead.org>
To: Kamal Dasu <kdasu.kdev@gmail.com>
Cc: cernekee@gmail.com, xfs@oss.sgi.com
Subject: Re: Inode lockdep problem observed on 2.6.37.6 xfs with RT subvolume
Date: Thu, 2 Feb 2012 04:13:30 -0500 [thread overview]
Message-ID: <20120202091330.GA31203@infradead.org> (raw)
In-Reply-To: <CAC=U0a1huHVULfMObyH_XNcQi5aTZtrbpcciNhw=92PE96f4cg@mail.gmail.com>
On Wed, Feb 01, 2012 at 07:44:13PM -0500, Kamal Dasu wrote:
> Need some help understanding the state of xfs with rt subvolume
> support on 2.6.37.
>
> When using xfs rt subvolume on a harddisk partition with kernel
> 2.6.37.6,and normal r/w/delete file operations? causes deadlock
> like hangs .? Failure? symptoms are lockups and mount failure on reboot.
>
> On further investigation it was found that one of the changes could be
> the cause.
> The same tests seem to pass with xfs in 2.6.31 kernel.
>
> xfs: simplify xfs_trans_iget? : aa72a5cf00001d0b952c7c755be404b9118ceb2e
> http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=commitdiff;h=aa72a5cf00001d0b952c7c755be404b9118ceb2e
>
> Reverting the change and forward porting to the xfs_trans_inode() seems to
> get rid of the deadlock and mount issues .
>
> Below is the change
Please just upgrade to Linux 2.6.39 or better Linux 3.0 which is the
long term support release. RT subvolume support has been fixed in 2.6.39
by the following changes:
xfs: only lock the rt bitmap inode once per allocation
xfs: fix xfs_get_extsz_hint for a zero extent size hint
xfs: add lockdep annotations for the rt inodes
But in general the RT subvolume code is not regularly tested and only
fixed when issues arise.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-02-02 9:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 0:44 Inode lockdep problem observed on 2.6.37.6 xfs with RT subvolume Kamal Dasu
2012-02-02 9:13 ` Christoph Hellwig [this message]
2012-02-02 16:26 ` Kamal Dasu
2012-02-02 16:28 ` Christoph Hellwig
2012-02-10 3:27 ` kdasu
-- strict thread matches above, loose matches on Subject: below --
2012-02-02 1:02 kdasu
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=20120202091330.GA31203@infradead.org \
--to=hch@infradead.org \
--cc=cernekee@gmail.com \
--cc=kdasu.kdev@gmail.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