Not logged in
Log in now
Create an account
Subscribe to LWN
LWN.net Weekly Edition for May 23, 2013
An "enum" for Python 3
An unexpected perf feature
LWN.net Weekly Edition for May 16, 2013
A look at the PyPy 2.0 release
The problem actually wasn't disk or raid related, but filesystem related after a kernel oops
and panic. jfyi.
On the vger.kernel.org outage
Posted Mar 21, 2008 11:44 UTC (Fri) by Cato (subscriber, #7643)
This is something of a concern too - would be interesting to know the filesystem used, how it
was configured (e.g. for ext3, was barrier=1 in effect to ensure that data=ordered works
properly with drive-level write-caching), kernel version, etc.
A kernel oops shouldn't cause a very long filesystem recovery, unless perhaps the disks are so
huge that a full fsck takes a very long time. But then a journalling filesystem should
prevent such long fsck's anyway...
Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds