I would more vote for a feature to have a zpool level property of /redundancy/ (or something along that) that I can set to /off//(default)|mirror|raidz<level>/ that then enforces zpool add to be supplied a vdev specification of at least (or exactly that) that level of redundancy, else fail with descriptive error message and /not/ be overrideable with -f (since I can change the /redundancy /property if I really want to shoot myself into the foot). This property could be set to the redundancy level used when issuing the initial /zpool create/.
That to fix the problem of adding single-disk vdevs instead of a /partial /implementation of device removal (which would be, should it work for all types of vdevs, a great feature). Gregor Am 04.03.2016 um 07:46 schrieb ilove zfs: > This talk about accidentally adding a non-redundant top level vdev is > a bit bizarre: > > Josephs-MacBook-Pro:zp joe$ sudo zpool add mismatch disk4 > invalid vdev specification > use '-f' to override the following errors: > mismatched replication level: pool uses mirror and new vdev is disk > > Unless you're habitually or reflexively using -f that shouldn't > happen. The error is rather clear. Should we make it -F or -ff > instead? lol > ------------------------------------------- openzfs-developer Archives: https://www.listbox.com/member/archive/274414/=now RSS Feed: https://www.listbox.com/member/archive/rss/274414/28015062-cce53afa Modify Your Subscription: https://www.listbox.com/member/?member_id=28015062&id_secret=28015062-f966d51c Powered by Listbox: http://www.listbox.com
