From: Felix Miata <mrmazda@earthlink.net>
To: linux-nfs@vger.kernel.org
Subject: Re: system updating routinely umounts "manual" nfs mounts
Date: Thu, 29 May 2014 05:45:24 -0400 [thread overview]
Message-ID: <538701B4.6030207@earthlink.net> (raw)
In-Reply-To: <20140527205527.GC32160@fieldses.org>
On 2014-05-27 16:55 (GMT-0400) J. Bruce Fields composed:
> On Sun, May 25, 2014 at 02:49:54PM -0400, Felix Miata wrote:
>> This has been happening here for several months or more in devel
>> distro versions Factory and IIRC Cauldron and Rawhide.
>> Maybe others' manual nfs mounts are more "manual" than mine are.
>> Mine are actually a group of noauto fstab entries I enable via
>> script when I want them active. All of my installations are on real
>> x86 hardware, some 32 and others 64 bit. I'm guessing what's going
>> on is systemd updates syncing /proc/mounts to fstab, oblivious to
>> the manual post-init mount processes having taken place, but this
>> certainly could be nfs evolutionary fallout or something else I know
>> nothing about. Is this happening to others? Expected? My search of
>> nfs component @bugzilla.kernel.org produced nothing on apparent
>> point.
> The kernel certainly isn't going to unmount things for you like this, so
> this is a question for the distro or systemd maintainers or something.
Couldn't make it happen in Cauldron or Rawhide, so filed openSUSE bug:
https://bugzilla.novell.com/show_bug.cgi?id=880208
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
prev parent reply other threads:[~2014-05-29 9:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-25 18:49 system updating routinely umounts "manual" nfs mounts Felix Miata
2014-05-27 20:55 ` J. Bruce Fields
2014-05-29 9:45 ` Felix Miata [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=538701B4.6030207@earthlink.net \
--to=mrmazda@earthlink.net \
--cc=linux-nfs@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.