• Create ZFS pool with 3 way mirror fails


    JonathanM
    • Minor

    Attempted to change a formerly BTRFS 3 way mirror to ZFS, "format" fails, error in log is...

    emhttpd: cache: invalid profile: 'mirror' 3 0

     

    I have NOT

    wiped the devices and tried again

    restarted and tried again

     

    I wanted to leave things as is in case more info was needed to help deal with the original issue.

     




    User Feedback

    Recommended Comments

    Cannot reproduce, but "invalid profile: 'mirror' 3 0" is a problem, should be 'mirror' 3 1.

     

    Can you describe the steps you took to create the pool?

     

    This is what I did:

     

    assign 3 devices to a pool

    click on the first device and change fs to zfs, mirror, 1 group of 3 devices

    start array

    format pool

     

     

     

     

    Link to comment

    Maybe order matters?

     

    Already had 3 device pool that originally had the 3 SSD's in a BTRFS 3 way, but slots were empty.

    Clicked on first device, changed format to ZFS, 1 group 3 members, applied changes

    Assigned 3 devices to the 3 empty slots, confirmed ZFS still was selected

    Started array, formatted pool.

     

    I guess to recreate try first setting up a 3 way BTRFS, format it, stop the array, unassign pool slots, start/stop array to commit change, change first pool slot to ZFS, assign disks.

    Link to comment
    8 minutes ago, JonathanM said:

    Maybe order matters?

    Yep, that's it, if you first select the pool type before assigning the devices it will fail, it's something I never tried before, the idea is that you select the fs/profile after assigning the devices, because you can't even change from mirror to a different one for example without devices assigned, but the GUI does allow that, so it should be corrected.

    Link to comment

    So, what would be the best way to reset?

     

    14 minutes ago, JorgeB said:

    it's something I never tried before

    🤣 Well, at least I uncovered it early. Too bad I didn't try it during the RC cycle.

    Link to comment

    Since the pool is new and there's no data you can:

     

    stop array

    click on first pool device 

    click erase and proceed to erase the pool

    set fs to zfs and profile to mirror

    start array

    format pool

     

    And yes, leave it open for now, I think it's something LT will want to fix.

    Link to comment

    That worked, thanks!

    I added a few steps, but the end result was the same. I first selected auto as the file system type, and as expected, it imported the existing BTRFS pool. Then I did the erase and reset.

     

    BTW, the three way default after I did the erase and selected ZFS was RAID0, don't know if that's intended.

    Link to comment
    3 minutes ago, JonathanM said:

    don't know if that's intended.

    It's the default for now, but the plan is to change that in the future.

    Link to comment

    Is it possible to have 2 or more mirrored cache pools with zfs? I have previously successfully created an SSD mirrored cache pool with zfs but when following the same process to create another cache pool with zfs mirror with a pair of HDDs I get the error as indicated earlier in this thread and cannot resolve it by following the instruction. 
     

    thanks 

    Edited by BigFam
    Clarification
    Link to comment
    44 minutes ago, BigFam said:

    Is it possible to have 2 or more mirrored cache pools with zfs?

    Yes, if it's failing post the diags after doing it.

    Link to comment


    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.