Comment 4 for bug 132279
Revision history for this message
| asdfghjklasdfghjkl (asdfghjklasdfghjkl-deactivatedaccount-deactivatedaccount) wrote Re: Usability: 'Cannot mount volume' details are not selectable | #4 |
But why is the -o force not enabled by default?
If the case's that it's potentially dangerous to mount a dirty volume, the package should ASK the user what to do, ignore the case that can lead to data loss and mount it, or "Do not mount".
The possibility of data loss in dirty unmount situations is relatively small, so small that every volume should be mountable without any data loss.
I have always forced the mount, and nothing bad has happened.