Groups keyboard shortcuts have been updated
Dismiss
See shortcuts

mount(2) system call failed: Operation canceled after upgrading to 7.4.4

53 views
Skip to first unread message

Paul Jähne

unread,
Aug 22, 2024, 10:28:29 AM8/22/24
to beegfs-user
Hello, I updated from BeeGFS 7.3.1 to 7.4.4 and I got a strange Problem. Only one client was unable to mount BeeGFS after the update. The error was:
$ sudo mount /mnt/beegfs
mount: /mnt/beegfs: mount(2) system call failed: Operation canceled.


I looked into dmesg and there was this error:
beegfs: mount(4044977): The config argument 'connDisableAuthentication' is invalid
beegfs: mount(4044977): Configuration error: Initialization of common objects failed. (Log file may provide additional information.)

/var/log/beegfs-client.log doesn't conatin something related to this.

After commenting the line with connDisableAuthentication = false in /etc/begfs/beegfs-client.conf I got the same error when trying to mount beegfs and this message in dmesg:
beegfs: mount(4059882): The config argument 'connTCPRcvBufSize' is invalid
beegfs: mount(4059882): Configuration error: Initialization of common objects failed. (Log file may provide additional information.)
and this message after commenting the line connTCPRcvBufSize = 0
mount(4067453): The config argument 'connUDPRcvBufSize' is invalid
beegfs: mount(4067453): Configuration error: Initialization of common objects failed. (Log file may provide additional information.)

and after commenting the line connUDPRcvBufSize = 0 mounting beegfs works again:
beegfs: mount(4067515): BeeGFS mount ready.

I couldn't find something in the release notes that might have changed with these parameters and it's strange, that it was only a problem on one client as I use Ansible for the configuration, so the files are identical on all clients.

Waltar

unread,
Aug 22, 2024, 11:03:42 AM8/22/24
to beegfs-user
That looks more to an package update problem one the 1 client as the others are working. Rerun your ansible playbook and if you reboot the client do a "sync" before.

Guan Xin

unread,
Aug 23, 2024, 4:00:26 AM8/23/24
to beegfs-user
Earlier in dmesg there should be a line showing the version of beegfs.ko
Check that beegfs.ko has been upgraded.

If not, modprobe -r beegfs and then upgrade beegfs.ko, then
modprobe beegfs

Guan

Paul Jähne

unread,
Aug 23, 2024, 5:00:16 AM8/23/24
to beegfs-user
Thank you for your suggestions!

@Waltar: I resolved it like you said.

@Guan Xin: I couldn't find something regarding beegfs.ko in my dmesg output. Nethertheless, it mitght help me to diagnose some other problem in the future.
Reply all
Reply to author
Forward
0 new messages