[Bug 513644] Re: Does not log fsck invocations in /var/log/fsck/

[Tristan Grimaux]

This is a critical bug. One of those bugs you find when everything is in
danger, and about to be lost. As I gently type, I'm trying to find ways
to recover my server. I know there has to be a disk about to fail, I've
seen the strange behavior on boot and because I was there I know
something is wrong.

But there is no log about it.

If you are so insensitive to keep this bug as a wishlist, if you truly
don't care that not having a good log about a critical event on boot is
crushing our hearts, you will be hurting the sysadmin community.

And this is no good.

Because we know for sure this is easy to fix. A silly bug indeed.

-- 
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/513644

Title:
  Does not log fsck invocations in /var/log/fsck/

Status in “mountall” package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: mountall

  This concerns mountall 1.0 in Karmic.

  After fsck is invoked at boot time, the two log files in
  /var/log/fsck/ remain empty. In Jaunty, the
  /etc/init.d/check{fs,root}.sh scripts saved the output of the commands
  to that directory ("A log is being saved in ${FSCK_LOGFILE} if that
  location is writable") but mountall has yet to do this.

  As this would have to be newly implemented, I'd like to request a
  slight change from the Jaunty behavior, and have entries be appended
  to the log files rather than the files being overwritten each time
  with the latest (single) entry. Log rotation on these files may be
  good, too, although I'm not sure which package would/should be
  responsible for that.

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