[arch-general] Pacman and Systemd's automount
Hello! I have enabled systemd, and since then, I see the following: [root@guillelinux ~]# LANG=C pacman -Syu :: Synchronizing package databases... core is up to date extra is up to date community is up to date multilib is up to date :: Starting full system upgrade... resolving dependencies... looking for inter-conflicts... Targets (1): openssh-6.1p1-2 Total Download Size: 0.53 MiB Total Installed Size: 2.62 MiB Net Upgrade Size: 0.00 MiB Proceed with installation? [Y/n] y :: Retrieving packages from core... openssh-6.1p1-2-x86_64 540.5 KiB 2034K/s 00:00 [################################################] 100% (1/1) checking package integrity [################################################] 100% (1/1) loading package files [################################################] 100% (1/1) checking for file conflicts [################################################] 100% warning: could not get filesystem information for /mnt/atlantac: No such device warning: could not get filesystem information for /mnt/atlantad: No such device warning: could not get filesystem information for /mnt/asusc: No such device warning: could not get filesystem information for /mnt/asusd: No such device warning: could not get filesystem information for /mnt/asusf: No such device (1/1) checking available disk space [################################################] 100% (1/1) upgrading openssh [################################################] 100% It seems that pacman tries to access or check every mounted filesystem in my PC. It is not very important, except when I'm out of the office. I have defined some mount points like this: 172.31.217.10:/vol/vol0 /mnt/up nfs noauto,x-systemd.automount,defaults 0 0 When pacman reaches this filesystems, that obviously can't be accessed from outside the office, it hangs forever. I have to issue Systemctl stop mnt-systemd.up And then it works. Why is pacman trying to access all the mountpoints? Best Regards, Guillermo Leira
On Sep 4, 2012 11:04 AM, "Guillermo Leira" <gleira@gleira.com> wrote:
Hello!
I have enabled systemd, and since then, I see the following:
[root@guillelinux ~]# LANG=C pacman -Syu :: Synchronizing package databases... core is up to date extra is up to date community is up to date multilib is up to date :: Starting full system upgrade... resolving dependencies... looking for inter-conflicts...
Targets (1): openssh-6.1p1-2
Total Download Size: 0.53 MiB Total Installed Size: 2.62 MiB Net Upgrade Size: 0.00 MiB
Proceed with installation? [Y/n] y :: Retrieving packages from core... openssh-6.1p1-2-x86_64 540.5 KiB 2034K/s 00:00 [################################################] 100% (1/1) checking package integrity [################################################] 100% (1/1) loading package files [################################################] 100% (1/1) checking for file conflicts [################################################] 100% warning: could not get filesystem information for /mnt/atlantac: No such device warning: could not get filesystem information for /mnt/atlantad: No such device warning: could not get filesystem information for /mnt/asusc: No such
device
warning: could not get filesystem information for /mnt/asusd: No such device warning: could not get filesystem information for /mnt/asusf: No such device (1/1) checking available disk space [################################################] 100% (1/1) upgrading openssh [################################################] 100%
It seems that pacman tries to access or check every mounted filesystem in my PC. It is not very important, except when I'm out of the office. I have defined some mount points like this:
172.31.217.10:/vol/vol0 /mnt/up nfs noauto,x-systemd.automount,defaults 0 0
When pacman reaches this filesystems, that obviously can't be accessed from outside the office, it hangs forever. I have to issue
Systemctl stop mnt-systemd.up
And then it works.
Why is pacman trying to access all the mountpoints?
Best Regards,
Guillermo Leira
Because you you have Check space enabled in pacman.conf
On 04/09/2012 11:08 AM, Daniel Wallace wrote:
On Sep 4, 2012 11:04 AM, "Guillermo Leira" <gleira@gleira.com> wrote:
Hello!
I have enabled systemd, and since then, I see the following:
[root@guillelinux ~]# LANG=C pacman -Syu :: Synchronizing package databases... core is up to date extra is up to date community is up to date multilib is up to date :: Starting full system upgrade... resolving dependencies... looking for inter-conflicts...
Targets (1): openssh-6.1p1-2
Total Download Size: 0.53 MiB Total Installed Size: 2.62 MiB Net Upgrade Size: 0.00 MiB
Proceed with installation? [Y/n] y :: Retrieving packages from core... openssh-6.1p1-2-x86_64 540.5 KiB 2034K/s 00:00 [################################################] 100% (1/1) checking package integrity [################################################] 100% (1/1) loading package files [################################################] 100% (1/1) checking for file conflicts [################################################] 100% warning: could not get filesystem information for /mnt/atlantac: No such device warning: could not get filesystem information for /mnt/atlantad: No such device warning: could not get filesystem information for /mnt/asusc: No such device warning: could not get filesystem information for /mnt/asusd: No such device warning: could not get filesystem information for /mnt/asusf: No such device (1/1) checking available disk space [################################################] 100% (1/1) upgrading openssh [################################################] 100%
It seems that pacman tries to access or check every mounted filesystem in my PC. It is not very important, except when I'm out of the office. I have defined some mount points like this:
172.31.217.10:/vol/vol0 /mnt/up nfs noauto,x-systemd.automount,defaults 0 0
When pacman reaches this filesystems, that obviously can't be accessed from outside the office, it hangs forever. I have to issue
Systemctl stop mnt-systemd.up
And then it works.
Why is pacman trying to access all the mountpoints?
Best Regards,
Guillermo Leira
Because you you have Check space enabled in pacman.conf As well, I would suggest adding x-systemd.device-timeout to your fstab, so it doesn't hang forever.
Because you you have Check space enabled in pacman.conf As well, I would suggest adding x-systemd.device-timeout to your fstab, so it doesn't hang forever.
What's the reason for the default being hang forever? -- _______________________________________________________________________ 'Write programs that do one thing and do it well. Write programs to work together. Write programs to handle text streams, because that is a universal interface' (Doug McIlroy) _______________________________________________________________________
On Wed, 5 Sep 2012 12:11:27 +0100 Kevin Chadwick <ma1l1ists@yahoo.co.uk> wrote:
Because you you have Check space enabled in pacman.conf As well, I would suggest adding x-systemd.device-timeout to your fstab, so it doesn't hang forever.
What's the reason for the default being hang forever?
I would imagine the reason is to avoid making assumptions about how long it takes every device to come up. See also: halting problem. You could argue that some long default is sensible, but this is not the systemd development list... -- John K Pate http://jkpate.net/ The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336.
-----Mensaje original----- De: arch-general [mailto:arch-general-bounces@archlinux.org] En nombre de Daniel Wallace Enviado el: martes, 04 de septiembre de 2012 17:09 Para: General Discussion about Arch Linux Asunto: Re: [arch-general] Pacman and Systemd's automount
On Sep 4, 2012 11:04 AM, "Guillermo Leira" <gleira@gleira.com> wrote:
[...]
It seems that pacman tries to access or check every mounted filesystem
in my
PC. It is not very important, except when I'm out of the office. I have defined some mount points like this:
172.31.217.10:/vol/vol0 /mnt/up nfs noauto,x-systemd.automount,defaults 0 0
When pacman reaches this filesystems, that obviously can't be accessed from outside the office, it hangs forever. I have to issue
Systemctl stop mnt-systemd.up
And then it works.
Why is pacman trying to access all the mountpoints?
Because you you have Check space enabled in pacman.conf
And... It has to check -every- filesystem? Ok, I suppose I'll disable that option, but I don't understand... :-) I thought that it would check only the filesystems that it was going to write to. Thanks, Guillermo
On Tue, Sep 04, 2012 at 10:08:32PM +0200, Guillermo Leira wrote:
-----Mensaje original----- De: arch-general [mailto:arch-general-bounces@archlinux.org] En nombre de Daniel Wallace Enviado el: martes, 04 de septiembre de 2012 17:09 Para: General Discussion about Arch Linux Asunto: Re: [arch-general] Pacman and Systemd's automount
On Sep 4, 2012 11:04 AM, "Guillermo Leira" <gleira@gleira.com> wrote:
[...]
It seems that pacman tries to access or check every mounted filesystem
in my
PC. It is not very important, except when I'm out of the office. I have defined some mount points like this:
172.31.217.10:/vol/vol0 /mnt/up nfs noauto,x-systemd.automount,defaults 0 0
When pacman reaches this filesystems, that obviously can't be accessed from outside the office, it hangs forever. I have to issue
Systemctl stop mnt-systemd.up
And then it works.
Why is pacman trying to access all the mountpoints?
Because you you have Check space enabled in pacman.conf
And... It has to check -every- filesystem?
Ok, I suppose I'll disable that option, but I don't understand... :-)
I thought that it would check only the filesystems that it was going to write to.
Thanks,
Guillermo
it is fixed with this patch http://projects.archlinux.org/pacman.git/commit/?id=e183522e3168 in pacman-git -- Daniel Wallace Archlinux Trusted User (gtmanfred) Georgia Institute of Technology
-----Mensaje original----- De: arch-general [mailto:arch-general-bounces@archlinux.org] En nombre de Daniel Wallace Enviado el: miércoles, 05 de septiembre de 2012 0:33 Para: General Discussion about Arch Linux Asunto: Re: [arch-general] Pacman and Systemd's automount
On Tue, Sep 04, 2012 at 10:08:32PM +0200, Guillermo Leira wrote:
-----Mensaje original----- De: arch-general [mailto:arch-general-bounces@archlinux.org] En nombre de Daniel Wallace Enviado el: martes, 04 de septiembre de 2012 17:09 Para: General Discussion about Arch Linux Asunto: Re: [arch-general] Pacman and Systemd's automount
[...]
Why is pacman trying to access all the mountpoints?
Because you you have Check space enabled in pacman.conf
And... It has to check -every- filesystem?
Ok, I suppose I'll disable that option, but I don't understand... :-)
I thought that it would check only the filesystems that it was going to write to.
Thanks,
Guillermo
it is fixed with this patch http://projects.archlinux.org/pacman.git/commit/?id=e183522e3168 in pacman-git
-- Daniel Wallace Archlinux Trusted User (gtmanfred) Georgia Institute of Technology
Great, thank you!!! I'll wait for new version, then. :-) Guillermo
participants (5)
-
Daniel Wallace
-
Guillermo Leira
-
John K Pate
-
Kevin Chadwick
-
Stephen E. Baker