日前，同事反饋一個問題：在一個大分區(24T)中使用xfs文件系統，用來做歷史文件備份，突然提示沒有磁盤空間錯誤，先檢查下：
復制代碼代碼如下:
[root@imysql ~]# df -hT
Filesystem Type Size Used Avail Use% Mounted on
/dev/sdb1 xfs 19T 16T 2.4T 88% /backup</p>
<p>[root@imysql ~]# df -hi
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/sdb1 9.3G 3.4M 9.3G 1% /backup
可以看到，不管是物理空間，還是inode，都還有很多余量，那為何還會報告磁盤空間不夠呢？
查詢了下XFS FAQ，發現有一段：
復制代碼代碼如下:
Q: What is the inode64 mount option for?</p>
<p>By default, with 32bit inodes, XFS places inodes only in the first 1TB of a disk. If you have a disk with 100TB, all inodes will be stuck in the first TB. This can lead to strange things like "disk full" when you still have plenty space free, but there's no more place in the first TB to create a new inode. Also, performance sucks.
To come around this, use the inode64 mount options for filesystems >1TB. Inodes will then be placed in the location where their data is, minimizing disk seeks.
Beware that some old programs might have problems reading 64bit inodes, especially over NFS. Your editor used inode64 for over a year with recent (openSUSE 11.1 and higher) distributions using NFS and Samba without any corruptions, so that might be a recent enough distro.
大意就是xfs文件系統會把inode存儲在磁盤最開始的這1T空間裡，如果這部分空間被完全填滿了，那麼就會出現磁盤空間不足的錯誤提示了。解決辦法就是在掛載時，指定 inode64 選項：
復制代碼代碼如下:
mount -o remount -o noatime,nodiratime,inode64,nobarrier /dev/sdb1 /backup
P.S，磁盤空間小於1T的不用擔心這個問題 :)
