Andrei POPESCU wrote:
> On Du, 14 mar 21, 17:34:40, Victor Sudakov wrote:
> > Andrei POPESCU wrote:
> > >
> > > I'm guessing it's in the GPT somewhere. Did you try removing the entire
> > > partition table before switching to ZFS?
> >
> > There had been no partition table, I just ran "mkfs.btrfs /dev/nvme1n1"
> > on the whole raw volume, and then mounted /dev/nvme1n1.
> >
> > Later, when switching to ZFS, I ran "zpool create fastdrive /dev/nvme1n1"
> > again on the whole volume. But ZFS outsmarted me and created a GPT
> > though I had not asked it to.
>
> Your blkid output suggests the GPT was created by btrfs ;)
Maybe btrfs does create it under some circumstances, but I cannot
reproduce it now:
root@test2-vas:~# blkid /dev/xvdg
root@test2-vas:~# mkfs.btrfs /dev/xvdg
btrfs-progs v4.20.1
See http://btrfs.wiki.kernel.org for more information.
Detected a SSD, turning off metadata duplication. Mkfs with -m dup if you want to force metadata duplication.
Label: (null)
UUID: 7d64c5ab-ae59-4e8d-aa6a-a86d7702f029
Node size: 16384
Sector size: 4096
Filesystem size: 100.00GiB
Block group profiles:
Data: single 8.00MiB
Metadata: single 8.00MiB
System: single 4.00MiB
SSD detected: yes
Incompat features: extref, skinny-metadata
Number of devices: 1
Devices:
ID SIZE PATH
1 100.00GiB /dev/xvdg
root@test2-vas:~#
root@test2-vas:~# blkid /dev/xvdg
/dev/xvdg: UUID="7d64c5ab-ae59-4e8d-aa6a-a86d7702f029" UUID_SUB="f0868f63-b40d-413a-ba76-6837b67b8ecf" TYPE="btrfs"
root@test2-vas:~#
root@test2-vas:~# fdisk !$
fdisk /dev/xvdg
Welcome to fdisk (util-linux 2.33.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
The old btrfs signature will be removed by a write command.
Device does not contain a recognized partition table.
Created a new DOS disklabel with disk identifier 0x43734e7e.
Command (m for help):
--
Victor Sudakov VAS4-RIPE
http://vas.tomsk.ru/
2:5005/49@fidonet
Attachment:
signature.asc
Description: PGP signature