在ITPUB上看到這樣一個案例，在一套Linux的RAC環境中，一個OCFS卷的inode節點已經用完，但是數據庫仍然能夠正常運行。
文件可以正常創建，該系統的幾本情況大致如下：
OS:LINUXAS3 U3
ORACLE:ORACLE9204 RAC
以下為具體顯示，/U04僅僅存放兩節點產生的歸檔日志
[root@db1 /]# cat /etc/issue
Red Hat Enterprise Linux AS release 3 (Taroon Update 3)
[root@db1/]# rpm -qa |grep ocfs
ocfs-support-1.0.10-1
ocfs-tools-1.0.10-1
ocfs-2.4.21-EL-smp-1.0.13-1
[root@db1 /]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/emcpowerd1 50G 44M 50G 1% /u04
[root@db1 /]# df -i
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/emcpowerd1 409580 409231 349 100% /u04
最後作者從Metalink上找到了解釋，也就是說OCFS和通常的文件系統不同，inodes在這裡並不發揮通常文件系統的作用。
這是OCFS的特性，是正常的。
引用一點解釋記錄如下：
@ OCFS does not have the concept of inodes, however, for the vfs layer in the
@ kernel we need to fill out structures. the number returned by df -i is
@ based on diskspace free. it's the number of clusterblocsk in the filesystem
@ we dont' preallocate inodes like most filesystems do. nor do we HAVE to do
@ that. not a bug, expected behaviour, not required to do what any other
@ filesystem does.