tags 594812 + moreinfo quit Jonathan Nieder wrote: > Daniel Kobras wrote:
>> I've updated my devel machine to the latest kernel version, and now I can >> reproduce the problem. It's not the fsync(), actually, but but the stopping >> of >> the pdflush daemon that makes the flush-<major>:<minor> kernel threads enter >> a >> busy loop (spinning in bdi_writeback_task()). It can be triggered as simple >> as: >> >> echo 0 > /proc/sys/vm/dirty_writeback_centisecs >> >> (Use echo 500 > /proc/sys/vm/dirty_writeback_centisecs to restore a sane >> behaviour.) Suspending pdflush activity this way used to work before. Now it >> seems to be interpreted as a zero wait time between iterations in the flush >> threads. Thus, I'd say this is a regression in the kernel. > > Thanks. What version did you experience this on? Is it fixed in > squeeze? Ping? -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
