From: Stan Hoeppner <stan@hardwarefreak.com>
To: "Patrick J. LoPresti" <lopresti@gmail.com>
Cc: Eric Sandeen <sandeen@sandeen.net>, xfs@oss.sgi.com
Subject: Re: xfs_repair: "fatal error -- ran out of disk space!"
Date: Thu, 23 Jun 2011 02:42:41 -0500 [thread overview]
Message-ID: <4E02EE71.7010300@hardwarefreak.com> (raw)
In-Reply-To: <BANLkTinu03WnKTL=SzoWt+Sd9YHjy0_w6g@mail.gmail.com>
On 6/22/2011 6:41 PM, Patrick J. LoPresti wrote:
> I guess one question is how xfs_repair should behave in this case. I
> mean, what if the file system had been full, but too corrupt for me to
> delete anything?
Maybe you should rethink your policy on filesystem space management.
>From what you stated the FS in question actually was full. You
apparently were unaware of it until a problem (misbehaving nfsd process)
brought it to your attention. You should be monitoring your FS usage.
Something as simple as logwatch daily summaries can save your bacon here.
As a general rule, when an FS begins steadily growing past the 80% mark
heading toward 90%, you need to take action, either adding more disk to
the underlying LVM device and growing the FS, mounting a new device/FS
into a new directory in the tree and manually moving files, or making
use of some HSM software.
Full filesystems have been a source of problems basically forever. It's
best to avoid such situations instead of tickling the dragon.
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-06-23 7:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 21:32 xfs_repair: "fatal error -- ran out of disk space!" Patrick J. LoPresti
2011-06-22 22:27 ` Eric Sandeen
2011-06-22 23:24 ` Dave Chinner
2011-06-22 23:41 ` Patrick J. LoPresti
2011-06-23 7:42 ` Stan Hoeppner [this message]
2011-06-23 14:16 ` Patrick J. LoPresti
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=4E02EE71.7010300@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=lopresti@gmail.com \
--cc=sandeen@sandeen.net \
--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