From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Cc: Bernard Chan <bernard@goanimate.com>
Subject: Re: ENOSPC and filesystem shutdowns
Date: Fri, 9 Sep 2011 09:19:54 +0200 [thread overview]
Message-ID: <201109090919.56571@zmi.at> (raw)
In-Reply-To: <CAKxAxjFUMrQpb5kQUdpRdt2wx83oKxaLZPTVTR_j43dkhcOyyw@mail.gmail.com>
[-- Attachment #1.1: Type: Text/Plain, Size: 946 bytes --]
On Donnerstag, 8. September 2011 Bernard Chan wrote:
> ENOSPC
There have been some "optimizations" for NFS in earlier kernel, leading
to large space reservation per open file. Marc Lehman yelled at that
early August in thread "frequent kernel BUG and lockups - 2.6.39 +
xfs_fsr". Maybe that's your problem too? Do you use "allocsize=" mount
option? It could be your new kernel version fixed that, but I can't
tell, as I'm not a dev.
inode64 helps in case there is no more space in the area <1TB. As you
have "only" 4TB, chances are it wouldn't make a difference for you.
Somebody once posted a [perl?] script on this list to find out how much
space is left at <1TB, maybe that can be of help.
--
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc
it-management Internet Services: Protéger
http://proteger.at [gesprochen: Prot-e-schee]
Tel: +43 660 / 415 6531
// Haus zu verkaufen: http://zmi.at/langegg/
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-09-09 7:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-04 6:09 ENOSPC and filesystem shutdowns Bernard Chan
2011-09-05 7:47 ` Christoph Hellwig
2011-09-08 11:09 ` Bernard Chan
2011-09-09 7:19 ` Michael Monnerie [this message]
2011-09-09 8:00 ` Christoph Hellwig
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=201109090919.56571@zmi.at \
--to=michael.monnerie@is.it-management.at \
--cc=bernard@goanimate.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