From: Dave Chinner <david@fromorbit.com>
To: Marc Lehmann <schmorp@schmorp.de>
Cc: Michael Monnerie <michael.monnerie@is.it-management.at>, xfs@oss.sgi.com
Subject: Re: frequent kernel BUG and lockups - 2.6.39 + xfs_fsr
Date: Thu, 11 Aug 2011 00:16:19 +1000 [thread overview]
Message-ID: <20110810141619.GA26978@dastard> (raw)
In-Reply-To: <20110809111526.GA7631@schmorp.de>
On Tue, Aug 09, 2011 at 01:15:27PM +0200, Marc Lehmann wrote:
> On Tue, Aug 09, 2011 at 12:10:48PM +0200, Michael Monnerie <michael.monnerie@is.it-management.at> wrote:
> > (rw,nodiratime,relatime,logbufs=8,logbsize=256k,attr2,barrier,largeio,swalloc)
> > and sometimes also
> > ,allocsize=64m
>
> As has been reported on this list, this option is really harmful on
> current xfs - in my case, it lead to xfs causing ENOSPC even when the disk
> was 40% empty (~188gb).
Seeing you keep stating this is a problem, I'll ask again whether
commit 778e24b ("xfs: reset inode per-lifetime state when recycling
it") fixed this problem for you?
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:[~2011-08-10 14:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-06 12:25 frequent kernel BUG and lockups - 2.6.39 + xfs_fsr Marc Lehmann
2011-08-06 14:20 ` Dave Chinner
2011-08-07 1:42 ` Marc Lehmann
2011-08-07 10:26 ` Dave Chinner
2011-08-08 19:02 ` Marc Lehmann
2011-08-09 10:10 ` Michael Monnerie
2011-08-09 11:15 ` Marc Lehmann
2011-08-10 6:59 ` Michael Monnerie
2011-08-11 22:04 ` Marc Lehmann
2011-08-12 4:05 ` Dave Chinner
2011-08-26 8:08 ` Marc Lehmann
2011-08-31 12:45 ` Dave Chinner
2011-08-10 14:16 ` Dave Chinner [this message]
2011-08-11 22:07 ` Marc Lehmann
2011-08-09 9:16 ` Marc Lehmann
2011-08-09 11:35 ` Dave Chinner
2011-08-09 16:35 ` Marc Lehmann
2011-08-09 22:31 ` 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=20110810141619.GA26978@dastard \
--to=david@fromorbit.com \
--cc=michael.monnerie@is.it-management.at \
--cc=schmorp@schmorp.de \
--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.