touch-packages team mailing list archive

[SideShowFry <fry@xxxxxxxxxxxxx>]

There is some terse fsck info being logged on my 14.04 Trusty desktop in
/var/log/upstart/mountall.log. Usually, it says something like this:

fsck from util-linux 2.20.1
grubboot: clean, 520/51200 files, 98181/204800 blocks


When I force checking by setting "Maximum mount count" to 1, it looks like this:

fsck from util-linux 2.20.1
grubboot has been mounted 1 times without being checked, check forced.
grubboot: 520/51200 files (10.4% non-contiguous), 98181/204800 blocks


I'm assuming that it didn't find any errors, and hoping that it will be more verbose if it does.

I might try messing with mountall.conf to try to force it to use
--verbose when calling mountall and see what that does.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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