Dave Howorth wrote:
Sandy Drobic wrote:
Maybe you maxed out the number of possible inodes.
The XFS FAQ says: "Q: What is the inode64 mount option for? "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. "Q: Can I just try the inode64 option to see if it helps me? "Starting from kernel 2.6.35, you can try and then switch back. Older kernels have a bug leading to strange problems if you mount without inode64 again. For example, you can't access files & dirs that have been created with an inode >32bit anymore." Am I right in thinking that using 'inode64' is likely to cure my problem? And then I'll be stuck with it, even if I upgrade from 11.2 to 11.3? (kernel 2.6.34, AFAIK) Do I just unmount the filesystem, add the option in fstab and remount? Cheers, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org