diff options
| author | Giuseppe Scrivano <gscrivan@redhat.com> | 2022-04-28 11:39:12 +0200 |
|---|---|---|
| committer | Matthew Heon <matthew.heon@pm.me> | 2022-05-03 13:36:00 -0400 |
| commit | e5d6b6b0a2cfdbb21506b8f5e741cf719c149cb4 (patch) | |
| tree | 25b5d7c4451f702c7c7162116139ac6297888744 /libpod/volume.go | |
| parent | 77f147468c4bf514dd5a2951a29128f226d1186c (diff) | |
| download | podman-e5d6b6b0a2cfdbb21506b8f5e741cf719c149cb4.tar.gz podman-e5d6b6b0a2cfdbb21506b8f5e741cf719c149cb4.tar.bz2 podman-e5d6b6b0a2cfdbb21506b8f5e741cf719c149cb4.zip | |
volume: add new option -o o=noquota
add a new option to completely disable xfs quota usage for a volume.
xfs quota set on a volume, even just for tracking disk usage, can
cause weird errors if the volume is later re-used by a container with
a different quota projid. More specifically, link(2) and rename(2)
might fail with EXDEV if the source file has a projid that is
different from the parent directory.
To prevent such kind of issues, the volume should be created
beforehand with `podman volume create -o o=noquota $ID`
Closes: https://github.com/containers/podman/issues/14049
Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
Diffstat (limited to 'libpod/volume.go')
| -rw-r--r-- | libpod/volume.go | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/libpod/volume.go b/libpod/volume.go index bffafdc15..ab461a37f 100644 --- a/libpod/volume.go +++ b/libpod/volume.go @@ -52,6 +52,9 @@ type VolumeConfig struct { Size uint64 `json:"size"` // Inodes maximum of the volume. Inodes uint64 `json:"inodes"` + // DisableQuota indicates that the volume should completely disable using any + // quota tracking. + DisableQuota bool `json:"disableQuota,omitempty"` } // VolumeState holds the volume's mutable state. |