[Bug 138044] Re: checkfs.sh chokes on loop device

[Steve Langasek]

I believe this old issue is resolved in newer versions of Ubuntu which
use mountall and upstart.

** Changed in: sysvinit (Ubuntu)
       Status: Confirmed => Fix Released

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

Title:
  checkfs.sh chokes on loop device

Status in “sysvinit” package in Ubuntu:
  Fix Released

Bug description:
  If I add a loop-mounted filesystem to /etc/fstab, the system will no
  longer boot automatically because /etc/init.d/checkfs.sh fails to
  correctly fsck that filesystem. I have to press Ctrl-D on the console
  in order to get past this.

  This is the case regardless of the following two forms I use in
  /etc/fstab (one at a time, the two forms are not present in /etc/fstab
  at the same time):

  /raid5/nobackup/backupFileSystem.img /mnt/backuphd ext2
  defaults,noauto,loop=/dev/loop0,noatime,nodiratime 1 2

  /dev/loop0 /mnt/backuphd ext2 defaults,noauto,noatime,nodiratime 1 2

  Obviously, the second form requires me to first issue losetup
  /dev/loop0 /raid5/nobackup/backupFileSystem.img before mounting, so
  that I would prefer to be able to use the first form.

  The filesystem is not corrupt: if I do the losetup thing and then call
  fsck on /dev/loop0 everything is dandy.

  I can't claim to understand /etc/init.d/checkfs.sh, but it doesn't
  seem to be able to take a configuration option that avoids it
  attempting to fsck certain entries in /etc/fstab.

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