So I have been playing around with ZFS on my test computer before changing all my servers to ZFS.
Currently BOOT device is nvd1p4.
gpart list nvd1
I decided to do some simple testing by adding nvd0 to nvd1 zpool....
I did not try to do RAID nor MIRROR because wanted to do a simple test to add to ZPOOL.
unfortunately after add I cannot REMOVE the drive.....
nvd1p4 460G 38.4G 422G - - 4% 8%
nvd0p1 464G 63.6M 464G - - 0% 0%
========================================================================================================
My question is why can't I remove it? Do I really need to transfer the zvol into another drive and destroy zpool and recreate as 2 independent zpool?
Any information on past experience will be great....
Above there is a feature = device_removal install on computer, wasn't this feature implemented for my specific test case that is not mirror, cache, hot spare or raidz?Thank you in advance.
FreeBSD 12.1-RELEASE FreeBSD 12.1-RELEASE
Currently BOOT device is nvd1p4.
gpart list nvd1
Code:
1. Name: nvd1p1
Mediasize: 209715200 (200M)
Sectorsize: 512
Stripesize: 0
Stripeoffset: 20480
Mode: r0w0e0
efimedia: HD(1,GPT,ac10b120-37c0-11eb-9882-7085c25db4b0,0x28,0x64000)
rawuuid: ac10b120-37c0-11eb-9882-7085c25db4b0
rawtype: c12a7328-f81f-11d2-ba4b-00a0c93ec93b
label: efiboot0
length: 209715200
offset: 20480
type: efi
index: 1
end: 409639
start: 40
2. Name: nvd1p2
Mediasize: 524288 (512K)
Sectorsize: 512
Stripesize: 0
Stripeoffset: 209735680
Mode: r0w0e0
efimedia: HD(2,GPT,ac19cd27-37c0-11eb-9882-7085c25db4b0,0x64028,0x400)
rawuuid: ac19cd27-37c0-11eb-9882-7085c25db4b0
rawtype: 83bd6b9d-7f41-11dc-be0b-001560b84f0f
label: gptboot0
length: 524288
offset: 209735680
type: freebsd-boot
index: 2
end: 410663
start: 409640
3. Name: nvd1p3
Mediasize: 2147483648 (2.0G)
Sectorsize: 512
Stripesize: 0
Stripeoffset: 210763776
Mode: r1w1e0
efimedia: HD(3,GPT,ac1f9718-37c0-11eb-9882-7085c25db4b0,0x64800,0x400000)
rawuuid: ac1f9718-37c0-11eb-9882-7085c25db4b0
rawtype: 516e7cb5-6ecf-11d6-8ff8-00022d09712b
label: swap0
length: 2147483648
offset: 210763776
type: freebsd-swap
index: 3
end: 4605951
start: 411648
4. Name: nvd1p4
Mediasize: 497749590016 (464G)
Sectorsize: 512
Stripesize: 0
Stripeoffset: 2358247424
Mode: r1w1e1
efimedia: HD(4,GPT,ac23c64c-37c0-11eb-9882-7085c25db4b0,0x464800,0x39f21800)
rawuuid: ac23c64c-37c0-11eb-9882-7085c25db4b0
rawtype: 516e7cba-6ecf-11d6-8ff8-00022d09712b
label: zfs0
length: 497749590016
offset: 2358247424
type: freebsd-zfs
index: 4
end: 976773119
start: 4605952
Consumers:
1. Name: nvd1
Mediasize: 500107862016 (466G)
Sectorsize: 512
Mode: r2w2e3
40 976773088 nvd0 GPT (466G)
40 976773088 - free - (466G)
Code:
gpart list nvd0
Geom name: nvd0
modified: false
state: OK
fwheads: 255
fwsectors: 63
last: 976773127
first: 40
entries: 128
scheme: GPT
Providers:
1. Name: nvd0p1
Mediasize: 500107821056 (466G)
Sectorsize: 512
Stripesize: 0
Stripeoffset: 20480
Mode: r1w1e1
efimedia: HD(1,GPT,47a22f3a-3f49-11eb-bf29-7085c25db4b0,0x28,0x3a385fe0)
rawuuid: 47a22f3a-3f49-11eb-bf29-7085c25db4b0
rawtype: 516e7cba-6ecf-11d6-8ff8-00022d09712b
label: (null)
length: 500107821056
offset: 20480
type: freebsd-zfs
index: 1
end: 976773127
start: 40
Consumers:
1. Name: nvd0
Mediasize: 500107862016 (466G)
Sectorsize: 512
Mode: r1w1e2
I decided to do some simple testing by adding nvd0 to nvd1 zpool....
Code:
zpool add zroot_nvme_1 nvd0p1
I did not try to do RAID nor MIRROR because wanted to do a simple test to add to ZPOOL.
unfortunately after add I cannot REMOVE the drive.....
Code:
zpool remove zroot_nvme_1 nvd0p1
cannot remove nvd0p1: invalid config; all top-level vdevs must have the same sector size and not be raidz.
nvd0p1 464G 63.6M 464G - - 0% 0%
Code:
zpool upgrade -v
async_destroy (read-only compatible)
Destroy filesystems asynchronously.
empty_bpobj (read-only compatible)
Snapshots use less space.
lz4_compress
LZ4 compression algorithm support.
multi_vdev_crash_dump
Crash dumps to multiple vdev pools.
spacemap_histogram (read-only compatible)
Spacemaps maintain space histograms.
enabled_txg (read-only compatible)
Record txg at which a feature is enabled
hole_birth
Retain hole birth txg for more precise zfs send
extensible_dataset
Enhanced dataset functionality, used by other features.
embedded_data
Blocks which compress very well use even less space.
bookmarks (read-only compatible)
"zfs bookmark" command
filesystem_limits (read-only compatible)
Filesystem and snapshot limits.
large_blocks
Support for blocks larger than 128KB.
large_dnode
Variable on-disk size of dnodes.
sha512
SHA-512/256 hash algorithm.
skein
Skein hash algorithm.
device_removal
Top-level vdevs can be removed, reducing logical pool size.
obsolete_counts (read-only compatible)
Reduce memory used by removed devices when their blocks are freed or remapped.
zpool_checkpoint (read-only compatible)
Pool state can be checkpointed, allowing rewind later.
spacemap_v2 (read-only compatible)
Space maps representing large segments are more efficient.
========================================================================================================
My question is why can't I remove it? Do I really need to transfer the zvol into another drive and destroy zpool and recreate as 2 independent zpool?
Any information on past experience will be great....
Above there is a feature = device_removal install on computer, wasn't this feature implemented for my specific test case that is not mirror, cache, hot spare or raidz?Thank you in advance.
FreeBSD 12.1-RELEASE FreeBSD 12.1-RELEASE
Last edited by a moderator: