fstab mount with option "nofail" not working

Bug #1653887 reported by Alexander Bangert
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
schroot (Ubuntu)
New
Undecided
Unassigned

Bug Description

We need for our schroot environment a few initial mounts. This mounts are configured in the schroot config fstab file with the following parameters:

#/yocto-build /yocto-build none bind,defaults,nofail 0 0

Important for us is the option "nofail" because there are some temporary mounts which must not exist. This "nofail" option is working as follows with no errors as expected:
sudo mount -o nofail,bind /NOT_EXISTING_DIR /mnt

But with the configured option in the fstab for schroot the following errors appears:
E: 10mount: mount: /var/lib/schroot/mount/jessie/yocto-build is not mountpoint or bad option
E: 10mount:
E: 10mount: In some cases useful info is found in syslog - try
E: 10mount: dmesg | tail or so.
E: jessie: Chroot setup failed: stage=setup-start

There are no relevant syslog or dmesg entries...

Description: Ubuntu 16.04.1 LTS
Release: 16.04

schroot:
  Installiert: 1.6.10-1ubuntu3
  Installationskandidat: 1.6.10-1ubuntu3
  Versionstabelle:
 *** 1.6.10-1ubuntu3 500
        500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
        100 /var/lib/dpkg/status

Tags: xenial
Revision history for this message
Markus F. (mk.f) wrote :

Try removing the 'defaults' option. The options contained in 'defaults' could be incompatible with the 'bind' option.

Revision history for this message
Alexander Bangert (alex66955) wrote :

I got the same behavior without the default option

Ken Sharp (kennybobs)
tags: added: xenial
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.