All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: util-linux@vger.kernel.org
Subject: mount nofail: what failures should we allow ?
Date: Tue, 19 Jan 2016 18:24:58 -0500	[thread overview]
Message-ID: <20160119232458.GO14840@vapier.lan> (raw)

[-- Attachment #1: Type: text/plain, Size: 930 bytes --]

i've received two requests for the "nofail" option.  the doc for the
option is a bit ... terse ... so it's hard to guess at the overall
intention.

(1) ignore ENOMEDIUM like:
sys-utils/mount.c could be updated to do:
    case ENOMEDIUM:
        if (uflags & MNT_MS_NOFAIL)
            return MOUNT_EX_SUCCESS;
        warnx(_("no medium found on %s"), src);
        break;
this is for cases like cd/dvd drives which happens to have no disk loaded.

(2) ignore unknown fs types.  e.g. when a kernel config/module is missing
support for the requested filesystem type.  so a fstab entry like:
	..src..  /mnt/foo  somefs defaults,nofail
rather than error out with:
	mount: unknown filesystem type 'somefs'
it would just issue a warning like it does for other nofail options.

if we go this route though, how far should we take it ?  should we make
all failures when nofail is active the same ?  i'm kind of leaning that
way ...
-mike

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

             reply	other threads:[~2016-01-19 23:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-19 23:24 Mike Frysinger [this message]
2016-01-20 10:28 ` mount nofail: what failures should we allow ? Karel Zak
2016-01-20 20:00   ` Mike Frysinger
2016-01-21 10:18     ` Karel Zak
2016-01-20 20:20 ` [PATCH] mount: allow nofail to silence ENOMEDIUM cases Mike Frysinger
2016-01-21  9:51   ` Karel Zak

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160119232458.GO14840@vapier.lan \
    --to=vapier@gentoo.org \
    --cc=util-linux@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.