Zvol Creation through GUI Hangs Indefinitely
Attempting to create a Zvol inside of a dataset through the GUI results in the attempt hanging indefinitely when hitting Save. No error is returned, and no zvol is created.
Creating a Zvol through CLI works fine: zfs create -V 250G mypool/dataset/vol1
It appears this is the case if you do not choose a block size. It would make sense for the "default" block size be "inherit" similar to other GUI wizard screens, or error out when no block size is properly selected. Further, the GUI should specify the requirement to select a Block Size field is required before the form can be submitted.
#3 Updated by Erin Clark about 1 year ago
- Private changed from No to Yes
Is this easily reproducible on your box? If so could you both provide us a debug (Go to system > advanced and click save debug) and could you see if there are any tracebacks in the console (right click > inspect and go to console). I am marking the ticket private so you can upload your debug privately.
#12 Updated by Ray Sundland about 1 year ago
The record size of the parent dataset is set to inherit (from the pool), and the pool is set to 128K.
I do notice that 512, 1K, and 2K options are greyed out if I try to change the record size at the pool or dataset level.
Just noticed, if I attempt to create the Zvol at the pool directly (not under a dataset), the Block Size gets automatically set to 16K (not 128K which is the pool's record size) -- which also seems odd if, as you said, it should inherit from the parent.
So with that, I just created a new dataset with a static Record Size (not inheriting from the pool), but then creating the Zvol under the new dataset results in the same JS error, no block size defined, and hangs indefinitely unless the block size is chosen.
#17 Updated by Vaibhav Chauhan about 1 year ago
#21 Updated by Erin Clark about 1 year ago
- Status changed from In Progress to Closed
- Reason for Closing set to Duplicate Issue
Since this is most likely fixed as of https://redmine.ixsystems.com/issues/62028, I am going to go ahead and close this, please update to the next release that comes out and if you are still having problems reopen the ticket and we will investigate this further.