The user is always right
Today I had a failing fsck during Ubuntu startup: any HDD activity would simply stop when the check claimed to have reached 89% Couldn't abort, had to cold start the box. Same result. OK, abort the check, bypass it and see what's going on. If only! Ubuntu thinks it is a great idea to drop normal users into maintenance mode. Once you leave maintenance mode, the check starts again! Same result. Did it occur to anyone that the check itself might be at fault sometimes, and that a userfriendly way to bypass this check is absolutely crucial?
(If fsck had a better reputation for finding real problems instead of being the root cause for many data losses, and if the ext4 version wasn't written by mr-lossy-file-systems-ftw himself, then perhaps I'd be worried. I am not. Fsck offers little protection if you don't have a real backup anyway. So the best advice is really to disable any automatic fsck checks.)
Comments
No comments yet.
Post a Comment
This site's webmaster failed misserably in upgrading the underlaying web framework.
The comment system is entirely broken right now. Sorry!
