Project

General

Profile

Bug #26586

Prevent Volume Manager from switching to stripe after selecting cache device

Added by Thomas DeMoss over 1 year ago. Updated about 1 year ago.

Status:
Done
Priority:
Critical
Assignee:
William Grzybowski
Category:
Middleware
Target version:
Seen in:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
No
Needs Doc:
No
Needs Merging:
No
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

I installed 2 SSD's into my Freenas Server for the purposes of setting up the L2ARC cache devices. While working in the small dialog box (using a 4K monitor), I noticed the volume layout section that a data disk group would not configure until I touched the little disk near ada1. This also unexpectedly switches the cache (L2ARC) setting to stripe mode.

Next I find the drop down to the right of the cache drop down disappear. After canceling several times and retrying to make sure I had this perfect, I click Extend Volume. When I check on the status, the SSD is now stripped into the Volume instead of being setup as L2ARC cache. Please help me get this fixed. I don't even see the point under any circumstances to ever stripe in a non-JBOD disk into an array like that. Why is it even possible? This is coming from a storage engineer for the last 22 year.

vm-cache1.PNG (20.9 KB) vm-cache1.PNG Thomas DeMoss, 11/09/2017 06:36 PM
vm-cache2.PNG (21.4 KB) vm-cache2.PNG Thomas DeMoss, 11/09/2017 06:36 PM
vm-Vol1-status.PNG (15.6 KB) vm-Vol1-status.PNG Thomas DeMoss, 11/09/2017 06:36 PM
bug_demo_2017-11-20 23-57-58.flv (16.3 MB) bug_demo_2017-11-20 23-57-58.flv Thomas DeMoss, 11/20/2017 11:05 PM
12995
12996
12997

Related issues

Related to FreeNAS - Feature #26622: Warn before Extending poolsDone2017-11-12

Associated revisions

Revision db2ea66a (diff)
Added by William Grzybowski over 1 year ago

fix(gui): do not switch away from select vdev type

Unless changing number of disks.

Ticket: #26586

Revision adfb76a2 (diff)
Added by William Grzybowski over 1 year ago

fix(gui): do not switch away from select vdev type

Unless changing number of disks.

Ticket: #26586

History

#1 Updated by Thomas DeMoss over 1 year ago

  • File debug-freenas-20171109193619.txz added

#2 Updated by Thomas DeMoss over 1 year ago

12995

#3 Updated by Thomas DeMoss over 1 year ago

12996

#4 Updated by Thomas DeMoss over 1 year ago

12997

#5 Updated by Thomas DeMoss over 1 year ago

  • File debug-freenas-20171109202433.tgz added

Uploading debug

#6 Updated by Thomas DeMoss over 1 year ago

Despite the bug, my priority is to remove the SSD from Vol1.

#7 Updated by Dru Lavigne over 1 year ago

  • Assignee changed from Release Council to William Grzybowski

#8 Updated by William Grzybowski over 1 year ago

  • Status changed from Unscreened to Screened
  • Priority changed from No priority to Critical
  • Target version set to 11.2-BETA1

I am sorry this has happened to you but there is no going back.

You have to nuke and repave.

#9 Updated by Thomas DeMoss over 1 year ago

William Grzybowski wrote:

I am sorry this has happened to you but there is no going back.

You have to nuke and repave.

Well that is very very disappointing. All Jails and VM's will need to be rebuilt. Is there a way I can save them off and import them back?

What is happening in the UI that causes it to switch from cache to stripe? I'm sure it something to do with validating some other fields.

#10 Updated by William Grzybowski over 1 year ago

Thomas DeMoss wrote:

William Grzybowski wrote:

I am sorry this has happened to you but there is no going back.

You have to nuke and repave.

Well that is very very disappointing. All Jails and VM's will need to be rebuilt. Is there a way I can save them off and import them back?

What is happening in the UI that causes it to switch from cache to stripe? I'm sure it something to do with validating some other fields.

We will have to figure that out, I have no clue yet, unfortunately.

I think you could replicate the pool to another one, export the pool on UI without deleting jails/shares and then reimport.

#11 Updated by Thomas DeMoss over 1 year ago

I was reading forum posts on the topic and some very good suggestions are there on how to move Jails to another volume. I have about 15TB of data on the affected volume and it won't fit inside my other two volumes at the moment. I may need to just copy this out to some spare drives then copy it back in, but I'll figure it out. This will likely be over the Thanksgiving weekend. Once I get the new Volume recreated and before I restore the contents back, I'll setup the new L2ARC cache and see if I run into the same bug. If I can replicate it again, I'll post additional logs up here.

#12 Updated by Dru Lavigne over 1 year ago

#13 Updated by Thomas DeMoss over 1 year ago

Just added a short video demo of the bug in action to the case.

#14 Updated by William Grzybowski over 1 year ago

Thomas DeMoss wrote:

Just added a short video demo of the bug in action to the case.

Thanks for the video, its very helpful.

#15 Updated by William Grzybowski over 1 year ago

  • Status changed from Screened to Ready For Release
  • Seen in changed from Unspecified to 11.1

I have only fixed the Cache -> Stripe bug since that the most important one.

We will refrain from fixing the other mentioned bugs since it seems a waste of time because 11.2 will feature a whole new UI by default.

https://github.com/freenas/freenas/pull/625

#16 Updated by Dru Lavigne over 1 year ago

  • File deleted (debug-freenas-20171109193619.txz)

#17 Updated by Dru Lavigne over 1 year ago

  • File deleted (debug-freenas-20171109202433.tgz)

#18 Updated by Dru Lavigne over 1 year ago

  • Private changed from Yes to No

#19 Updated by Dru Lavigne over 1 year ago

  • Subject changed from Volume Manager unexpectedly switches to stripe after selecting cache device to Prevent Volume Manager from switching to stripe after selecting cache device
  • Status changed from Ready For Release to Done
  • Needs Doc changed from Yes to No
  • Needs Merging changed from Yes to No

#20 Updated by Dru Lavigne about 1 year ago

  • Status changed from Done to Ready for Testing

#21 Updated by William Grzybowski about 1 year ago

  • Category changed from GUI (new) to Middleware

#22 Updated by Timothy Moore II about 1 year ago

  • Status changed from Ready for Testing to Passed Testing
  • Severity set to New

#23 Updated by Dru Lavigne about 1 year ago

  • Status changed from Passed Testing to Done

#24 Updated by Dru Lavigne about 1 year ago

  • Needs QA changed from Yes to No

Also available in: Atom PDF