ZFS detach mirrored drives in a pool

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP












3















I have an older (2-3 years) NAS running FreeNAS. I figured its time to upgrade some of the hard drives. Here's the current status:



 NAME STATE READ WRITE CKSUM 
Pool1 ONLINE 0 0 0
raidz1 ONLINE 0 0 0
ada3p2 ONLINE 0 0 0
ada4p2 ONLINE 0 0 0
ada5p2 ONLINE 0 0 0
mirror ONLINE 0 0 0
ada1p2 ONLINE 0 0 0
ada2p2 ONLINE 0 0 0


The drives in RaidZ1 are all 1GB and will stay.



What's the best way to add 2 or 3 more 1GB hard drives to RaidZ1 and completely remove the mirrored drives, which are 500GB only, without:



  • Copying the data to a temporary holding spot

  • Recreating the pool

  • Copying it back

The pool is about 50% full, so I'm not even sure there's data on the mirrored drives.



How to check or where to begin?










share|improve this question
























  • Surely you mean 1 TB instead of "1GB", right?

    – Kenny Evitt
    Mar 30 '18 at 0:38















3















I have an older (2-3 years) NAS running FreeNAS. I figured its time to upgrade some of the hard drives. Here's the current status:



 NAME STATE READ WRITE CKSUM 
Pool1 ONLINE 0 0 0
raidz1 ONLINE 0 0 0
ada3p2 ONLINE 0 0 0
ada4p2 ONLINE 0 0 0
ada5p2 ONLINE 0 0 0
mirror ONLINE 0 0 0
ada1p2 ONLINE 0 0 0
ada2p2 ONLINE 0 0 0


The drives in RaidZ1 are all 1GB and will stay.



What's the best way to add 2 or 3 more 1GB hard drives to RaidZ1 and completely remove the mirrored drives, which are 500GB only, without:



  • Copying the data to a temporary holding spot

  • Recreating the pool

  • Copying it back

The pool is about 50% full, so I'm not even sure there's data on the mirrored drives.



How to check or where to begin?










share|improve this question
























  • Surely you mean 1 TB instead of "1GB", right?

    – Kenny Evitt
    Mar 30 '18 at 0:38













3












3








3


0






I have an older (2-3 years) NAS running FreeNAS. I figured its time to upgrade some of the hard drives. Here's the current status:



 NAME STATE READ WRITE CKSUM 
Pool1 ONLINE 0 0 0
raidz1 ONLINE 0 0 0
ada3p2 ONLINE 0 0 0
ada4p2 ONLINE 0 0 0
ada5p2 ONLINE 0 0 0
mirror ONLINE 0 0 0
ada1p2 ONLINE 0 0 0
ada2p2 ONLINE 0 0 0


The drives in RaidZ1 are all 1GB and will stay.



What's the best way to add 2 or 3 more 1GB hard drives to RaidZ1 and completely remove the mirrored drives, which are 500GB only, without:



  • Copying the data to a temporary holding spot

  • Recreating the pool

  • Copying it back

The pool is about 50% full, so I'm not even sure there's data on the mirrored drives.



How to check or where to begin?










share|improve this question
















I have an older (2-3 years) NAS running FreeNAS. I figured its time to upgrade some of the hard drives. Here's the current status:



 NAME STATE READ WRITE CKSUM 
Pool1 ONLINE 0 0 0
raidz1 ONLINE 0 0 0
ada3p2 ONLINE 0 0 0
ada4p2 ONLINE 0 0 0
ada5p2 ONLINE 0 0 0
mirror ONLINE 0 0 0
ada1p2 ONLINE 0 0 0
ada2p2 ONLINE 0 0 0


The drives in RaidZ1 are all 1GB and will stay.



What's the best way to add 2 or 3 more 1GB hard drives to RaidZ1 and completely remove the mirrored drives, which are 500GB only, without:



  • Copying the data to a temporary holding spot

  • Recreating the pool

  • Copying it back

The pool is about 50% full, so I'm not even sure there's data on the mirrored drives.



How to check or where to begin?







zfs freenas nas






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jul 2 '14 at 17:38









polym

6,74143158




6,74143158










asked Jul 1 '14 at 14:53









dopefreshuserdopefreshuser

192




192












  • Surely you mean 1 TB instead of "1GB", right?

    – Kenny Evitt
    Mar 30 '18 at 0:38

















  • Surely you mean 1 TB instead of "1GB", right?

    – Kenny Evitt
    Mar 30 '18 at 0:38
















Surely you mean 1 TB instead of "1GB", right?

– Kenny Evitt
Mar 30 '18 at 0:38





Surely you mean 1 TB instead of "1GB", right?

– Kenny Evitt
Mar 30 '18 at 0:38










2 Answers
2






active

oldest

votes


















0














The only way to do it is as you suggest: copy all the datasets to a new pool and rebuild this one. zfs does not support extending raidz1's by adding drives to it, and it doesn't support removing top-level vdevs either (which is what 'mirror' is).






share|improve this answer























  • I know that seems the obvious solutions but there has to be something more elegant/geeky that can be done. After all ZFS is the best filesystem on earth right? :)

    – dopefreshuser
    Jul 2 '14 at 14:50











  • update - freebsdfoundation.org/blog/… and delphix.com/blog/delphix-engineering/openzfs-device-removal

    – mmusante
    Jun 14 '18 at 0:21


















0














First before making any changes, you may want to consider kicking off a zpool scrub to ensure everything is healthy.



Going off memory (so you'll want to confirm), I believe the option you'll want is zpool add to be able to grow your existing raidz pool.



To easily move the data around, you can use zfs send|receive, along with using snapshots for incremental send|receives.






share|improve this answer






















    Your Answer








    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "106"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader:
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    ,
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













    draft saved

    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f140180%2fzfs-detach-mirrored-drives-in-a-pool%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    The only way to do it is as you suggest: copy all the datasets to a new pool and rebuild this one. zfs does not support extending raidz1's by adding drives to it, and it doesn't support removing top-level vdevs either (which is what 'mirror' is).






    share|improve this answer























    • I know that seems the obvious solutions but there has to be something more elegant/geeky that can be done. After all ZFS is the best filesystem on earth right? :)

      – dopefreshuser
      Jul 2 '14 at 14:50











    • update - freebsdfoundation.org/blog/… and delphix.com/blog/delphix-engineering/openzfs-device-removal

      – mmusante
      Jun 14 '18 at 0:21















    0














    The only way to do it is as you suggest: copy all the datasets to a new pool and rebuild this one. zfs does not support extending raidz1's by adding drives to it, and it doesn't support removing top-level vdevs either (which is what 'mirror' is).






    share|improve this answer























    • I know that seems the obvious solutions but there has to be something more elegant/geeky that can be done. After all ZFS is the best filesystem on earth right? :)

      – dopefreshuser
      Jul 2 '14 at 14:50











    • update - freebsdfoundation.org/blog/… and delphix.com/blog/delphix-engineering/openzfs-device-removal

      – mmusante
      Jun 14 '18 at 0:21













    0












    0








    0







    The only way to do it is as you suggest: copy all the datasets to a new pool and rebuild this one. zfs does not support extending raidz1's by adding drives to it, and it doesn't support removing top-level vdevs either (which is what 'mirror' is).






    share|improve this answer













    The only way to do it is as you suggest: copy all the datasets to a new pool and rebuild this one. zfs does not support extending raidz1's by adding drives to it, and it doesn't support removing top-level vdevs either (which is what 'mirror' is).







    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Jul 2 '14 at 0:38









    mmusantemmusante

    61736




    61736












    • I know that seems the obvious solutions but there has to be something more elegant/geeky that can be done. After all ZFS is the best filesystem on earth right? :)

      – dopefreshuser
      Jul 2 '14 at 14:50











    • update - freebsdfoundation.org/blog/… and delphix.com/blog/delphix-engineering/openzfs-device-removal

      – mmusante
      Jun 14 '18 at 0:21

















    • I know that seems the obvious solutions but there has to be something more elegant/geeky that can be done. After all ZFS is the best filesystem on earth right? :)

      – dopefreshuser
      Jul 2 '14 at 14:50











    • update - freebsdfoundation.org/blog/… and delphix.com/blog/delphix-engineering/openzfs-device-removal

      – mmusante
      Jun 14 '18 at 0:21
















    I know that seems the obvious solutions but there has to be something more elegant/geeky that can be done. After all ZFS is the best filesystem on earth right? :)

    – dopefreshuser
    Jul 2 '14 at 14:50





    I know that seems the obvious solutions but there has to be something more elegant/geeky that can be done. After all ZFS is the best filesystem on earth right? :)

    – dopefreshuser
    Jul 2 '14 at 14:50













    update - freebsdfoundation.org/blog/… and delphix.com/blog/delphix-engineering/openzfs-device-removal

    – mmusante
    Jun 14 '18 at 0:21





    update - freebsdfoundation.org/blog/… and delphix.com/blog/delphix-engineering/openzfs-device-removal

    – mmusante
    Jun 14 '18 at 0:21













    0














    First before making any changes, you may want to consider kicking off a zpool scrub to ensure everything is healthy.



    Going off memory (so you'll want to confirm), I believe the option you'll want is zpool add to be able to grow your existing raidz pool.



    To easily move the data around, you can use zfs send|receive, along with using snapshots for incremental send|receives.






    share|improve this answer



























      0














      First before making any changes, you may want to consider kicking off a zpool scrub to ensure everything is healthy.



      Going off memory (so you'll want to confirm), I believe the option you'll want is zpool add to be able to grow your existing raidz pool.



      To easily move the data around, you can use zfs send|receive, along with using snapshots for incremental send|receives.






      share|improve this answer

























        0












        0








        0







        First before making any changes, you may want to consider kicking off a zpool scrub to ensure everything is healthy.



        Going off memory (so you'll want to confirm), I believe the option you'll want is zpool add to be able to grow your existing raidz pool.



        To easily move the data around, you can use zfs send|receive, along with using snapshots for incremental send|receives.






        share|improve this answer













        First before making any changes, you may want to consider kicking off a zpool scrub to ensure everything is healthy.



        Going off memory (so you'll want to confirm), I believe the option you'll want is zpool add to be able to grow your existing raidz pool.



        To easily move the data around, you can use zfs send|receive, along with using snapshots for incremental send|receives.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Feb 3 '17 at 22:19









        sleepyweaselsleepyweasel

        88329




        88329



























            draft saved

            draft discarded
















































            Thanks for contributing an answer to Unix & Linux Stack Exchange!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid


            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.

            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f140180%2fzfs-detach-mirrored-drives-in-a-pool%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown






            Popular posts from this blog

            How to check contact read email or not when send email to Individual?

            Bahrain

            Postfix configuration issue with fips on centos 7; mailgun relay