public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Geoffrey Wehrman <gwehrman@sgi.com>
To: Turbo Fredriksson <turbo@bayour.com>
Cc: xfs@oss.sgi.com
Subject: Re: No space left on device
Date: Fri, 24 Sep 2010 10:23:24 -0500	[thread overview]
Message-ID: <20100924152324.GA5551@sgi.com> (raw)
In-Reply-To: <A7468B16-5A58-4012-B38B-784D89566D86@bayour.com>

On Fri, Sep 24, 2010 at 04:07:23PM +0200, Turbo Fredriksson wrote:
| I started with a few hundred gig on my FS
| (on top of LVM which in turn is on top a bunch
| of MD devices).
| 
| Slowly increasing the size with pvmove/{vg,lv}extend
| etc. Yesterday, I added more disks yet again and
| now have about 8Tb on one FS... ~1Tb free. But still
| get the 'No space left on device'.
| 
| 
| I've been looking through the 'Net and it
| must be because I'm out of inodes (and that
| the data is on the first 1Tb etc)...

You may may be able to workaround the the problem by increasing imaxpct
on the filesystem.
See http://oss.sgi.com/archives/xfs/2010-09/msg00295.html

| I'm running on AMD 64bit (native kernel, but
| Debian Lenny 32bit userland - 2.6.2[4-6] kernel).
| 
| 
| 
| Now, if I use (I'll try to upgrade to a newer
| kernel so I can reverse) the inode64, what
| impact will this have? I guess I still have
| to move my firstly created 1Tb of-disk and
| then back again?
| 
| 
| The worst thing is that every time I grow
| the FS, I have to reboot into a 32bit kernel:
| 
| xfs_growfs: XFS_IOC_FSGROWFSDATA xfsctl failed: Invalid argument

This may be becuase your are running 32bit userland.

| and then back to the 64bit kernel... How will
| this (system/FS) react if I go 64bit inodes?!
| 
| 
| And how safe is this!? I just don't have the
| possibility to do a full backup of all this
| data, not even temporarily... I _might_ be
| able to do this in a few weeks (work is ordering
| a bunch of LaCie 8Tb USB/eSATA storage boxes
| which I might be able to load for a few days
| 'to do some stress testing on' :)
| 
| 
| References:
| http://xfs.org/index.php/XFS_FAQ#Q:_Why_do_I_receive_No_space_left_on_device_after_xfs_growfs.3F
| http://xfs.org/index.php/XFS_FAQ#Q:_Can_I_just_try_the_inode64_option_to_see_if_it_helps_me.3F
| http://www.doc.ic.ac.uk/~dcw/xfs_16tb/

Once you have 64bit inodes, it is difficult to go back to 32bit inodes.
The filesystem will stay together, but you may not be able to access
your files with 64bit inodes from 32bit applications.


-- 
Geoffrey Wehrman

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

  reply	other threads:[~2010-09-24 15:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-24 14:07 No space left on device Turbo Fredriksson
2010-09-24 15:23 ` Geoffrey Wehrman [this message]
     [not found]   ` <2D51C7BA-FE51-48AF-9839-1A6AD2171510@bayour.com>
     [not found]     ` <20100927160643.GA10594@sgi.com>
     [not found]       ` <D3DB5B56-D15C-408C-B2B4-58626C23D798@bayour.com>
2010-10-04  6:40         ` Turbo Fredriksson
2010-09-25  2:18 ` Dave Chinner
  -- strict thread matches above, loose matches on Subject: below --
2012-06-19 12:05 André Øien Langvand
2012-06-19 12:36 ` Geoffrey Wehrman
2012-06-20  6:07   ` Dave Chinner
2012-06-20 15:30     ` André Øien Langvand

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=20100924152324.GA5551@sgi.com \
    --to=gwehrman@sgi.com \
    --cc=turbo@bayour.com \
    --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