cracauer@
Developer
Now I need to do this last bit but not sure how.
zpool set autoexpand=on tank
That's all, it should automatically balloon to the size of the partition.
Now I need to do this last bit but not sure how.
I ran zpool set autoexpand=on zroot (I presume that was correct in my case)zpool set autoexpand=on tank
That's all, it should automatically balloon to the size of the partition.
I ran zpool set autoexpand=on zroot (I presume that was correct in my case)
df -h shows the same as it did before, ie 273G on zroot/ROOT/default.
zpool list shows EXPANDSZ 632G
Is that to be expected?
zpool set autoexpand=on zroot not working
Not exactly sure what that means but it will probably sort itself out.I asked ChatGPT:-
1. What
- It does NOT immediately resize existing vdevs
- It only allows a vdev to grow after the underlying block device grows
- Expansion happens when ZFS detects a size change, or when you explicitly tell it to
So setting the property alone does nothing until the disk itself is larger and ZFS is told to rescan.
I asked ChatGPT:-
1. What
- It does NOT immediately resize existing vdevs
- It only allows a vdev to grow after the underlying block device grows
- Expansion happens when ZFS detects a size change, or when you explicitly tell it to
So setting the property alone does nothing until the disk itself is larger and ZFS is told to rescan.
I managed to sort it following suggestions by ChatGPT and now df -h reports 886G
zpool online -e zroot device_name will finish the job.I ran zpool set autoexpand=on zroot (I presume that was correct in my case)
df -h shows the same as it did before, ie 273G on zroot/ROOT/default.
zpool list shows EXPANDSZ 632G
Is that to be expected?
I followed what I got from ChatGPT when I typed:-What exactly did you do?
zpool set autoexpand=on zroot not working