Messages in this thread | | | Date | Mon, 17 Jan 2005 12:55:42 +0100 | From | Jan-Frode Myklebust <> | Subject | Re: XFS: inode with st_mode == 0 |
| |
On Mon, Jan 17, 2005 at 11:07:46AM +0100, Jakob Oestergaard wrote: > > Where should I begin? ;)
Guess we've been struggeling with much of the same problems..
> ------- > Scenario 2: Mailservers: > Running XFS on mailqueue:
The 2.6.10-1.737_FC3 + 's/posix_lock_file/posix_lock_file_wait/' on fs/nfs/file.c seems stable on our mailserver running XFS on mail queue and spool (mbox). 4 days of uptime!
> > ======= > Resolution to the storage server problem: > 2.6.8.1 UP is stable (but oopses regularly after memory allocation > failures)
My XFS-fileserver ran 2.6.9-rc3 stable since october 25. Got lots of "possible deadlock in kmem_alloc (mode:0xd0)" this weekend, so I upgraded to plain 2.6.10. Seems OK so far.
> > Hardware on all servers: IBM x335 and x345.
Mail servers: Dell 2650, IBM ServeRAID 6M, EXP400. File servers: IBM x330, qla2300, infortrend eonstor.
All running Whitebox/centos RHEL clone.
-jf - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |