From: Steve Dickson <SteveD@RedHat.com>
To: Lennart Poettering <mzxreary@0pointer.de>
Cc: NeilBrown <neilb@suse.com>,
systemd-devel@freedesktop.org, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] nfs.man: document incompatibility between "bg" option and systemd.
Date: Wed, 7 Jun 2017 06:04:12 -0400 [thread overview]
Message-ID: <5132dc9e-42a4-feab-2ee8-fcecf1a1cf1f@RedHat.com> (raw)
In-Reply-To: <20170607081257.GH27006@gardel-login>
On 06/07/2017 04:12 AM, Lennart Poettering wrote:
> On Tue, 06.06.17 14:07, Steve Dickson (SteveD@RedHat.com) wrote:
>
>> Hello,
>>
>> On 05/29/2017 06:19 PM, NeilBrown wrote:
>>>
>>> Systemd does not, and will not, support "bg" correctly.
>>> It has other, better, ways to handle "background" mounting.
>> The only problem with this is bg mounts still work at least
>> up to 4.11 kernel...
>>
>> It appears there is a problem with a 4.12 kernel. The mount no
>> longer errors out with ECONNREFUSED it just hangs in the
>> kernel trying forever... It sounds like a bug to me but
>> maybe that change was intentional.. Anna?? Trond???
>>
>> So I'm a bit hesitant to commit this since not accurate, yet.
>>
>> Finally, the whole idea of systemd randomly/silently
>> strip off mount options is crazy... IMHO...
>>
>> Just because a concept that has been around for years
>> does not fix well in the systemd world it gets
>> rip out??? IDK... but I think we can do better than that.
>
> Well "bg" doesn't really work on systemd systems, and this was never
> different, hence I think it's only fair to document that it is
> incompatible with systemd.
I'm seeing it work just fine...
/etc/fstab: nfssrv:/home/tmp /mnt/tmp nfs bg 0 0
nfssrv is down
reboot client
login to client
# ps ax | grep mount
980 ? Ss 0:00 /sbin/mount.nfs nfssrv:/home/tmp /mnt/tmp -o rw,bg
> In addition, I have the suspicion it is not
> used very widely, since I never actually got complaints about it.
Since it seems to be still working we probably would not hear
any complaints about it...
steved.
next prev parent reply other threads:[~2017-06-07 10:04 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 2:46 systemd and NFS "bg" mounts NeilBrown
2017-05-29 13:38 ` [systemd-devel] " Lennart Poettering
2017-05-29 22:05 ` NeilBrown
2017-05-29 22:19 ` [PATCH] nfs.man: document incompatibility between "bg" option and systemd NeilBrown
2017-05-30 4:47 ` Niels de Vos
2017-05-30 7:40 ` [systemd-devel] " Michael Biebl
2017-05-30 8:55 ` NeilBrown
2017-05-30 9:15 ` Michael Biebl
2017-05-30 12:45 ` Lennart Poettering
2017-05-30 12:43 ` Lennart Poettering
2017-06-06 18:07 ` Steve Dickson
2017-06-06 19:57 ` [systemd-devel] " Michael Biebl
2017-06-07 8:13 ` Lennart Poettering
2017-06-07 9:42 ` Steve Dickson
2017-06-06 21:49 ` NeilBrown
2017-06-07 10:08 ` Steve Dickson
2017-06-07 12:02 ` Lennart Poettering
2017-06-07 19:48 ` Steve Dickson
2017-06-08 5:16 ` NeilBrown
2017-06-08 15:36 ` J. Bruce Fields
2017-06-08 21:54 ` NeilBrown
2017-06-08 20:24 ` Steve Dickson
2017-06-07 8:12 ` Lennart Poettering
2017-06-07 10:04 ` Steve Dickson [this message]
2017-06-07 16:08 ` J. Bruce Fields
2017-06-08 20:34 ` Steve Dickson
2017-07-04 22:20 ` NeilBrown
2017-07-10 15:26 ` Steve Dickson
2017-07-10 22:56 ` NeilBrown
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=5132dc9e-42a4-feab-2ee8-fcecf1a1cf1f@RedHat.com \
--to=steved@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=mzxreary@0pointer.de \
--cc=neilb@suse.com \
--cc=systemd-devel@freedesktop.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;
as well as URLs for NNTP newsgroup(s).