csi-driver-nfs

History

Jan Safranek 59fe400d43 <carry>: Umount volumes with force In 4.5, NFS driver pod used 'clientaddr=<pod ip>' as a mount option. When such pod restarts, it gets a different IP address and volumes mounted by the old pod are basically broken - all operations (stat, umount) will just hang forever. Therefore: 1. Do not use IsLikelyNotMountPoint - it runs stat() on the volume, which could hang forever. Read /etc/mounts instead. 2. Use "umount -f" to forcefully remove NFS mount. Carry at least for whole OCP 4.6, where we need to support move from 4.5.	2020-08-19 16:57:20 +02:00
..
nfs	<carry>: Umount volumes with force	2020-08-19 16:57:20 +02:00

Jan Safranek 59fe400d43 <carry>: Umount volumes with force

In 4.5, NFS driver pod used 'clientaddr=<pod ip>' as a mount option.
When such pod restarts, it gets a different IP address and volumes mounted
by the old pod are basically broken - all operations (stat, umount) will
just hang forever.

Therefore:

1. Do not use IsLikelyNotMountPoint - it runs stat() on the volume, which
could hang forever. Read /etc/mounts instead.

2. Use "umount -f" to forcefully remove NFS mount.

Carry at least for whole OCP 4.6, where we need to support move from 4.5.

2020-08-19 16:57:20 +02:00

nfs

<carry>: Umount volumes with force

2020-08-19 16:57:20 +02:00