From: Dave Chinner <david@fromorbit.com>
To: Dave Hall <kdhall@binghamton.edu>
Cc: xfs@oss.sgi.com
Subject: Re: Slightly Urgent: XFS No Space Left On Device
Date: Fri, 3 Apr 2015 09:36:08 +1100 [thread overview]
Message-ID: <20150402223608.GF8465@dastard> (raw)
In-Reply-To: <551D5316.8050201@binghamton.edu>
On Thu, Apr 02, 2015 at 10:32:54AM -0400, Dave Hall wrote:
> Thanks for the help. Rookie error. I didn't set these mount
> options, but I see that this option is set for all of the other XFS
> volumes I have.
>
> I am wondering why XFS would default this way though. Seems like
> heuristically you could assume that a large volume on a 64-bit OS
> would need 64-bit inodes.
The historical argument against inode64 on 64 bit machines was NFS
export and 32 bit clients, which could then break if we used 64 bit
inodes. The Linux NFS client handles this just fine on 32bit
machines (has for a few years), so there's no reason for us to care
very much about this anymore....
> At least perhaps put out a message from
> mkfs.xfs suggesting the use of inode64 on the mount command?
inode64 is now the default for upstream kernels (has been for a
couple of years), but older distros are not going to get those
kernel updates, or anything we might have put in xfsprogs...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2015-04-02 22:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 18:19 Slightly Urgent: XFS No Space Left On Device Dave Hall
2015-03-30 19:45 ` Dave Chinner
2015-04-01 19:53 ` Dave Hall
2015-04-02 0:12 ` Dave Chinner
2015-04-02 14:32 ` Dave Hall
2015-04-02 14:36 ` Grozdan
2015-04-02 14:41 ` Grozdan
2015-04-02 22:36 ` Dave Chinner [this message]
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=20150402223608.GF8465@dastard \
--to=david@fromorbit.com \
--cc=kdhall@binghamton.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