Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*D\s+State\s+and\s+XFS\s+1\.2\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*D\s+State\s+and\s+XFS\s+1\.2\s*$/: 9 ]

Total 9 documents matching your query.

1. D State and XFS 1.2 (score: 1): Author: xxxxxx; Date: Tue, 27 May 2003 16:13:00 -0400; 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; /archives/xfs/2003-05/msg00279.html (7,308 bytes)
2. re[2]: D State and XFS 1.2 (score: 1): Author: xxxxx>; Date: Tue, 27 May 2003 19:12:46 -0400; 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. Unfortu; /archives/xfs/2003-05/msg00280.html (9,091 bytes)
3. Re: D State and XFS 1.2 (score: 1): Author: xxxxx>; Date: Wed, 28 May 2003 08:53:32 +0800; In my case faulty RAM hit me. Even the "extensive" BIOS check didn't find the problem: I had to do two full passes of MemTest86 to find the minor corruption. With the memory replaced, our server has; /archives/xfs/2003-05/msg00281.html (9,193 bytes)
4. D State and XFS 1.2 (score: 1): Author: n@xxxxxxxxxxx; Date: Tue, 27 May 2003 16:13:00 -0400; 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; /archives/xfs/2003-05/msg00586.html (7,308 bytes)
5. re[2]: D State and XFS 1.2 (score: 1): Author: xxxxxxxxxxxx>; Date: Tue, 27 May 2003 19:12:46 -0400; 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. Unfortu; /archives/xfs/2003-05/msg00587.html (9,091 bytes)
6. Re: D State and XFS 1.2 (score: 1): Author: xxxxxxxxxxxx>; Date: Wed, 28 May 2003 08:53:32 +0800; In my case faulty RAM hit me. Even the "extensive" BIOS check didn't find the problem: I had to do two full passes of MemTest86 to find the minor corruption. With the memory replaced, our server has; /archives/xfs/2003-05/msg00588.html (9,193 bytes)
7. D State and XFS 1.2 (score: 1): Author: Greg Freemyer <freemyer@xxxxxxxxxxxxxxxxx>; Date: Tue, 27 May 2003 16:13:00 -0400; 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; /archives/xfs/2003-05/msg00893.html (7,308 bytes)
8. re[2]: D State and XFS 1.2 (score: 1): Author: "'Greg Freemyer'" <freemyer@xxxxxxxxxxxxxxxxx>; Date: Tue, 27 May 2003 19:12:46 -0400; 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 parti; /archives/xfs/2003-05/msg00894.html (9,106 bytes)
9. Re: D State and XFS 1.2 (score: 1): Author: Federico Sevilla III <jijo@xxxxxxxxxxx>; Date: Wed, 28 May 2003 08:53:32 +0800; In my case faulty RAM hit me. Even the "extensive" BIOS check didn't find the problem: I had to do two full passes of MemTest86 to find the minor corruption. With the memory replaced, our server has; /archives/xfs/2003-05/msg00895.html (9,374 bytes)

Current List: 1 - 9
Page: [1]