| To: | Christian Kujau <lists@xxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: No space left on device on xfs filesystem with 1.6TB free |
| From: | Dave Chinner <david@xxxxxxxxxxxxx> |
| Date: | Fri, 23 Jan 2009 10:25:44 +1100 |
| Cc: | Owen Dunn <osd1000@xxxxxxxxx>, xfs@xxxxxxxxxxx |
| In-reply-to: | <alpine.DEB.2.00.0901221514190.4084@xxxxxxxxxxxxxxxxxx> |
| Mail-followup-to: | Christian Kujau <lists@xxxxxxxxxxxxxxx>, Owen Dunn <osd1000@xxxxxxxxx>, xfs@xxxxxxxxxxx |
| References: | <alpine.LSU.2.00.0901211007200.19898@xxxxxxxxxxxxxxxxxxxxxx> <20090121225453.GN10158@disturbed> <20090122030955.GT10158@disturbed> <alpine.DEB.2.00.0901221514190.4084@xxxxxxxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.18 (2008-05-17) |
On Thu, Jan 22, 2009 at 03:15:59PM +0100, Christian Kujau wrote: > On Thu, 22 Jan 2009, Dave Chinner wrote: >> 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. > > With volumes bigger and bigger, should this procedure be mentioned in > the xfs_growfs manpage or in the XFS FAQ? Sure: the FAQ is a wiki now so you can add it yourself. ;) http://xfs.org/index.php/XFS_FAQ Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: spurious -ENOSPC on XFS, Christoph Hellwig |
|---|---|
| Next by Date: | Re: [PATCH] Re: Corrupted XFS log replay oops., Dave Chinner |
| Previous by Thread: | Re: No space left on device on xfs filesystem with 1.6TB free, Christian Kujau |
| Next by Thread: | Re: No space left on device on xfs filesystem with 1.6TB free, Christian Kujau |
| Indexes: | [Date] [Thread] [Top] [All Lists] |