Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*2\.6\.27\.30\s+fc10\,\s+some\s+processes\s+stuck\s+in\s+D\s+state\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*2\.6\.27\.30\s+fc10\,\s+some\s+processes\s+stuck\s+in\s+D\s+state\s*$/: 3 ]

Total 3 documents matching your query.

1. 2.6.27.30 fc10, some processes stuck in D state (score: 1): Author: <yuji_touya@xxxxxxxxxxxxxxxxxxxx>; Date: Thu, 6 Jan 2011 13:18:27 +0900; Hello folks, We need to save a bunch of transport-stream(TS) data(4MB/sec, 300GB/day), and are using xfs formatted hardware RAID system to save TS data. Some processes (pdflush, kswapd, our own servi; /archives/xfs/2011-01/msg00062.html (22,997 bytes)
2. Re: 2.6.27.30 fc10, some processes stuck in D state (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Thu, 6 Jan 2011 16:00:57 +1100; Everything is waiting for log space to be freed. Typically a sign that metadata has not been flushed or that IO completion has not occurred so the tail is not moving forward. What did you change 3 mo; /archives/xfs/2011-01/msg00063.html (8,664 bytes)
3. RE: 2.6.27.30 fc10, some processes stuck in D state (score: 1): Author: <yuji_touya@xxxxxxxxxxxxxxxxxxxx>; Date: Fri, 7 Jan 2011 20:00:38 +0900; Dave, Thank you for your replying. Nice to know it! It will help us. This always happens. Yes, new read IOs seem to wake up them. Are there any tools/ways to examine whether expected interrupt occurr; /archives/xfs/2011-01/msg00092.html (9,582 bytes)

Current List: 1 - 3
Page: [1]