mirror of
https://github.com/ceph/ceph-csi.git
synced 2024-12-18 11:00:25 +00:00
f60a358007
When a volume has AccessType=Block and is encrypted with LUKS, a resize of the filesystem on the (decrypted) block-device is attempted. This should not be done, as the application that requested the Block volume is the only authoritive reader/writer of the data. In particular VirtualMachines that use RBD volumes as a disk, usually have a partition table on the disk, instead of only a single filesystem. The `resizefs` command will not be able to resize the filesystem on the block-device, as it is a partition table. When `resizefs` fails during NodeStageVolume, the volume is unstaged and an error is returned. Resizing an encrypted block-device requires `cryptsetup resize` so that the LUKS header on the RBD-image is updated with the correct size. But there is no need to call `resizefs` in this case. Fixes: #3945 Signed-off-by: Niels de Vos <ndevos@ibm.com> |
||
|---|---|---|
| .. | ||
| driver | ||
| clone.go | ||
| controllerserver_test.go | ||
| controllerserver.go | ||
| diskusage.go | ||
| encryption_test.go | ||
| encryption.go | ||
| errors.go | ||
| globals.go | ||
| identityserver.go | ||
| migration_test.go | ||
| migration.go | ||
| mirror.go | ||
| nodeserver_test.go | ||
| nodeserver.go | ||
| rbd_attach_test.go | ||
| rbd_attach.go | ||
| rbd_healer.go | ||
| rbd_journal.go | ||
| rbd_util_test.go | ||
| rbd_util.go | ||
| replication.go | ||
| snapshot.go | ||