Properly handle dataset recordsize of 1M
on 11.1-U5, changing the recordsize of a dataset (from the GUI) doesn't reflect the change that has been made.
1. create dataset
2. during creation, click on advanced and set recordsize to 1024k
3. double-click said dataset
4. look at the recordsize and it will show (inherited)
The webUI should show 1024K instead of inherited.
This does, however, change the recordsize at the OS level.
root@eye-02:~ # zfs get recordsize cargo-enc root@eye-02:~ # zfs get recordsize cargo-enc/recordsize NAME PROPERTY VALUE SOURCE cargo-enc/recordsize recordsize 1M local
#2 Updated by Dru Lavigne about 3 years ago
- Project changed from TrueNAS to FreeNAS
- Subject changed from webUI doesn't update when chaning recordsize of dataset to webUI doesn't update when changing recordsize of dataset
- Category changed from GUI to Middleware
- Assignee changed from Release Council to William Grzybowski
- Seen in changed from 11.1-U5 to TrueNAS 11.1-U5
- Migration Needed deleted (
- Hide from ChangeLog deleted (
- Support Department Priority deleted (
#4 Updated by William Grzybowski about 3 years ago
- Status changed from Unscreened to Blocked
- Reason for Blocked set to Need additional information from Author
I cannot reproduce this in our 11.2 Nightlies, so perhaps this was already fixed? Could you or someone else try in a newer version to confirm?
#5 Updated by Michael Reynolds about 3 years ago
- Status changed from Blocked to Failed Testing
- Reason for Blocked changed from Need additional information from Author to Waiting for feedback
I created a new dataset named Bug-34969
Changed the Record Size from "Inherit (128k)
to Record Size 1024K
Went into options to check dataset. The Record Size is Inherit (1048576)
zfs get recordsize reports 1M
1Mebibit equals 1024Kibibit
1024Kibibit equals 1048576Bits
So it looks like there is a couple of bugs here.
1st bug why is the new custom value listed as Inherit(1048576)
Seems the Inherit() shouldn't be there as it's no longer inherited?
2nd "bug" is an issue with the unit of measure used to display the values.
Looks to me that everything is in Mebibit/Kibibit/Bits not the more "normal" Megabytes/Kilobytes/Bytes that most people expect.
It's fine to use the forms used, but we should spell the entire value out Kibibit, not K for example.
I'd say we could/should even have a warning or tooltip, and a userguide entry explaining the measurement used.
#8 Updated by Michael Reynolds about 3 years ago
- File 1RecordSizeDefault-2018-06-15.png 1RecordSizeDefault-2018-06-15.png added
- File 2RecordSize1024k-2018-06-15.png 2RecordSize1024k-2018-06-15.png added
- File 3RecordSizeInherit-1048576-2018-06-15.png 3RecordSizeInherit-1048576-2018-06-15.png added
- File zfsReported-2018-06-15.png zfsReported-2018-06-15.png added
Apologies forgot the screenshots
This is using the latest FreeNAS nightly
#15 Updated by Bonnie Follweiler almost 3 years ago
- File Screen Shot 2018-06-26 at 10.23.20 AM.png Screen Shot 2018-06-26 at 10.23.20 AM.png added
- File Screen Shot 2018-06-26 at 10.24.17 AM.png Screen Shot 2018-06-26 at 10.24.17 AM.png added
- Status changed from Ready for Testing to Failed Testing
I created a dataset with a record limit of 1M
In the old UI it shows Record Size 1M
In the New GUI it shows Record size inherit (1048576)