From: Dave Chinner <david@fromorbit.com>
To: Eli Morris <ermorris@ucsc.edu>
Cc: xfs@oss.sgi.com
Subject: Re: filesystem shrinks after using xfs_repair
Date: Fri, 30 Jul 2010 09:01:47 +1000 [thread overview]
Message-ID: <20100729230147.GN655@dastard> (raw)
In-Reply-To: <D6C570D6-FEC7-4E3C-AAC2-13275721370A@ucsc.edu>
On Thu, Jul 29, 2010 at 12:22:30PM -0700, Eli Morris wrote:
> I tried filling up the disk with data to see if that worked Ok and
> it did, up until this point. There is something I don't understand
> going on though. 'df' says that I have 381 GB free on the disk,
> but I can't write to the disk anymore because it says it there
> isn't any space left on it. Is this some insane round off error or
> is there something going on here?
If you haven't specified inode64, then all inodes are located below
the 1TB mark. You've probably run out of space (or contiguous 16k
chunks of free space) below 1TB. Using inode64 will avoid this - for
a filesystem of that size, inode64 is probably a good idea as it
will significantly improve performance.
Keep in mind that legacy 32bit applications may have problems with
64 bit inode numbers, so if you have such applications (or 32 bit
NFS clients) then you need to check carefully as to whether 64 bit
inodes will work correctly or not....
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:[~2010-06-08 15:24 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-12 1:10 filesystem shrinks after using xfs_repair Eli Morris
2010-07-12 2:24 ` Stan Hoeppner
2010-07-12 11:47 ` Emmanuel Florac
2010-07-23 8:30 ` Eli Morris
2010-07-23 10:23 ` Emmanuel Florac
2010-07-23 16:36 ` Eli Morris
2010-07-24 0:54 ` Dave Chinner
2010-07-24 1:08 ` Eli Morris
2010-07-24 2:39 ` Dave Chinner
2010-07-26 3:20 ` Eli Morris
2010-07-26 3:45 ` Dave Chinner
2010-07-26 4:04 ` Eli Morris
2010-07-26 5:57 ` Michael Monnerie
2010-07-26 6:06 ` Dave Chinner
2010-07-26 6:46 ` Eli Morris
2010-07-26 8:40 ` Michael Monnerie
2010-07-26 9:49 ` Emmanuel Florac
2010-07-26 17:22 ` Eli Morris
2010-07-26 18:33 ` Stuart Rowan
2010-07-26 21:06 ` Emmanuel Florac
2010-07-27 5:02 ` Eli Morris
2010-07-27 6:48 ` Stan Hoeppner
2010-07-27 8:21 ` Michael Monnerie
2010-07-26 10:20 ` Dave Chinner
2010-07-28 5:12 ` Eli Morris
2010-07-29 19:22 ` Eli Morris
2010-07-29 22:09 ` Emmanuel Florac
2010-07-29 22:48 ` Eli Morris
2010-07-29 23:01 ` Dave Chinner [this message]
2010-07-29 23:15 ` Eli Morris
2010-07-30 0:39 ` Michael Monnerie
2010-07-30 1:49 ` Eli Morris
2010-07-30 7:15 ` Emmanuel Florac
2010-07-30 7:57 ` Christoph Hellwig
2010-07-30 10:23 ` Michael Monnerie
2010-07-30 10:29 ` Christoph Hellwig
2010-07-30 12:40 ` Michael Monnerie
2010-07-30 13:17 ` Emmanuel Florac
-- strict thread matches above, loose matches on Subject: below --
2010-07-12 6:39 Eli Morris
2010-07-11 6:32 Eli Morris
2010-07-11 10:56 ` Stan Hoeppner
2010-07-11 16:29 ` Emmanuel Florac
2010-07-09 23:07 Eli Morris
2010-07-10 8:16 ` Stan Hoeppner
2010-07-24 21:09 ` Eric Sandeen
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=20100729230147.GN655@dastard \
--to=david@fromorbit.com \
--cc=ermorris@ucsc.edu \
--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