I have a server with a single 3ware 7500-8 board and 8 Maxtor 160GB disks running as a hardware RAID5 w/ a hot spare. I'm running RedHat 7.3 and the 2.4.18-18SGI_XFS_1.2.0smp kernel (more on the kern
At 12:57 18-2-2004 -0500, Joshua Baker-LePain wrote: I've pretty much ruled out hardware. I've swapped the 3ware and rebuilt the array, and the disks all show good SMART data. Have you considered rai
At 19:41 18-2-2004 +0100, Seth Mos wrote: At 12:57 18-2-2004 -0500, Joshua Baker-LePain wrote: Perhaps creating the filessystem with a larger inode size like 512. You could also use version logs inst
Unfortunately I shold have mentioned that this is a heavily used production server, and doing anything the requires rebuilding the FS is pretty much off limits unless I have a *very* good reason. Yea
described Yeah, I really think it's the large number of files. I'm working to see how much of them we can clean up right now. I was wondering if xfs_fsr would be a good idea, but ISTR it not being al
Ah... sure... :) Can you watch /proc/slabinfo as this happens, is any particular slab cache growing extremely large? Where is the memory going? Glen suggested that perhaps your directory with all th
There's nothing like confidence I always say... ;) I'll schedule some time to reboot into the "newer" kernel to try this. I reverted to XFS 1.2 after that behavior (obviously), and can't reboot ATM a
If any one of those has a huge number of inodes in a single dir, that'd be the one we're interested in. -Eric -- Eric Sandeen [C]XFS for Linux http://oss.sgi.com/projects/xfs sandeen@xxxxxxx SGI, Inc