Open-E Knowledgebase
Search:     Advanced search

System reports 'disk full' when there is in fact free space.

Article ID: 2423
Last updated: 14 May, 2013
Views: 1810
Posted: 14 May, 2013
by:
Updated: 14 May, 2013
by: Rafinski G.

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.

This can be corrected with a small update from the support team.
To get the small update, please open a support case in your user portal.

This article was:   Excellent | Very Good | Good | Fair | Poor
Also listed in
folder Troubleshooting -> Software -> SMB problems

Prev   Next
Can't access my shares when NFS Failover is on.     ACL for users secondary group not working while using NFS share...

The Knowledge base is managed by Open-E data storage software company.
RSS