[Bug 1303905] [NEW] should log important problems to dmesg

Colin Watson cjwatson at canonical.com
Mon Apr 7 16:41:33 UTC 2014


Public bug reported:

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.

** Affects: mountall (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to mountall in Ubuntu.
https://bugs.launchpad.net/bugs/1303905

Title:
  should log important problems to dmesg

Status in “mountall” package in Ubuntu:
  New

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1303905/+subscriptions



More information about the foundations-bugs mailing list