I have a litte problem with a xfs filesystem while stress testing a new server (not in production yet). When i try to create a new file i get no space left on device but have 13GB available. The fil
I think you got bitten by stripe alignment. Inode clusters are allocated on stripe boundaries. You probably have no boundaries left free, so it cannot allocate any inode space. If you go into xfs_db
Actually, you are out of inode room. We actually allocate inodes in blocks of 64 - which is 4 fs blocks in the default setup. We deal with them in memory in chunks of 2 fs blocks, but on disk we ask
Hi Steve Should i run xfs_db with freesp and frag? I had run frag before the no space left situation (about 70% usage i guess), it reports 14% fragmentation. The files are actually copied from our ma
Hi Steve It would be nice if it can fallback to smaller chunks. Ideally down to 1 fs block. Or reduced the report of free inodes (df -i). It is somewhat ugly to get a file system full error when df a
I have a litte problem with a xfs filesystem while stress testing a new server (not in production yet). When i try to create a new file i get no space left on device but have 13GB available. The fil
I think you got bitten by stripe alignment. Inode clusters are allocated on stripe boundaries. You probably have no boundaries left free, so it cannot allocate any inode space. If you go into xfs_db
Actually, you are out of inode room. We actually allocate inodes in blocks of 64 - which is 4 fs blocks in the default setup. We deal with them in memory in chunks of 2 fs blocks, but on disk we ask
Hi Steve Should i run xfs_db with freesp and frag? I had run frag before the no space left situation (about 70% usage i guess), it reports 14% fragmentation. The files are actually copied from our ma
Hi Steve It would be nice if it can fallback to smaller chunks. Ideally down to 1 fs block. Or reduced the report of free inodes (df -i). It is somewhat ugly to get a file system full error when df a