[Top] [All Lists]

Re: Slightly Urgent: XFS No Space Left On Device

To: Dave Hall <kdhall@xxxxxxxxxxxxxx>
Subject: Re: Slightly Urgent: XFS No Space Left On Device
From: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Fri, 3 Apr 2015 09:36:08 +1100
Cc: xfs@xxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <551D5316.8050201@xxxxxxxxxxxxxx>
References: <551993CF.4060908@xxxxxxxxxxxxxx> <20150330194510.GD28621@dastard> <551C4CB8.7@xxxxxxxxxxxxxx> <20150402001235.GI28621@dastard> <551D5316.8050201@xxxxxxxxxxxxxx>
User-agent: Mutt/1.5.21 (2010-09-15)
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...


Dave Chinner

<Prev in Thread] Current Thread [Next in Thread>