diff options
| author | Hemant Kumar <hekumar@redhat.com> | 2017-07-23 12:52:40 -0400 |
|---|---|---|
| committer | Hemant Kumar <hekumar@redhat.com> | 2017-07-23 12:52:40 -0400 |
| commit | 73d26e8916202f6e1f411c5e7d98e37e0a19073e (patch) | |
| tree | 662b562c4c0404604230a8c8b43c739cfd014287 | |
| parent | a8fed8c733341611301a60e04bcd6eaf266a07c6 (diff) | |
Expand of how actual file system resize performed
| -rw-r--r-- | contributors/design-proposals/grow-volume-size.md | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/contributors/design-proposals/grow-volume-size.md b/contributors/design-proposals/grow-volume-size.md index 7fb94767..ca3b7851 100644 --- a/contributors/design-proposals/grow-volume-size.md +++ b/contributors/design-proposals/grow-volume-size.md @@ -134,6 +134,11 @@ online file system resize if volume type and file system supports it - we are le * When calling `MountDevice` or `Setup` call of volume plugin, volume manager will in addition compare `pv.spec.capacity` and `pvc.status.capacity` and if `pv.spec.capacity` is greater than `pvc.status.spec.capacity` then volume manager will additionally resize the file system of volume. * The call to resize file system will be performed inside `operation_generator.GenerateMountVolumeFunc`. `VolumeToMount` struct will be enhanced to store PVC as well. +* The flow of file system resize will be as follow: + * Perform a resize based on file system used inside block device. + * If resize succeeds, proceed with mounting the device as usual. + * If resize failed with an error that shows no file system exists on the device, then log a warning and proceed with format and mount. + * If resize failed with any other error then fail the mount operation. * Any errors during file system resize will be added as *events* to Pod object and mount operation will be failed. * If there are any errors during file system resize `pvc.Status.Conditions` will be updated with `ResizeFailed: True`. Any errors will be added to `Conditions` field. |