Comment 35 for bug 620074
Revision history for this message
|
|
#35 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Re: blaming the scheduler in 2.6.26
The problem was observed a long time before that. There might be additional
scheduler problems (this bug in general suffers from the "lots of different problems" disease), but that is unlikely to be the old well known disk starvation with different devices issue.
Re comment #9 vim stalls while disk is pounded:
You're running ext3 or reiser right? That's a known problem in that vim
regularly does fsync on its auto safe file and that causes a synchronous
JBD transaction and since all transactions are strictly ordered if there
are enough of them in front and the disk is busy it takes quite a long time.
At least on the higher level that is supposed to be mostly solved by ext4
or by XFS.
Of course it's another problem that the disk schedulers allow that long starvation in the first time.