You can update the server with the mapped rbd and shouldn't see as much as
a blip on your VMs.
On Tue, Sep 26, 2017, 3:32 AM Götz Reinicke
wrote:
> Hi Thanks David & David,
>
> we don’t use the fuse code. And may be I was a bit unclear, but your
> feedback clears some other aspects in that conte
Hi Thanks David & David,
we don’t use the fuse code. And may be I was a bit unclear, but your feedback
clears some other aspects in that context.
I did an update already on our OSD/MONs while a NFS Fileserver still had a rbd
connected and was exporting files (Virtual disks for XEN server) onlin
It depends a bit on how you have the RBDs mapped. If you're mapping them
using krbd, then they don't need to be updated to use the new rbd-fuse or
rbd-nbd code. If you're using one of the latter, then you should schedule
a time to restart the mounts so that they're mapped with the new Ceph
versio
Hi Götz
If you did a rolling upgrade, RBD clients shouldn't have experienced
interrupted IO and therefor IO to NFS exports shouldn't have been affected.
However, in the past when using kernel NFS over kernel RBD, I did have some
lockups when OSDs went down in the cluster so that's something to wat
Hi,
I updated our ceph OSD/MON Nodes from 10.2.7 to 10.2.9 and everything looks
good so far.
Now I was wondering (as I may have forgotten how this works) what will happen
to a NFS server which has the nfs shares on a ceph rbd ? Will the update
interrupt any access to the NFS share or is it th