* John Goerzen [200625 00:39]:
>
> On Tue, Jun 23 2020, Chris Hofstaedtler wrote:
>
> > Okay, that would match the suggestion. In this case I'd think this
> > is more a systemd issue than a mount issue - mount passes your mount
> > request to the kernel, and the kernel mounts it. Then something
On Tue, Jun 23 2020, Chris Hofstaedtler wrote:
> Okay, that would match the suggestion. In this case I'd think this
> is more a systemd issue than a mount issue - mount passes your mount
> request to the kernel, and the kernel mounts it. Then something else
> (probably systemd) unmounts it
* John Goerzen [200512 22:45]:
> Sorry about that, Chris. I have tried just now and, rather to my
> surprise, have been unable to duplicate this in order to gather more
> information. I had assumed it would be fairly readily reproducible;
> that is my mistake.
Right. I've asked around, and
On Tue, May 12 2020, Chris Hofstaedtler wrote:
Hi Chris,
> I must say this is a very generic report. To your points 1) and 2)
> I could ask "What did the kernel say at this time, esp. did it claim
> success?", to 3) and 4) I could say "There is also no documentation
> on interactions with other
Hi John,
thanks for your report, however...
* John Goerzen [200512 20:24]:
> There are multiple issues reflected in this report:
>
> 1) That mount failed to properly mount a filesystem;
>
> 2) That it incorrectly said it had mounted it;
>
> 3) That running systemctl daemon-reload fixed the
Package: mount
Version: 2.33.1-0.1
Severity: important
There are multiple issues reflected in this report:
1) That mount failed to properly mount a filesystem;
2) That it incorrectly said it had mounted it;
3) That running systemctl daemon-reload fixed the issue;
4) That neither the mount nor
6 matches
Mail list logo
