OMV 3.X versus OMV 2.X; "Growing" a RAID 5 array

    • ryecoaaron wrote:

      There are "should"s in the statement While it should work, it may do something wrong.
      The last time I looked at this, which was a couple years ago (OMV 3.X), the mdadm RAID "Grow" button added a drive as a spare. It didn't actually grow the array. There's a thread from that time frame concerning this behavior.

      As of the last time I checked OMV 3, (about a year ago) the Grow button would only add a spare.

      Video Guides :!: New User Guide :!: Docker Guides :!: Pi-hole in Docker
      Good backup takes the "drama" out of computing.
      ____________________________________
      Primary: OMV 4.1.17, ThinkServer TS140, 12GB ECC, 16GB USB boot, 4TB+4TB zmirror, 3TB client backup.
      OMV 4.1.17, Intel Server SC5650HCBRP, 32GB ECC, 16GB USB boot, UnionFS+SNAPRAID
      Backup: OMV 4.1.9, Acer RC-111, 4GB, 32GB USB boot, 3TB+3TB zmirror, 4TB Rsync'ed disk
    • flmaxey wrote:

      As of the last time I checked OMV 3, (about a year ago) the Grow button would only add a spare.
      It adds the drive and then does two grows - github.com/openmediavault/open…ned/rpc/raidmgmt.inc#L308
      omv 4.1.19 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • ryecoaaron wrote:

      It adds the drive and then does two grows - github.com/openmediavault/open…ned/rpc/raidmgmt.inc#L308
      In OMV4, I just checked and you're right.
      _____________________________________________

      But the user in this thread is still on OMV3

      GTvert90 wrote:

      Should I reboot? I'm on OMV3.
      _____________________________________________

      I have an OMV3 VM built so I checked it again. As it was before, the "Grow" button adds a drive as a spare (details below) with no option in the GUI to actually grow (as in restripe) the array.

      Source Code

      1. Version : 1.2
      2. Creation Time : Fri Feb 1 16:23:29 2019
      3. Raid Level : raid5
      4. Array Size : 10477568 (9.99 GiB 10.73 GB)
      5. Used Dev Size : 5238784 (5.00 GiB 5.36 GB)
      6. Raid Devices : 3
      7. Total Devices : 4
      8. Persistence : Superblock is persistent
      9. Update Time : Fri Feb 1 16:24:52 2019
      10. State : active
      11. Active Devices : 3
      12. Working Devices : 4
      13. Failed Devices : 0
      14. Spare Devices : 1
      15. Layout : left-symmetric
      16. Chunk Size : 512K
      17. Name : OMV3-VM:RAID5 (local to host OMV3-VM)
      18. UUID : c78d3f3b:694049fe:87674a93:25445edf
      19. Events : 20
      20. Number Major Minor RaidDevice State
      21. 0 8 16 0 active sync /dev/sdb
      22. 1 8 32 1 active sync /dev/sdc
      23. 2 8 48 2 active sync /dev/sdd
      24. 3 8 64 - spare /dev/sde
      Display All
      At the time (a couple years ago), I assumed that this was intended behavior - that Dev's (yourself, Volker, etc.) were attempting to discourage growing RAID5 arrays because of the risks.

      Video Guides :!: New User Guide :!: Docker Guides :!: Pi-hole in Docker
      Good backup takes the "drama" out of computing.
      ____________________________________
      Primary: OMV 4.1.17, ThinkServer TS140, 12GB ECC, 16GB USB boot, 4TB+4TB zmirror, 3TB client backup.
      OMV 4.1.17, Intel Server SC5650HCBRP, 32GB ECC, 16GB USB boot, UnionFS+SNAPRAID
      Backup: OMV 4.1.9, Acer RC-111, 4GB, 32GB USB boot, 3TB+3TB zmirror, 4TB Rsync'ed disk
    • flmaxey wrote:

      But the user in this thread is still on OMV3
      OMV3 does an add then one grow - github.com/openmediavault/open…ned/rpc/raidmgmt.inc#L296

      flmaxey wrote:

      At the time (a couple years ago), I assumed that this was intended behavior - that Dev's (yourself, Volker, etc.) were attempting to discourage growing RAID5 arrays because of the risks.
      I don't think that was intentional but I honestly don't remember. Just one more reason to upgrade to OMV 4.x.
      omv 4.1.19 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!