mixed vdev capacities but 2 mirrors with the exact same disks

Herman Eggink

Explorer
Joined
Jan 27, 2014
Messages
73
I am seeing an orange exclamation mark saying mixed vdev capacities but the pool has 2 mirrors each having 2 identical disks. Any idea? Can't recall having seen this pre-cobia but may have been.
 
Joined
Oct 22, 2019
Messages
3,641
Are you using any special vdevs?
 

Herman Eggink

Explorer
Joined
Jan 27, 2014
Messages
73
Not that I know...

1701183397985.png


1701183425942.png
 

Patrick M. Hausen

Hall of Famer
Joined
Nov 25, 2013
Messages
7,776
What do the partition tables look like? IIRC lsblk would be one way to get them in Linux.
 
Joined
Oct 22, 2019
Messages
3,641
Either it's a bug...

Or at one point you changed the default "swap partition size", which is triggering this (pointless) warning.
 

Herman Eggink

Explorer
Joined
Jan 27, 2014
Messages
73
What do the partition tables look like? IIRC lsblk would be one way to get them in Linux.
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 7.3T 0 disk
├─sda1 8:1 0 2G 0 part
│ └─md126 9:126 0 2G 0 raid1
│ └─md126 253:0 0 2G 0 crypt [SWAP]
└─sda2 8:2 0 7.3T 0 part
sdb 8:16 0 7.3T 0 disk
├─sdb1 8:17 0 2G 0 part
│ └─md127 9:127 0 2G 0 raid1
│ └─md127 253:1 0 2G 0 crypt [SWAP]
└─sdb2 8:18 0 7.3T 0 part
sdc 8:32 0 7.3T 0 disk
├─sdc1 8:33 0 2G 0 part
│ └─md126 9:126 0 2G 0 raid1
│ └─md126 253:0 0 2G 0 crypt [SWAP]
└─sdc2 8:34 0 7.3T 0 part
sdd 8:48 0 7.3T 0 disk
├─sdd1 8:49 0 2G 0 part
│ └─md127 9:127 0 2G 0 raid1
│ └─md127 253:1 0 2G 0 crypt [SWAP]
└─sdd2 8:50 0 7.3T 0 part
sde 8:64 0 55.9G 0 disk
├─sde1 8:65 0 512K 0 part
└─sde2 8:66 0 55.9G 0 part
sdf 8:80 0 7.3T 0 disk
├─sdf1 8:81 0 2G 0 part
└─sdf2 8:82 0 7.3T 0 part
sdg 8:96 1 0B 0 disk
zd0 230:0 0 512G 0 disk

sda,b,c and d are my data disks for my pool Main
sdf is a single backup drive (same as all other disks) for a pool Backup
sde is a smaller boot SSD (55G)
sdg is listed as a Generic_STORAGE_DEVICE-0:0 of 0B (no idea how that ever got there but it's unused)
 

Herman Eggink

Explorer
Joined
Jan 27, 2014
Messages
73
Either it's a bug...

Or at one point you changed the default "swap partition size", which is triggering this (pointless) warning.
I can't recall ever changing swap. I did switch out all Red's for SSD's a while back (given that the system isn't very write active and the SSD's dropped quite a bit in price and I was upset with the noise and and and) but I didn't change swap AFAICT.
 

Patrick M. Hausen

Hall of Famer
Joined
Nov 25, 2013
Messages
7,776
All the data disks have the standard 2G swap partition. I'm out of ideas.
 
Joined
Oct 22, 2019
Messages
3,641
Can you run the lsblk command again, but this time pass the "-b" flag?
 

Herman Eggink

Explorer
Joined
Jan 27, 2014
Messages
73
SD media card reader? :tongue:
Owww bugger, now why didn't I think of that...

Here's lsblk -b:

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 8001563222016 0 disk
├─sda1 8:1 0 2147418624 0 part
│ └─md126 9:126 0 2145320960 0 raid1
│ └─md126 253:0 0 2145320960 0 crypt [SWAP]
└─sda2 8:2 0 7999415655936 0 part
sdb 8:16 0 8001563222016 0 disk
├─sdb1 8:17 0 2147418624 0 part
│ └─md127 9:127 0 2145320960 0 raid1
│ └─md127 253:1 0 2145320960 0 crypt [SWAP]
└─sdb2 8:18 0 7999415655936 0 part
sdc 8:32 0 8001563222016 0 disk
├─sdc1 8:33 0 2147418624 0 part
│ └─md126 9:126 0 2145320960 0 raid1
│ └─md126 253:0 0 2145320960 0 crypt [SWAP]
└─sdc2 8:34 0 7999415655936 0 part
sdd 8:48 0 8001563222016 0 disk
├─sdd1 8:49 0 2147418624 0 part
│ └─md127 9:127 0 2145320960 0 raid1
│ └─md127 253:1 0 2145320960 0 crypt [SWAP]
└─sdd2 8:50 0 7999415655936 0 part
sde 8:64 0 60022480896 0 disk
├─sde1 8:65 0 524288 0 part
└─sde2 8:66 0 60021915648 0 part
sdf 8:80 0 8001563222016 0 disk
├─sdf1 8:81 0 2147418624 0 part
└─sdf2 8:82 0 7999415655936 0 part
sdg 8:96 1 0 0 disk
zd0 230:0 0 549755813888 0 disk
 
Joined
Oct 22, 2019
Messages
3,641
What the heck is SCALE complaining about? Every single partition in your data vdevs are the same exact size, down to the very byte.

Surely this has to be a bug.
 
Joined
Oct 22, 2019
Messages
3,641
I managed to fix your problem. It's all about the color and the symbol!

everything-is-fine.png


But in seriousness, I'd file a bug report. (I could have sworn a similar issue happened before, which they supposedly "fixed" with an update?)
 

Herman Eggink

Explorer
Joined
Jan 27, 2014
Messages
73
Will do. I thought I was going mad. Thanks for confirming and for the help.
 
Top