Murthy,
Thanks
I'm not sure I am having the same I'm not sure I am having the same problem you
were having.
I just started having D-state lockups on another Linux box where I don't have
any xfs partitions.
Unfortunately I am out of the office for the next couple of days, so I will
have to look into it Friday.
Thanks
Greg
--
Greg Freemyer
>> Greg, you can just issue an /sbin/xfs_freeze -u <snapshot "parent"> and
>> your
>> filesystem will come unstuck (after which you can unmount and mount to
>> sync
>> your fs); a kill -9 on the stuck processes will not do it, IIRC.
>> My earlier message, unfortunately buried in the "zero filled files"
>> thread,
>> goes over this.
>> >-----Original Message-----
>> >From: Greg Freemyer [mailto:freemyer@xxxxxxxxxxxxxxxxx]
>> >Sent: Tuesday, May 27, 2003 16:13
>> >To: xfs mailing list
>> >Subject: D State and XFS 1.2
>> >
>> >
>> >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
>> >
>> >
|