24.10 RC2 Raidz expansion caused miscalculated available storage

TrueNAS General
, ,
142

Yes, but when? :slight_smile:

1 Like
143

I am struggling with the concept on how the UI reports capacity as well :slight_smile:
9 x 12 TB raidz2. Started with 4 disks, expanded the remaining disks one by one with no errors, no reboots.

“zpool list” shows 87 TB size, 29 TB free. UI shows “Usable Capacity:
42.5 TiB”, “Free Space: 13.63 TiB” - does not make any sense to me.

Does anybody know a workaround/fix to get the UI to be consistent with what the OS reports?

1 Like
144

This is a known issue with no, current cure. Go by the CLI.

2 Likes
145

Thanks! - too late, I already ordered two more 12 TB drives :slight_smile: which should get me set for the next 100 years lol

2 Likes
146

Is there work being done to fix this, or just SOL for the time being?

147

Just search for RAID-Zx-expansion tag and do some reading. CLI is most accurate reporting currently.

148

… and use zpool list report info, not zfs list.

149

Unfortunately this is still an issue in 25.04
I just expanded a 4 wide raidz2 to 5 wide and was trying to figure out why almost an entire drives worth of available capacity was missing

1 Like
150

I don’t know if this is an issue that will be fixed. You can read the other threads with the RAID-Zx-expansion tags to get an idea of what is involved with how the expansion happens and ZFS.

151

Maybe not fully fixed, but we are working on a nice change to zfs that will mitigate this and allow easier way to fix the reporting down the road, among other nice benefits :slight_smile:

6 Likes
152

So in its current state it only removes the need to run a rebalance script on an expanded vdev, but doesn’t fix incorrect drive space reporting correct? But you’re saying it might make fixing the space reporting on an expanded vdev easier once that bug is taken on?

153

Just transcode them with AV1 preset 0, duh.

Don't wanna hurry you, but...

1 Like
155

TL:DR we’ll have to wait for a fix or?

156

It may be healthier to acknowledge that there is no fix. While this can be fixed, I wouldn’t expect it within any reasonable interpretation of Soon™. You’re talking generational change. Maybe your descendants’ descendants will get to see it.

2 Likes
157

Longer explanation:
The borked space accounting was a deliberate decision by the main developer of raidz expansion (and one of the ZFS architects…) to make implementation easier.

To “fix” means reopening the case for raidz expansion… Expect similar time frames for delivery. At the VERY best. (For a realistic estimate, see @yorick above.)

3 Likes
158

I wouldn’t be quite as pessimistic… Based on what IX says, this could be fixed by changing the shrink value after running zfs rewrite - which has been merged and is slated for addition to 25.10.

1 Like
159

That issue contains an absolutely genius comment by user HammyHavoc:

The level of risk is directly proportionate to your ability to restore the data from a backup.

Engrave that in marble, place it on top of the web UI. :slightly_smiling_face:

5 Likes
160

I hope it never gets fixed. If my 4GB movie is supposedly only consuming 3GB of storage, that’s something I can brag about! :smiley:

1 Like
161

Take a clue from WD and pretend it is a “3GB-class” file…

3 Likes
162

I dont really get it, zpool info shows correct info. How hard is to display that tu TNS gui. At least something…

1 Like