should log important problems to dmesg
Bug #1303905 reported by
Colin Watson
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| mountall (Ubuntu) |
Confirmed
|
High
|
Unassigned | ||
Bug Description
I logged into a remote system today to find that its root filesystem was read-only. I didn't expect logs to be updated, but I tried looking in dmesg to see what the problem was: there was no indication there. Adam looked at the console and found something there, but it would have been helpful to have a hint of the problem (last mount in the future due to a wrong clock, in this case) in dmesg for easier debugging.
| Changed in mountall (Ubuntu): | |
| importance: | Undecided → High |
Revision history for this message
| Mehmet Atif Ergun (mehmetaergun) wrote | #1 |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in mountall (Ubuntu): | |
| status: | New → Confirmed |
To post a comment you must log in.
Bug #513644 might be relevant for when you were to reboot the system to have an fsck run on it.