You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once again, what is dull and routine on Solaris and FreeBSD, is tricky, obscured and overcomplicated on Linux. I have resized the disk under the zpool doubledata, but system just doesn't see the new size as EXPANDSZ. Pool remains like the disk hasn't been resized. I cannot resize it using any possible trick I'm aware of.
Describe how to reproduce the problem
[root@db3 etc]# zpool status pool: data state: ONLINE scan: none requestedconfig: NAME STATE READ WRITE CKSUM data ONLINE 0 0 0 sdb ONLINE 0 0 0errors: No known data errors pool: doubledata state: ONLINE scan: scrub repaired 0B in 0h50m with 0 errors on Fri Nov 30 16:04:17 2018config: NAME STATE READ WRITE CKSUM doubledata ONLINE 0 0 0 sdc ONLINE 0 0 0errors: No known data errors[root@db3 etc]# zpool listNAME SIZE ALLOC FREE EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOTdata 398G 56.2G 342G - 83% 14% 1.00x ONLINE -doubledata 298G 264G 34.0G - 75% 88% 1.00x ONLINE -[root@db3 etc]# parted /dev/sdcGNU Parted 3.1Using /dev/sdcWelcome to GNU Parted! Type 'help' to view a list of commands.(parted) pModel: QEMU QEMU HARDDISK (scsi)Disk /dev/sdc: 408GBSector size (logical/physical): 512B/512BPartition Table: gptDisk Flags:Number Start End Size File system Name Flags 1 1049kB 322GB 322GB zfs-a1787aff0eb8073d 9 322GB 322GB 8389kB(parted) q[root@db3 etc]# zpool offline doubledata sdccannot offline sdc: no valid replicas[root@db3 etc]# zpool online -e doubledata sdc[root@db3 etc]# zpool online doubledata sdc[root@db3 etc]# zpool listNAME SIZE ALLOC FREE EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOTdata 398G 56.2G 342G - 83% 14% 1.00x ONLINE -doubledata 298G 264G 34.0G - 75% 88% 1.00x ONLINE -[root@db3 etc]# zpool set autoexpand=on doubledata[root@db3 etc]# zpool listNAME SIZE ALLOC FREE EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOTdata 398G 56.2G 342G - 83% 14% 1.00x ONLINE -doubledata 298G 264G 34.0G - 75% 88% 1.00x ONLINE -[root@db3 etc]# zpool online doubledata sdc[root@db3 etc]# zpool listNAME SIZE ALLOC FREE EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOTdata 398G 56.2G 342G - 83% 14% 1.00x ONLINE -doubledata 298G 264G 34.0G - 75% 88% 1.00x ONLINE -[root@db3 etc]# zpool set autoexpand=on doubledata[root@db3 etc]# zpool export doubledata[root@db3 etc]# zpool import doubledata[root@db3 etc]# zpool listNAME SIZE ALLOC FREE EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOTdata 398G 56.2G 342G - 83% 14% 1.00x ONLINE -doubledata 298G 264G 34.0G - 75% 88% 1.00x ONLINE -[root@db3 etc]# zpool online doubledata sdc[root@db3 etc]# zpool listNAME SIZE ALLOC FREE EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOTdata 398G 56.2G 342G - 83% 14% 1.00x ONLINE -doubledata 298G 264G 34.0G - 75% 88% 1.00x ONLINE -[root@db3 etc]# zpool export doubledata[root@db3 etc]# zpool import doubledata -o autoexpand=on doubledata[root@db3 etc]# zpool listNAME SIZE ALLOC FREE EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOTdata 398G 56.3G 342G - 83% 14% 1.00x ONLINE -doubledata 298G 264G 34.0G - 75% 88% 1.00x ONLINE -[root@db3 etc]# zpool set autoexpand=off doubledata[root@db3 etc]# zpool export doubledata[root@db3 etc]# zpool import doubledata[root@db3 etc]# zpool get autoexpand doubledataNAME PROPERTY VALUE SOURCEdoubledata autoexpand off default[root@db3 etc]# zpool listNAME SIZE ALLOC FREE EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOTdata 398G 56.3G 342G - 83% 14% 1.00x ONLINE -doubledata 298G 264G 34.0G - 75% 88% 1.00x ONLINE -[root@db3 etc]#
Include any warning/errors/backtraces from the system logs
The text was updated successfully, but these errors were encountered:
You've unfortunately run in to a known issue with the 0.7.x series. There are a surprising number of small differences between Illumos, FreeBSD, and Linux which can end up leading to problems like this. We've been working hard to improve the test coverage to prevent regressions, and also to systematically address every issue we find.
This particular issue has been fixed in master by #7546 and #7629. There was work was done to back port both of these fixes for the 0.7.10 tag, but those changes needed to reverted in 0.7.11 after it was discovered they accidentally introduced a subtle bug. You can expect this to work properly in the 0.8 release.
System information
Describe the problem you're observing
Once again, what is dull and routine on Solaris and FreeBSD, is tricky, obscured and overcomplicated on Linux. I have resized the disk under the zpool doubledata, but system just doesn't see the new size as EXPANDSZ. Pool remains like the disk hasn't been resized. I cannot resize it using any possible trick I'm aware of.
Describe how to reproduce the problem
Include any warning/errors/backtraces from the system logs
The text was updated successfully, but these errors were encountered: