Have you checked that you have free inodes on your XFS partitions? xfs_db -r -c sb -c p /dev/sda1 | egrep 'ifree|icount' If you're running low - you'll have to mount your partition with the inode64 option. Note that it requires a 64bit box and all your gluster clients will also need to be 64bit for everything to work. There is a thread here a few months back about inode64 and gluster - dig through the archives lots of good info in it - but the short is it works fine as long as everything is 64bit. liam On Fri, Sep 18, 2009 at 5:44 PM, Nathan Stratton <nathan at robotics.net> wrote: > > Anyone else running into problems with XFS and Gluster? Things run fine for > a while, but then I get things like: > > ls: reading directory .: Input/output error > > I initially did not think it was a Gluster issue because I saw the errors on > the raw XFS exported partition. However when I checked I found that the > problem happened on all 4 nodes. I just don't know how 4 XFS partions on 4 > different boxes could all become corrupted at one time. > > Whatever happens it is bad wrong because xfs can't even fix it: > > http://share.robotics.net/xfs-crash.txt > >> <> > > Nathan Stratton ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?CTO, BlinkMind, Inc. > nathan at robotics.net ? ? ? ? ? ? ? ? ? ? ? ? nathan at blinkmind.com > http://www.robotics.net ? ? ? ? ? ? ? ? ? ? ? ?http://www.blinkmind.com > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://gluster.org/cgi-bin/mailman/listinfo/gluster-users >
