https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235388
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #6 from [email protected] --- I also URGE the Core Team to revert the behaviour. Suppose you host a bunch of FreeBSD guests on a hypervisor. Seasoned ZFS administrator would create three separate virtual storage devices for each virtual machine: one for ESP, another one for root ZFS pool and third for swap. First VSD will be partitioned and contain only the ESP while two others will be not! So, what do you do when you will have to expand swap space for VM in the setup described above? Right. You will shutdown VM, increase underlying storage and boot VM up. What will you have to do if you made swap space partitioned, even on separate VSD? Right, you will have to extend partition. How you will do it? swapoff? Too bad. But things become worse if you will have to expand root file system space for VM. If you made your root pool on raw unpartitioned device, especially with "autoexpand=on" set, you will shutdown VM, increase underlying storage and boot VM up. What will you do with ZFS on partition? Unmount root filesystem? ZFS rule of thumb: ZFS is self-contained. If you ever able to use raw disks -- use them. -- You are receiving this mail because: You are the assignee for the bug.
