Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f7T8J1Y17477 for linux-xfs-outgoing; Wed, 29 Aug 2001 01:19:01 -0700 Received: from babel.spoiled.org (babel.spoiled.org [212.84.234.227]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f7T8Iwd17439 for ; Wed, 29 Aug 2001 01:18:58 -0700 Received: (qmail 14677 invoked by uid 8); 29 Aug 2001 08:18:56 -0000 From: thomas graichen Reply-To: thomas graichen X-Newsgroups: spoiled.linux.sgi.xfs Subject: Re: Exim and XFS filesystem Date: Wed, 29 Aug 2001 09:57:06 +0200 Organization: spoiled dot org Lines: 27 Distribution: local Message-ID: References: <3B8BB7C7.4020808@omniti.com> <3B8BBB17.FD7AF0E5@sgi.com> Reply-To: thomas graichen X-Complaints-To: newsmaster@spoiled.org User-Agent: tin/1.4.4-20000803 ("Vet for the Insane") (UNIX) (Linux/2.4.8-xfs (i686)) To: linux-xfs@oss.sgi.com Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Eric Sandeen wrote: > "Theo E. Schlossnagle" wrote: >> Exim v3.14,v3.22,v3.33 and Linux 2.4.2-xfs. The xfs parition in question is >> running atop a RAID-1 md device on two 9GB scsi drives. >> It looked as if the kernel had a thread stuck writing to or reading from the >> filesystem journal. If anyone knows a solution to this problem, I am all >> ears. Otherwise, steer clear of running you Exim spools on xfs. > My first suggestion would be to upgrade to XFS-1.0.1 if possible, > 2.4.2/XFS-1.0 is a bit old, and several fixes went into 1.0.1 1.0.1 is > available as a patch against vanilla 2.4.5, or coupled with Red Hat's > 2.4.3 kernel release for RH Linux 7.1. and if it still happens then i think it would be a good idea to setup a serial console and enable kdb - you should be able to break into the debugger then this happens and give more detailed information about the state ... other might describe what exactly to do then better ... t -- thomas graichen ... perfection is reached, not when there is no longer anything to add, but when there is no longer anything to take away. --- antoine de saint-exupery