On 2020-01-15 11:05, Strahil Nikolov wrote: > On January 13, 2020 5:40:06 AM GMT+02:00, Nick Holland > <n...@holland-consulting.net> wrote: >>On 2020-01-12 15:39, Antoine Jacoutot wrote: >>> Sounds like something is keeping your fs busy. Could be gio-kqueue, >>do you have glib2 installed? >> >>That would be my first guess, too -- it's not unmounting because it >>shouldn't. But ... this is a VERY single purpose machine (backups >>via rsync --link-dest), and the only third party package is rsync >>and my scripts to do the backups. X is installed, but not running. >> >>$ pkg_info >>intel-firmware-20191115p0v0 microcode update binaries for Intel CPUs >>inteldrm-firmware-20181218 firmware binary images for inteldrm(4) >>driver >>quirks-3.216 exceptions to pkg_add rules >>rsync-3.1.3 mirroring/synchronization over low bandwidth links >>vmm-firmware-1.11.0p2 firmware binary images for vmm(4) driver >> >>I was careful to access the amd mounts by ls <fullpathname>, while >>sitting in my home directory, which is NOT part of the amd, so I >>didn't have a task under a doas or su camped out on the amd vols. >> >>I've tesed a lot of ways, but I just did an upgrade to -current and >>immediately "looked" at the amd mount, so even my backup scripts >>haven't run. >> >>Plus -- as a control, /v/2 has absolutely nothing on it, and it >>behaves the same way. Not that something couldn't camp out on the >>empty file system, but not much reason for something to do so. >> >>Thanks for looking! >> >>Nick. >> >> >>>  >>> Antoine >>> >>>> On 13 Jan 2020, at 06:01, Nick Holland <n...@holland-consulting.net> >>wrote: >>>> >>>> Hiya. >>>> >>>> I'd like to use amd(8) to automatically mount and dismount local >>file >>>> systems. The file systems in question are big, lots of complicated >>>> links, lots of files, and take a while to fsck if the power goes out >>>> unexpectedly, and are used relatively rarely (maybe an hour a day). >>>> Sounds like a perfect job for amd(8)! >>>> >>>> The file systems in question are mounted to /v/1 and /v/2 >>>> >>>> I've got the following set up: >>>> >>>> $ cat /etc/rc.conf.local >> >>>> amd_flags=-l syslog -x all -c 10 -w 10 >>>> lockd_flags= >>>> portmap_flags= >>>> >>>> $ cat /etc/amd/master >> >>>> /v amd.v >>>> >>>> $ cat /etc/amd/amd.v >>>> 1 type:=ufs;dev:=/dev/sd2i >>>> 2 type:=ufs;dev:=/dev/sd2j >>>> >>>> >>>> AND....it works! >>>> >>>> start the system up, I get this: >>>> >>>> $ df >>>> Filesystem 512-blocks Used Avail Capacity Mounted on >>>> /dev/sd2a 1011676 203812 757284 21% / >>>> /dev/sd2h 10319836 48 9803800 0% /home >>>> /dev/sd2f 4136828 20 3929968 0% /tmp >>>> /dev/sd2d 8264188 2369920 5481060 30% /usr >>>> /dev/sd2e 2065116 2104 1959760 0% /usr/local >>>> /dev/sd2g 4136828 64920 3865068 2% /var >>>> amd:36583 0 0 0 100% /v >>>> >>>> $ ls /v/1/ >>>> [...expected output from files and directories on that file >>system...] >>>> >>>> $ df >>>> Filesystem 1K-blocks Used Avail Capacity Mounted on >>>> /dev/sd2a 505838 83602 396946 17% / >>>> /dev/sd2h 5159918 24 4901900 0% /home >>>> /dev/sd2f 2068414 10 1964984 0% /tmp >>>> /dev/sd2d 4132094 1280264 2645226 33% /usr >>>> /dev/sd2e 1032558 1052 979880 0% /usr/local >>>> /dev/sd2g 2068414 32572 1932422 2% /var >>>> amd:92953 0 0 0 100% /v >>>> /dev/sd2i 2106117872 298739480 1702072504 15% >>/tmp_mnt/dbu/v/1 >>>> >>>> Success!! >>>> well...no. Seems it never umounts the amd file systems. And that >>is >>>> basically the point of this exercise -- to increase the odds that a >>FS >>>> isn't mounted when the power goes out. >>>> >>>> Am I doing something wrong? Do I have inaccurate expectations of >>>> what amd(8) does with local file systems? >>>> >>>> Nick. >>>>
... > Hi Nick, > > Can you test removing '-w 10' from the daemon's flags in order to test with > the default 2min timeout. > > I have a vague feeling that 10 seconds is way too short... You are right -- that was something I tried so I quit having to wait 5+ minutes every time I tried something different, so I stuffed absurdly short timeouts in place for testing, but there was no change. I've reverted those changes, and (as I expected), it is still not unmounting. New: $ cat /etc/rc.conf.local amd_flags=-l syslog -x all lockd_flags= portmap_flags= (the -x all was added to see if amd logged any dismount attempts or why they failed...nothing) So thanks, but ... no change. :-/ Nick.
