Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 27 May 2003 13:06:19 -0700 (PDT) Received: from imf43bis.bellsouth.net (mail206.mail.bellsouth.net [205.152.58.146]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h4RK5w2x014361 for ; Tue, 27 May 2003 13:05:59 -0700 Received: from tiger2 ([66.156.2.201]) by imf43bis.bellsouth.net (InterMail vM.5.01.04.25 201-253-122-122-125-20020815) with SMTP id <20030527200806.LTIO17201.imf43bis.bellsouth.net@tiger2> for ; Tue, 27 May 2003 16:08:06 -0400 Date: Tue, 27 May 2003 16:13:00 -0400 From: Greg Freemyer Subject: D State and XFS 1.2 To: xfs mailing list Mime-Version: 1.0 Organization: Norcross Group X-Mailer: GoldMine [6.00.21021] Content-Type: Text/plain Message-Id: <20030527200806.LTIO17201.imf43bis.bellsouth.net@tiger2> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id h4RK5x2x014367 X-archive-position: 4162 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: freemyer@NorcrossGroup.com Precedence: bulk X-list: linux-xfs Content-Length: 602 Lines: 19 I'm running a vanilla 2.4.19 kernel with xfs 1.2 patched in. xfsdump from 1am Monday morning is stuck in D state. The server has been up and running for 40 days. The xfsdump is of a lvm snapshot. The base FS is working fine. I remember seeing threads about getting stuck in D state, but did not realize it affected the 1.2 release. (I thought it was cvs only.) Is this a known/resolved issue, or is there some interest in troubleshooting the issue. I assume I can kill -9 the stuck processes, unmount the FS and kill the snapshot to restore normal operation. Thanks Greg -- Greg Freemyer