Disk Experiment

The Disk experiment fills up a block device by writing random data to files at the destination specified by --dir. The number of files created is directly related to the number of --workers specified when configuring the experiment.

‍

Options

‍

Container disk experiments

• The Disk experiment can target the ephemeral storage (e.g. <code>rootfs</code>) or externally mounted storage attached to your container, such as a directory backed by a Kubernetes PersistentVolumeClaim.
• If a target of a Disk experiment is killed during while the experiment is running, Gremlin relies on the garbage collection routines of the container platform to remove any impact to the terminated container's ephemeral storage. In most cases this is done automatically by the container platform on an as-needed basis. For Kubernetes users, see Garbage collection of unused containers and images. Impact to external volumes mounted by the target are automatically cleaned up when the target terminates.
• The Disk experiment for containers is not supported with the following legacy container drivers: docker-runc, containerd-runc, crio-runc, and docker (legacy). Users should use the latest linux container drivers. See Declare Container Driver.

‍

Microsoft Azure disk experiments

Azure Windows instances may throttle disk I/O such that large disk experiments will take an excessive amount of time to complete.

‍

Privileges required

‍