GUI doesn't prevent footshooting when deleting zpool/volume when child datasets/zvols/etc exist
|Reported by:||gcooper||Owned by:||william|
Currently if I do something like:
- Create a zpool named tank.
- Create a dataset named foo.
- Create a zvol named bar.
- Go and delete tank.
It doesn't warn me that I'm doing something potentially harmful unless a service is using the volume. Given that the actual layout isn't properly articulated today in the GUI (that tank is the container for foo and bar), the user may think they're doing something benign by nuking tank, but instead are also nuking foo and bar if they're not in use.
What I'm proposing is a dialog that says:
You're deleting tank. It's currently being used by the following items:
- Datasets: foo
- ZVols: bar
- Services: cifs, nfs, etc
Enumerating each of the individual services in use by the child datasets and zvols might be a good idea with an expanding '+' tree option, BUT that seems like it would overcomplicate how things are presented to end-users.