Dataset > Edit Option > Comments results in {rs!r} is an invalid recordsize

[lombana]

New user here migrating from a rack of ReadyNas and Synology units.

I'm finding that after I set up a new dataset in a pool and go back in to edit something as simple as the comment in that dataset, I'm met with {rs!r} is an invalid recordsize when I try to save it.

This is on a new build, no data has been transferred into the pool, just trying to make a change to the description of one of the datasets and finding it odd that just a change to a comment results in this error - {rs!r} is an invalid recordsize.

Thanks,
Miguel

 

[sretalla]

What do you get if you type this in a the shell:

zfs get recordsize pool/dataset (where you replace pool/dataset with the actual names of your pool and the dataset you're talking about).

 

[BitByteBit]

I get the same error in the GUI when Editing Existing Dataset Options, on a clean install of TrueNAS Core 13.0.
In my case I was trying to change the ACL Mode.

Anyone have any idea if this is already a known / tracked bug with iX Systems Jira?

 

[BitByteBit]

@sretalla, I realize you were asking the OP, but for me I'm using the (default) recordsize of 128K on the dataset.
This shows as Inherit (128 KiB) in the GUI as well.

 

[sretalla]

Good to know... sounds like it's a bug then...

 

[BitByteBit]

Looks like a change was made to the middleware code around 2 months ago which could be related:

NAS-115983 / 22.12 / missing f in f-string by yocalebo · Pull Request #8865 · truenas/middleware

TrueNAS CORE/Enterprise/SCALE Middleware Git Repository - NAS-115983 / 22.12 / missing f in f-string by yocalebo · Pull Request #8865 · truenas/middleware

github.com

Not sure if this change was included in TrueNAS Core 13.0 or not though...

 

[anodos]

Looks like a change was made to the middleware code around 2 months ago which could be related:

NAS-115983 / 22.12 / missing f in f-string by yocalebo · Pull Request #8865 · truenas/middleware

TrueNAS CORE/Enterprise/SCALE Middleware Git Repository - NAS-115983 / 22.12 / missing f in f-string by yocalebo · Pull Request #8865 · truenas/middleware

github.com

Not sure if this change was included in TrueNAS Core 13.0 or not though...

Code:

commit 297a8714384465c5e25b2c662079f46d4ac45eff
Author: themylogin <themylogin@gmail.com>
Date:   Fri Jun 3 17:11:16 2022 +0200

    Fix crash on validation of inherited `special_small_block_size` and `recordsize` (#9116)

 

[BitByteBit]

Code:

commit 297a8714384465c5e25b2c662079f46d4ac45eff
Author: themylogin <themylogin@gmail.com>
Date:   Fri Jun 3 17:11:16 2022 +0200

    Fix crash on validation of inherited `special_small_block_size` and `recordsize` (#9116)

Thank you for pointing to the bug fix commit. Hopefully this fix makes it into 13.0-U1.

 

[lombana]

What do you get if you type this in a the shell:

zfs get recordsize pool/dataset (where you replace pool/dataset with the actual names of your pool and the dataset you're talking about).

Reading down looks like I found a small bug - here was the result from that - it echoes the GUI

truenas-01% zfs get recordsize p1-biggie/backup-legacy
NAME PROPERTY VALUE SOURCE
p1-biggie/backup-legacy recordsize 128K default

Glad I could help in finding it.