All of lore.kernel.org
 help / color / mirror / Atom feed
From: Turbo Fredriksson <turbo@bayour.com>
To: xfs@oss.sgi.com
Subject: No space left on device
Date: Fri, 24 Sep 2010 16:07:23 +0200	[thread overview]
Message-ID: <A7468B16-5A58-4012-B38B-784D89566D86@bayour.com> (raw)

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)...

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

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/

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

             reply	other threads:[~2010-09-24 14:06 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-24 14:07 Turbo Fredriksson [this message]
2010-09-24 15:23 ` No space left on device Geoffrey Wehrman
     [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 --
2014-02-12  9:51 Jakob Truelsen
2014-02-12 10:26 ` Hugo Mills
2014-02-12 10:45   ` Jakob Truelsen
2014-02-12 11:07     ` Hugo Mills
2014-02-12 10:34 ` Leonidas Spyropoulos
2012-11-01 13:35 no " Kenneth Johansson
2012-11-02 15:54 ` Kyle Gates
2012-11-02 15:59   ` Hugo Mills
2012-11-06 13:23   ` Kenneth Johansson
2012-08-03 10:05 Mark Marshall
2012-08-04  9:14 ` Chris Samuel
2012-08-04  9:26 ` Martin Steigerwald
2012-06-19 12:05 No " 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
     [not found] <AANLkTinH225vC8fRbA7zk_iOEmyADFZMBS6b7gx1tOxm@mail.gmail.com>
2011-02-08  9:00 ` no " Leonidas Spyropoulos
2011-02-08  9:31   ` cwillu
2011-02-08 10:08     ` Leonidas Spyropoulos
2011-02-08 13:19       ` Helmut Hullen
2011-02-08 18:56         ` Erik Logtenberg
2011-02-08 19:43           ` Helmut Hullen
2011-02-12 14:11             ` Erik Logtenberg
2011-02-08 20:36           ` Helmut Hullen
2011-02-07 21:21 Leonidas Spyropoulos
2011-02-07 21:27 ` Erik Logtenberg
2011-02-07 23:58   ` Robert G.
2011-02-08  0:09 ` C Anthony Risinger
2010-07-30  5:31 Lubos Kolouch
     [not found] ` <AANLkTikBRfR45DZxZW9LM6wnREWrbysPCr9Z1d3YuYhC@mail.gmail.com>
2010-07-30 12:27   ` Lubos Kolouch
     [not found]     ` <AANLkTinBj1O-LapAeBCT2Y3A1ZhfFZ3AotCk6SZ-e-2U@mail.gmail.com>
2010-07-30 14:30       ` Leonidas Spyropoulos
2010-07-30 15:02         ` Lubos Kolouch
2010-07-30 15:09           ` Lubos Kolouch
2010-08-14 20:15             ` Lubos Kolouch
2008-12-08  9:46 No " Gabor MICSKO
2008-12-08 14:02 ` dcg
2002-03-19 17:27 Sebastian
2002-03-20 17:27 ` David Woodhouse
2002-03-27 18:49   ` Sebastian
2002-03-27 19:13   ` David Woodhouse
2002-03-27 19:58     ` Sebastian

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=A7468B16-5A58-4012-B38B-784D89566D86@bayour.com \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.