I think the reasoning is wrong here. so, we are in the situation that fsck recovery could trigger data loss. so, it's dangerous.
question is... what is the alternative for the user? who is going to repair a filesystem corruption in any other way than fsck? ever? I mean... basically there is only one choice. but ok... I guess at least we should ask the user... instead of just dumping her into a cryptic shell. "Serious data corruption occurred, what do you want to do?" <F5> auto repair (might cause dataloss) <F6> manual repair (expert mode) -> which dumps the user to a shell as of today because right now the user is dumped into a shell and most users will not know what to do and simply reinstall ubuntu, overwriting ALL of their data! so what did we protect the user from here? -- Command-line recovery required when fsck reports an unexpectedy inconsistency https://bugs.launchpad.net/bugs/58430 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
