Alternative suggestion: do as the error case, remount read-only with the
filesystem still marked dirty on disk. fsck still catches it on the next
| It is even _more_ inconsistent to say that with orphaned files, we'll
| let the user remount ro but not rw again!
But such an action is unsafe, therefore it is *correct* to do so regardless
of how "consistent" it is.
-- brandon s. allbery [os/2][linux][solaris][japh] firstname.lastname@example.org system administrator [WAY too many hats] email@example.com electrical and computer engineering KF8NH carnegie mellon university
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to firstname.lastname@example.org Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html