Hi Eric, On Wed, 10 Oct 2012 09:31:16 -0500 Eric Sandeen <sandeen@xxxxxxxxxxx> wrote: > Yep. Ditch that; it overrides the maintained module that comes with > the kernel itself. See if that helps, first, I suppose. I wasn't aware that stock kernel comes with xfs module. From my testing looks like stock kernel module is still preferred over kmod-xfs: # modinfo xfs filename: /lib/modules/2.6.18-308.el5/kernel/fs/xfs/xfs.ko license: GPL description: SGI XFS with ACLs, security attributes, large block/inode numbers, no debug enabled author: Silicon Graphics, Inc. srcversion: D37A003AFEE1A42BDD4DD56 depends: vermagic: 2.6.18-308.el5 SMP mod_unload gcc-4.1 module_sig: 883f3504f44471c48d0a1fbae482c4c11225a009e3fa1179850eea96ab882c910d750e88743fec5309d1ca09de3d81add6999f9dedc65f84a0d1e21293 Most likely due to historical reasons we still install kmod-xfs on our systems. To be sure I have removed kmod-xfs, unmounted filesystem and removed kernel module and them mounted filesystem again. Still seeing the very same behaviour. > Agreed that it would be good to know whether inode64 is in use. No, we don't use any special mount options here. > Let's start there (and with a modern xfs.ko) before we speculate > further. I guess next step would be to use inode64.. Regards, Marcin _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
