NFS server broken
Ste
151 Posts
September 25, 2025, 6:42 amQuote from Ste on September 25, 2025, 6:42 amOk, in the meanwhile i will try to recover the data mounting the ceph filesystem, is there a particular procedure to follow ?
Second question: do you think that upgrading to version 4.0 could fix this issue, without dedicating too much time to this problem ?
Thanks, Ste
ADDED: I studied a bit and found the command should be:
sudo mount -t ceph 10.220.12.45:6789:/ /mnt/cephfs -o name=client.admin,secret=AQBexxxxxxxxxxxxxxxxxxxxxxxx
but the problem is that the monitors are listening on the internal private network 192.168.110.0/24, and they are phisically separated. How can i solve this ?
Ok, in the meanwhile i will try to recover the data mounting the ceph filesystem, is there a particular procedure to follow ?
Second question: do you think that upgrading to version 4.0 could fix this issue, without dedicating too much time to this problem ?
Thanks, Ste
ADDED: I studied a bit and found the command should be:
sudo mount -t ceph 10.220.12.45:6789:/ /mnt/cephfs -o name=client.admin,secret=AQBexxxxxxxxxxxxxxxxxxxxxxxx
but the problem is that the monitors are listening on the internal private network 192.168.110.0/24, and they are phisically separated. How can i solve this ?
Last edited on September 25, 2025, 9:46 am by Ste · #21
admin
3,054 Posts
September 25, 2025, 10:12 pmQuote from admin on September 25, 2025, 10:12 pmin ceph, a ceph client needs to access monitors and osds directly, it needs to be on same network.
cannot say upgrade to 4.0 will solve your particular issue, as even older versions do have nfs working correctly. i our tests we test upgrades from versions as early as 2.3 and we have no issues with nfs.
in ceph, a ceph client needs to access monitors and osds directly, it needs to be on same network.
cannot say upgrade to 4.0 will solve your particular issue, as even older versions do have nfs working correctly. i our tests we test upgrades from versions as early as 2.3 and we have no issues with nfs.
admin
3,054 Posts
November 5, 2025, 2:43 pmQuote from admin on November 5, 2025, 2:43 pmOn nodes running NFS, do the following:
apt install fuse3
apt install podman
systemctl stop petasan-nfs-server
rm -r /var/lib/containers/storage/*
rm /etc/containers/storage.conf
podman system reset
systemctl restart petasan-nfs-server
On nodes running NFS, do the following:
apt install fuse3
apt install podman
systemctl stop petasan-nfs-server
rm -r /var/lib/containers/storage/*
rm /etc/containers/storage.conf
podman system reset
systemctl restart petasan-nfs-server
NFS server broken
Ste
151 Posts
Quote from Ste on September 25, 2025, 6:42 amOk, in the meanwhile i will try to recover the data mounting the ceph filesystem, is there a particular procedure to follow ?
Second question: do you think that upgrading to version 4.0 could fix this issue, without dedicating too much time to this problem ?
Thanks, Ste
ADDED: I studied a bit and found the command should be:
sudo mount -t ceph 10.220.12.45:6789:/ /mnt/cephfs -o name=client.admin,secret=AQBexxxxxxxxxxxxxxxxxxxxxxxx
but the problem is that the monitors are listening on the internal private network 192.168.110.0/24, and they are phisically separated. How can i solve this ?
Ok, in the meanwhile i will try to recover the data mounting the ceph filesystem, is there a particular procedure to follow ?
Second question: do you think that upgrading to version 4.0 could fix this issue, without dedicating too much time to this problem ?
Thanks, Ste
ADDED: I studied a bit and found the command should be:
sudo mount -t ceph 10.220.12.45:6789:/ /mnt/cephfs -o name=client.admin,secret=AQBexxxxxxxxxxxxxxxxxxxxxxxx
but the problem is that the monitors are listening on the internal private network 192.168.110.0/24, and they are phisically separated. How can i solve this ?
admin
3,054 Posts
Quote from admin on September 25, 2025, 10:12 pmin ceph, a ceph client needs to access monitors and osds directly, it needs to be on same network.
cannot say upgrade to 4.0 will solve your particular issue, as even older versions do have nfs working correctly. i our tests we test upgrades from versions as early as 2.3 and we have no issues with nfs.
in ceph, a ceph client needs to access monitors and osds directly, it needs to be on same network.
cannot say upgrade to 4.0 will solve your particular issue, as even older versions do have nfs working correctly. i our tests we test upgrades from versions as early as 2.3 and we have no issues with nfs.
admin
3,054 Posts
Quote from admin on November 5, 2025, 2:43 pmOn nodes running NFS, do the following:
apt install fuse3
apt install podman
systemctl stop petasan-nfs-server
rm -r /var/lib/containers/storage/*
rm /etc/containers/storage.conf
podman system reset
systemctl restart petasan-nfs-server
On nodes running NFS, do the following:
apt install fuse3
apt install podman
systemctl stop petasan-nfs-server
rm -r /var/lib/containers/storage/*
rm /etc/containers/storage.conf
podman system reset
systemctl restart petasan-nfs-server