public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Christian Kujau <lists@nerdbynature.de>
Cc: 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: Fri, 23 Jan 2009 10:25:44 +1100	[thread overview]
Message-ID: <20090122232544.GX10158@disturbed> (raw)
In-Reply-To: <alpine.DEB.2.00.0901221514190.4084@bogon.housecafe.de>

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@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2009-01-22 23:26 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
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 [this message]
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=20090122232544.GX10158@disturbed \
    --to=david@fromorbit.com \
    --cc=lists@nerdbynature.de \
    --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