Package: zfs-dkms Version: 0.6.5.9-2~bpo8+1 Severity: normal Dear Maintainer,
I try to expand a pool by growing the underlying vdev (/dev/sde in my case) * I've create a pool with: zpool create -f tank sde * then I've checked the ouput of fdisk # fdisk /dev/sde Commande (m pour l'aide) : p Disque /dev/sde : 20 GiB, 21474836480 octets, 41943040 secteurs Unités : secteur de 1 × 512 = 512 octets Taille de secteur (logique / physique) : 512 octets / 512 octets taille d'E/S (minimale / optimale) : 512 octets / 512 octets Type d'étiquette de disque : gpt Identifiant de disque : 504F5A4E-74DA-184F-AEBB-F9CB5BA2401C Device Start End Sectors Size Type /dev/sde1 2048 41924607 41922560 20G Solaris /usr & Apple ZFS /dev/sde9 41924608 41940991 16384 8M Solaris reserved 1 Commande (m pour l'aide) : q ``` * Then I've expended the *physical* disk with the vmware GUI from 20GB to 40GB * Then I've done a rescan of the disks with: # for i in /sys/class/scsi_disk/*/device/rescan;do echo $i echo 1 > "$i" done /sys/class/scsi_disk/2:0:0:0/device/rescan /sys/class/scsi_disk/2:0:1:0/device/rescan /sys/class/scsi_disk/2:0:2:0/device/rescan /sys/class/scsi_disk/2:0:3:0/device/rescan /sys/class/scsi_disk/2:0:4:0/device/rescan * I've checked again the ouptut of fdisk # LC_ALL=C fdisk /dev/sde Welcome to fdisk (util-linux 2.25.2). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. GPT PMBR size mismatch (41943039 != 83886079) will be corrected by w(rite). GPT PMBR size mismatch (41943039 != 83886079) will be corrected by w(rite). Command (m for help): p Disk /dev/sde: 40 GiB, 42949672960 bytes, 83886080 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 504F5A4E-74DA-184F-AEBB-F9CB5BA2401C Device Start End Sectors Size Type /dev/sde1 2048 41924607 41922560 20G Solaris /usr & Apple ZFS /dev/sde9 41924608 41940991 16384 8M Solaris reserved 1 Command (m for help): q * strange fdisk shows an error, and the partititon did not change * extend the pool zpool online -e tank sde * fdisk again LC_ALL=C fdisk /dev/sde Welcome to fdisk (util-linux 2.25.2). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Command (m for help): p Disk /dev/sde: 40 GiB, 42949672960 bytes, 83886080 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 504F5A4E-74DA-184F-AEBB-F9CB5BA2401C Device Start End Sectors Size Type /dev/sde1 2048 83867647 83865600 40G Solaris /usr & Apple ZFS /dev/sde9 83867648 83884031 16384 8M Solaris reserved 1 Command (m for help): q * now fdisk does not give an error anymore, and the partition seems to have changed accordingly * but, zpool persist on not showing more free space # zpool list -v NAME SIZE ALLOC FREE EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT tank 19.9G 19.3G 636M - 52% 96% 1.00x ONLINE - sde 19.9G 19.3G 636M - 52% 96% -- System Information: Debian Release: 8.8 APT prefers oldstable APT policy: (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_CH.UTF-8, LC_CTYPE=fr_CH.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages zfs-dkms depends on: ii debconf [debconf-2.0] 1.5.56 ii dkms 2.3-2~bpo8+1 ii lsb-release 4.1+Debian13+nmu1 ii spl-dkms 0.6.5.9-1~bpo8+1 Versions of packages zfs-dkms recommends: ii zfs-zed 0.6.5.9-2~bpo8+1 ii zfsutils-linux 0.6.5.9-2~bpo8+1 zfs-dkms suggests no packages. -- debconf information: * zfs-dkms/note-incompatible-licenses: zfs-dkms/stop-build-for-unknown-kernel: true zfs-dkms/stop-build-for-32bit-kernel: true
