From: Dave Chinner <david@fromorbit.com>
To: Owen Dunn <osd1000@cam.ac.uk>, xfs@oss.sgi.com
Subject: Re: No space left on device on xfs filesystem with 1.6TB free
Date: Thu, 22 Jan 2009 14:09:55 +1100 [thread overview]
Message-ID: <20090122030955.GT10158@disturbed> (raw)
In-Reply-To: <20090121225453.GN10158@disturbed>
On Wed, Jan 21, 2009 at 10:33:10AM +0000, Owen Dunn wrote:
> I'm running SuSE Linux Enterprise Server 10 SP2, on a 32-bit i386 Linux
> machine with kernel version 2.6.16.60-0.33-smp. I appear to have version
> 2.9.4 of xfsprogs.
>
> I have a 6TB xfs filesystem which has been grown twice from 2TB, and which
> appears to have 1.6TB and plenty of inodes free. However, attempts to
> create a new file fail with ENOSPC:
You've run out of inode space below 1TB or free space is
sufficiently fragmented below 1TB that new inode chunks cannot
be allocated.
> sf3:/EXPORT/space # touch splat
> touch: cannot touch `splat': No space left on device
> sf3:/EXPORT/space # df -h .
> Filesystem Size Used Avail Use% Mounted on
> /dev/mapper/bigvg-lv1
> 6.0T 4.5T 1.6T 75% /EXPORT/space
> sf3:/EXPORT/space # df -ih .
> Filesystem Inodes IUsed IFree IUse% Mounted on
> /dev/mapper/bigvg-lv1
> 4.0G 887K 4.0G 1% /EXPORT/space
df -i really doesn't tell you anything useful on filesystems that
dynamically allocate inodes like XFS.
> Any idea what's going on and how to fix it?
The only way to fix this is to move data around to free up space
below 1TB. Find your oldest data (i.e. that was around before even
the first grow) and move it off the filesystem (move, not copy).
Then if you copy it back on, the data blocks will end up above 1TB
and that should leave you with plenty of space for inodes below 1TB.
A complete dump and restore will also fix the problem ;)
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:[~2009-01-22 3:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 10:33 No space left on device on xfs filesystem with 1.6TB free Owen Dunn
2009-01-21 17:49 ` Bryon Roche
2009-01-21 20:08 ` Patrick Schreurs
[not found] ` <20090121225453.GN10158@disturbed>
2009-01-22 3:09 ` Dave Chinner [this message]
2009-01-22 10:25 ` Patrick Schreurs
2009-01-22 17:39 ` Eric Sandeen
2009-01-22 14:15 ` Christian Kujau
2009-01-22 23:25 ` Dave Chinner
2009-01-23 8:21 ` Christian Kujau
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=20090122030955.GT10158@disturbed \
--to=david@fromorbit.com \
--cc=osd1000@cam.ac.uk \
--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