Dear HPC,
It appears that /dpnc/beegfs is not yet mounted on the login-node following the OS migration of Baobab. Would it be possible to have a look at this?
Note that I have not checked the compute nodes, and that potentially it needs to be mounted for those as well.
All the best,
Paul
Hello @Paul.Coppin
I checked and had no problems:
(baobab)-[alberta@login1 ~]$ df -t beegfs
Filesystem 1K-blocks Used Available Use% Mounted on
beegfs_dpnc 539049799680 535486640640 3563159040 100% /srv/beegfs/dpnc
beegfs_scratch 1617149399040 1320638278144 296511120896 82% /srv/beegfs/scratch
beegfs_home 147639165952 144832774144 2806391808 99% /home
Are you sure the issue is on login node ?
Hi @Adrien.Albert,
Thank you for the quick reply.
I mean the directory: /dpnc/beegfs
not /srv/beegfs
/dpnc/beegfs should point to a ~900TB BeeGFS file system managed by the DPNC department on Baobab, Yggdrasil, and Bamboo. It appears it has not yet been mounted on Baobab following the OS upgrade. If my memory serves correctly, I believe it is usually mounted via NSF through grid06.unige.ch (which acts as the BeeGFS client).
All the best,
Paul
Hello,
Should be OK:
(baobab)-[root@login1 ~]$ ls /dpnc/beegfs/
ams atlas cta dampe etc fast herd neutrino pan share sys usage users
1 Like
Indeed, looks all good now. Thanks!