All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Cc: "Guk-Bong, Kwon" <gbkwon@gmail.com>
Subject: Re: xfs hang when filesystem filled
Date: Tue, 07 Aug 2012 12:18:07 +0200	[thread overview]
Message-ID: <4713150.YEl5atVIJR@saturn> (raw)
In-Reply-To: <CAJ-WH_z+6HhooORtMKeO2=kURyiWMcxk_5eUbeBSz3cAXgRRfQ@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 647 bytes --]

Am Dienstag, 7. August 2012, 14:54:48 schrieb Guk-Bong, Kwon:
> /dev/mapper/ld1-test  94325760  94325740        20 100% /test

You should never ever come into this situation. What else than a hang 
would you expect? Should the server crash instead?
A filesystem should have at least 5% free at all times, below that 
you're in a deep trouble situation that should be fixed. To keep high 
performance, you should even keep 15% free according to Dave Chinner.

-- 
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

[-- 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

  parent reply	other threads:[~2012-08-07 10:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-07  5:54 xfs hang when filesystem filled Guk-Bong, Kwon
2012-08-07  9:05 ` Burbidge, Simon A
2012-08-08  7:55   ` Guk-Bong, Kwon
2012-08-08 10:08     ` Dave Howorth
2012-08-08 10:28     ` Burbidge, Simon A
2012-08-07 10:18 ` Michael Monnerie [this message]
2012-08-07 13:04 ` Stan Hoeppner
2012-08-08 22:23 ` 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=4713150.YEl5atVIJR@saturn \
    --to=michael.monnerie@is.it-management.at \
    --cc=gbkwon@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 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.