From: Christian Kujau <lists@nerdbynature.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: 3.5.0-rc5: inconsistent lock state
Date: Thu, 5 Jul 2012 05:44:50 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.01.1207050535420.5568@trent.utfs.org> (raw)
In-Reply-To: <20120705074307.GA28127@infradead.org>
On Thu, 5 Jul 2012 at 03:43, Christoph Hellwig wrote:
> See my "do not take the iolock in inode reclaim context" series from
> yesterday, which should take care of this.
OK, good. I'll wait until this hits mainline then.
> Btw, if you hit this it's a sign you have out of the inode attributes,
> so if this isn't just a single inode with them you might be better off
> using larger inodes.
..."(run) out of inode attributes" - not really sure what that means and
why that would be the case.
And "using larger inodes" sounds like a
reformat with a larger "-i size=" option. Is there a way to find out my
current inode size? "mkfs.xfs -N" does not print its default values on a
mounted filesystem and I'm pretty sure I've used the default values when I
created the filesystem a while ago (i.e. just plain "mkfs.xfs" w/o any
options)
Thanks,
Christian.
--
BOFH excuse #109:
The electricity substation in the car park blew up.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-07-05 12:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-04 19:13 3.5.0-rc5: inconsistent lock state Christian Kujau
2012-07-04 19:14 ` Christian Kujau
2012-07-05 7:43 ` Christoph Hellwig
2012-07-05 12:44 ` Christian Kujau [this message]
2012-07-05 21:59 ` Dave Chinner
2012-07-05 23:39 ` Christian Kujau
2012-07-06 1:01 ` Dave Chinner
2012-07-06 1:55 ` Christian Kujau
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=alpine.DEB.2.01.1207050535420.5568@trent.utfs.org \
--to=lists@nerdbynature.de \
--cc=hch@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.