From: Karel Zak <kzak@redhat.com>
To: Bruce Dubbs <bruce.dubbs@gmail.com>
Cc: util-linux@vger.kernel.org
Subject: Re: umount -r
Date: Mon, 13 May 2013 14:41:24 +0200 [thread overview]
Message-ID: <20130513124010.GA1865@x2.net.home> (raw)
In-Reply-To: <518C7226.7020407@gmail.com>
On Thu, May 09, 2013 at 11:05:58PM -0500, Bruce Dubbs wrote:
> We have as a part of our shutdown scripts:
>
> umount -a -d -r -t notmpfs,nosysfs,nodevtmpfs,noproc
>
> What we expect is that the rootfs (/) will fail, but be remounted read only.
> This doesn't seem to be happening because we get messages about recovery
> needed during the next boot.
>
> We can work around it by adding
>
> mount -n -o remount,ro /
>
> I have a report that umount works as expected in version 2.21.2, but not in
> 2.22.2 or later. I this a misunderstanding about umount or a bug?
Please, run
LIBMOUNT_DEBUG=0xffff umount -a -d -r -t notmpfs,nosysfs,nodevtmpfs,noproc &> umount.log
and send me the log file.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
prev parent reply other threads:[~2013-05-13 12:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-10 4:05 umount -r Bruce Dubbs
2013-05-13 12:41 ` Karel Zak [this message]
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=20130513124010.GA1865@x2.net.home \
--to=kzak@redhat.com \
--cc=bruce.dubbs@gmail.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