From: Dave Chinner <david@fromorbit.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: "Patrick J. LoPresti" <lopresti@gmail.com>, xfs@oss.sgi.com
Subject: Re: xfs_repair: "fatal error -- ran out of disk space!"
Date: Thu, 23 Jun 2011 09:24:18 +1000 [thread overview]
Message-ID: <20110622232418.GV32466@dastard> (raw)
In-Reply-To: <4E026C42.2030500@sandeen.net>
On Wed, Jun 22, 2011 at 05:27:14PM -0500, Eric Sandeen wrote:
> On 6/22/11 4:32 PM, Patrick J. LoPresti wrote:
> > I have a 5.1TB XFS file system that is 93% full (399G free according to "df").
> >
> > I am trying to run "xfs_repair" on it.
> >
> > The output is appended.
> >
> > Question: What am I supposed to do about this? "xfs_repair -V" says
> > "xfs_repair version 3.1.5". (I downloaded and built the latest
> > version hoping it would fix the issue, but no luck.) Should I just
> > start deleting files at random?
>
> You could start by removing a few files you know you don't need, rather than
> at random. :)
>
> TBH I've not seen this one before, and the error message is not all that
> helpful. It'd be nice to know how many blocks it was trying to reserve
> when it ran out of space; I guess you'd need to use gdb, or instrument
> all the calls to res_failed() in phase6.c to know for sure...
Also, the number of inodes and directories in your filesystem might
tell us whether we should expect an ENOSPC, as well. I suspect that
there's an accounting error, because 400GB of transaction
reservations is an awful lot of directory rebuilds....
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-06-22 23:24 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 [this message]
2011-06-22 23:41 ` Patrick J. LoPresti
2011-06-23 7:42 ` Stan Hoeppner
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=20110622232418.GV32466@dastard \
--to=david@fromorbit.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