News for hackers. Stuff that matters.
Re:Linux 5.10 BTRFS performance regression by kefyras on Wednesday December 23, 2020 @10:26AM (#25518514)
> but ZFS doesn't like living on a partitioned disk nearly as much.

Don't know how true is this, since it's not even possible to create a zpool on the whole unpartitioned device on linux. It automatically creates GPT label with zfs and a small efi partition.

Re:Linux 5.10 BTRFS performance regression by zaarn on Wednesday December 23, 2020 @10:32AM (#25518592)
That is true, but I suspect that only happens to protect the zpool against tools like the Windows Repair Install (which likes to attempt repairs on disks without GPT label). Using ZFS on a partition inside a GPT disk tends to lead to a few quirky behaviours, like for example ZFS not always reporting correct SMART data of the device.
Re:Linux 5.10 BTRFS performance regression by fomine3 on Thursday December 24, 2020 @02:26AM (#25525695)
IIRC ZoL `zpool create /dev/disk/by-id/ata-XXX` makes gpt partition table and zfs partition inside it.
Re:Linux 5.10 BTRFS performance regression by zaarn on Thursday December 24, 2020 @06:08AM (#25526554)
A stub table.
Re:Linux 5.10 BTRFS performance regression by rleigh on Thursday December 24, 2020 @03:54AM (#25526021)
It's nonsense. A ZFS pool is created from block devices, and ZFS doesn't care if those are whole discs or partitions.

Every ZFS pool I have is composed of GPT partitions, and this is also recommended in ZFS books as good practice to make it easier to identify a failed drive. Since you see the GPT partition name in the "zpool status" and other tools' output, it's handy.