Skip to content
This repository has been archived by the owner on Feb 12, 2022. It is now read-only.

Correct the readme note about zvol snapshots #3

Open
Shados opened this issue Apr 24, 2018 · 0 comments
Open

Correct the readme note about zvol snapshots #3

Shados opened this issue Apr 24, 2018 · 0 comments

Comments

@Shados
Copy link

Shados commented Apr 24, 2018

You can snapshot a zvol that occupies 85% of your pool, you just need to change its refreservation to a normal reservation (or remove its reservation entirely, making it a sparse zvol). Both of those have potential risks / consequences in turn, of course, so read the ZFS man page entries for them carefully and give it some thought before doing so.

ZFS uses refreservation by default for zvols because otherwise in a free-space contention scenario you could accidentally run out of space for a zvol due to snapshots, despite thinking you had sufficient space reserved from the beginning. refreservation reserves space in the pool for the dataset without allowing children of that dataset (relevantly here, including snapshots) to consume from that reservation, while a normal reservation will be consumed by child datasets.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant