SCIENTIFIC-LINUX-USERS Archives

July 2014

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Patrick J. LoPresti" <[log in to unmask]>
Reply To:
Patrick J. LoPresti
Date:
Tue, 8 Jul 2014 08:59:52 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (21 lines)
On Tue, Jul 8, 2014 at 8:06 AM, Lamar Owen <[log in to unmask]> wrote:
>
> It's 'let's silently stop working when you pass 16TB of occupied space on
> your 24TB filesystem and no longer even mount it on bootup.'

You get a similar problem even on 64-bit systems unless you use the
"inode64" mount option.

"Similar problem" means that if the first 16TB of the block device are
full, file creation will fail with ENOSPC because XFS is restricting
its inode numbers to 32 bits. This failure mode is a little tricky to
diagnose, since most searches for relevant terms will tell you that
you have run out of inodes, when of course XFS is designed never to
run out of inodes (unless it runs out of disk).

inode64 was finally made the default in kernel 3.7, so I expect RHEL 7
inherited it making this a non-issue. But for RHEL 6 it still applies
(see https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Storage_Administration_Guide/xfsmounting.html)

 - Pat

ATOM RSS1 RSS2