On Wed, 12 Mar 2003, James D. Nurmi wrote: > One other thought, I had some issues w/ XFS and AFS that might be of > note... if my cache was on XFS, I had to wipe it prior to loading the > module, else get a kernel oops, and even then it hung and oopsd after a > few days... The end solution was to create an ext2 partition and host > it there, (or a pseudo partition via dd & mkfs)... > > I know you wont see oops unless you're at the console, and when I was > getting them, it hung during the "starting afs" phaze, with little to no > other output... have you checked dmesg output or the logs? they may give > some clue as to where its hung...
James, thanks again for your comments. We use XFS only for /vicepXX partitions, never for cache. The problem we observe happens before afsd is ever started (libafs that compiles well won't load...). Clearly there is a - destructive - interference between OpenAFS and XFS patches on the top of a standard RH kernel. I only wonder if anyone was able to find a workaround. Andrei. _______________________________________________ OpenAFS-info mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-info
