Util-Linux package development
 help / color / mirror / Atom feed
From: Zoltan <zoltan@z2zcorp.com>
To: util-linux@vger.kernel.org
Subject: util-linux-2.27.1 - umount -a -O _netdev problem, _netdev ignored
Date: Sat, 30 Jan 2016 19:30:13 -0800	[thread overview]
Message-ID: <56AD7FC5.3080902@z2zcorp.com> (raw)

Hello,

There is a problem in the code of util-linux-2.27.1, in the umount binary.

The command

umount -a -O _netdev

does _not_ umount anything, despite an /etc/fstab with the likes of

...
alpha:/var/mail       /var/mail      nfs _netdev,soft,tcp
...

The "mount -a -O _netdev" command works as expected.  However, the
/run/mount/utab files is empty, and I was unable to get the "umount -a -O
_netdev" to work as advertised.  Running it with "--verbose" flag merely
confirmed that everything was being ": ignored".

I have a physical /etc/mtab (not symlink), and the "_netdev" option is missing
from /etc/mtab file, but that's probably expected???

If I manually add it (_netdev) to /etc/mtab, then the umount -a -O _netdev
does work.  But /run/mount/utab is empty.  Trying to step through the code
gets pretty brutal, and the *fs population is still hidden inside some
macro...and I can never find where the /run/mount/utab is even being parsed in
the umount code-path.

This is with a root-over-NFS setup, in case that matters.  Probably shouldn't.
 Kernel is 4.3.0.

Is this  a regression?  Seems there were issues before...wondering if it
re-surfaced.

-- 
     ###  Any similarity between my views and the truth is completely ###
     ###     coincidental, except that they are endorsed by NO ONE    ###

             reply	other threads:[~2016-01-31  4:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-31  3:30 Zoltan [this message]
2016-02-01 10:14 ` util-linux-2.27.1 - umount -a -O _netdev problem, _netdev ignored 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=56AD7FC5.3080902@z2zcorp.com \
    --to=zoltan@z2zcorp.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox