touch-packages team mailing list archive

[Boris Gjenero <boris.gjenero@xxxxxxxxx>]

In 14.10 amd64, mountall keeps running, causing init to keep
/var/log/upstart/mountall.log open for writing, which prevents root from
being remounted read-only.

These things are easy to examine by adding a /bin/sh line to /etc/init.d/reboot in do_stop() before "reboot -d -f -i". Then when you reboot you can switch to virtual console 1 and use lsof and other commands to explore what is going on. For example this is the line in lsof output showing the problem:
init         1 root    8w      REG                8,5      613 1062101 /var/log/upstart/mountall.log

I added a 
/usr/bin/killall mountall 
line to /etc/init.d/umountroot before root is supposed to be remounted read-only. That seems to fix the problem. You need the full path because /usr/bin isn't in PATH, and don't use -9.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1261730

Title:
  /dev/sda1 must be recovered on every boot

Status in upstart package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 14.04 dev with mountall 2.52. On every boot I'm
  seeing these lines:

  [    8.535902] EXT4-fs (sda1): INFO: recovery required on readonly filesystem
  [    8.536025] EXT4-fs (sda1): write access will be enabled during recovery
  [   17.599477] EXT4-fs (sda1): recovery complete
  [   17.615731] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)

  
  I'm also wondering why it isn't telling me how many inodes were repaired (I remember to have seen this number on "real" recoveries a while ago).

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