On 7/3/11 10:59 AM, Eric Sandeen wrote:
> On 6/30/11 4:42 PM, kkeller@xxxxxxxxx wrote:
>> # uname -a
>> Linux sahara.xxx 2.6.18-128.1.6.el5 #1 SMP Wed Apr 1 09:10:25 EDT 2009
>> x86_64 x86_64 x86_64 GNU/Linux
>> Yes, it's not a completely current kernel. This box is running CentOS 5
>> with some yum updates.
> # rpm -qa | grep xfs
> If you see anything with "kmod" you're running an exceptionally old xfs
> 2.6.18-138 and beyond should have a newer xfs backport built into the kernel
> rpm itself, as shipped from Red Hat. But the ancient xfs-kmod (or similar)
> provided xfs.ko will take precedence even if you update that kernel.
... unless you uninstall the xfs-kmod package.
(i'm not sure how to set precedence of found kernel modules, I guess)
> * Fri Apr 03 2009 Don Zickus <dzickus@xxxxxxxxxx> [2.6.18-138.el5]
> - [fs] xfs: update to 220.127.116.11 codebase (Eric Sandeen ) 
> If at all possible I'd try an updated kernel, especially if your xfs.ko
> is provided by the very, very, very old centos xfs-kmod rpm.