Re: automount requests

[Greg Woods <greg@xxxxxxxxxxxxxx>]

On Wed, Dec 30, 2020 at 11:04 PM Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote:

On Wed, Dec 30, 2020 at 10:12 AM Greg Woods <greg@xxxxxxxxxxxxxx> wrote:

> pub.automount: Got automount request for /pub, triggered by 242640 (PT3122): 1 Time(s)
>
> I want to determine why this is happening, because the drive containing /pub (on a different machine mounted via NFS)  is spun down when idle, and these events are likely causing it to spin up. My understanding is that the part inside the parentheses is the command name of the process that triggered it, but I don't know what the "PT" syntax means.
>

One of those should be PID.

Yes. The format is  "Got automount request for /pub, triggered by #PID# (#command#): 1 Time(s)

I suppose I should provide more info. /pub is a place where I store a bunch of stuff. In particular there are our photo and music collections, and rsync'ed Fedora repos (I rsync F32 and F33 repos once a day, then I use the local repo to perform updates on my 6 Fedora systems). 

The problem here is that, by the time I see one of these entries and investigate, the PID is for a process that is long gone, and I'm not getting any useful info about what command is triggering this. 

As an example, here is a message that is the result of a known access (doing a "dnf update"):

pub.automount: Got automount request for /pub, triggered by 253560 (dnf): 1 Time(s)

Again, process 253560 is long gone, but at least I know that this automount was triggered by a dnf command. When the command is "PT3122", then I have no clue what triggered this automount. And the vast majority of these automount triggers do not have useful information about what command triggered it. I guess what I really want to know is if there is anywhere I can look for more information, or in general if there is any way to investigate this.

The machine that is producing these logs is my main Fedora server. It is NOT the server for the /pub disk, that is on a Raspberry Pi (NFS-mounted from that Pi server to this one), so these aren't NFS accesses from another system. If I look at my desktop system, which also automounts /pub from the Pi server, all of the similar entries do specify the command, for example "journalctl | grep /pub" snippet:

Dec 14 12:08:23 snowcrash.gregandeva.net systemd[1]: pub.automount: Got automount request for /pub, triggered by 1189068 (k3b)
Dec 14 12:08:23 snowcrash.gregandeva.net systemd[1]: Mounting /pub...
Dec 14 12:08:23 snowcrash.gregandeva.net systemd[1]: Mounted /pub.
Dec 14 12:09:24 snowcrash.gregandeva.net systemd[1]: Unmounting /pub...
Dec 14 12:09:24 snowcrash.gregandeva.net systemd[1]: Unmounted /pub.
Dec 14 16:24:26 snowcrash.gregandeva.net systemd[1]: pub.automount: Got automount request for /pub, triggered by 1210113 (dnf)
Dec 14 16:24:26 snowcrash.gregandeva.net systemd[1]: Mounting /pub...
Dec 14 16:24:26 snowcrash.gregandeva.net systemd[1]: Mounted /pub.
Dec 14 16:25:27 snowcrash.gregandeva.net systemd[1]: Unmounting /pub...
Dec 14 16:25:27 snowcrash.gregandeva.net systemd[1]: Unmounted /pub.

I do not see any entries that just list PT#### as the command on the desktop system. On the server, almost all of them are.

--Greg

_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx