On 07/08/2014 11:59 AM, Patrick J. LoPresti wrote:
On Tue, Jul 8, 2014 at 8:06 AM, Lamar Owen <[email protected]> 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.
Thanks for the pointer, Pat.
I don't recall if I had to specify that option or not with CentOS 5.10:
+++++++++++++++++++++++++++
[root@backup-rdc ~]# df -h
Filesystem Size Used Avail Use% Mounted on
...
/dev/mapper/plates-cx3--80
27T 26T 805G 98% /opt/plates
/dev/mapper/vg_opt-lv_backups
5.8T 5.4T 365G 94% /opt/backups
[root@backup-rdc ~]# blkid
...
/dev/mapper/plates-cx3--80: UUID="8890b8ac-874a-4526-be34-4f1f079fc826"
TYPE="xfs"
/dev/mapper/vg_opt-lv_backups:
UUID="25ace88b-1498-4843-8877-0cac46692c87" TYPE="ext4"
...
[root@backup-rdc ~]# cat /etc/redhat-release
CentOS release 5.10 (Final)
[root@backup-rdc ~]# cat /etc/fstab
...
/dev/plates/cx3-80 /opt/plates xfs defaults 1 2
/dev/vg_opt/lv_backups /opt/backups ext4 defaults 1 2
[root@backup-rdc ~]#
++++++++++++++++++++++++
That's using the default kmod-xfs from CentOS 5.
(see
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Storage_Administration_Guide/xfsmounting.html)
I don't have any >16TB filesystems on EL6, so haven't run into that one.
