Carlos E. R. wrote:
On 2010-09-15 13:02, Dave Howorth wrote:
Just to be sure, I then manually unmounted and remounted the filesystem but still get the same errors.
What am I missing?
Maybe you need to write back many files, to distribute where the inodes go. Perhaps reformat... dunno, this is new to me.
Verify with "mount" that the option is active.
I went over and asked my question on the xfs mail list and the good folks there seem to have solved it for me. It was indeed a problem with inode limits (who even knew xfs had such limits?). There's a command that shows some details: # xfs_info /dev/mapper/vg--storage-lv--data meta-data=/dev/mapper/vg--storage-lv--data isize=256 agcount=4, agsize=134217728 blks = sectsz=512 attr=2 data = bsize=4096 blocks=536870912, imaxpct=5 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0 log =internal bsize=4096 blocks=32768, version=2 = sectsz=512 sunit=0 blks, lazy-count=0 realtime =none extsz=4096 blocks=0, rtextents=0 AIUI the imaxpct=5 means that inodes are limited to 5% of the total size of the filesystem. Running another command can increase it: # xfs_growfs -m 10 /dev/mapper/vg--storage-lv--data That seems to have fixed it, along with the inode64 mount option. Cheers, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org