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

Zitat von ryecoaaron

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.

Zitat von ryecoaaron

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

Zitat von GTvert90

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.

Version : 1.2
  Creation Time : Fri Feb  1 16:23:29 2019
     Raid Level : raid5
     Array Size : 10477568 (9.99 GiB 10.73 GB)
  Used Dev Size : 5238784 (5.00 GiB 5.36 GB)
   Raid Devices : 3
  Total Devices : 4
    Persistence : Superblock is persistent


    Update Time : Fri Feb  1 16:24:52 2019
          State : active
 Active Devices : 3
Working Devices : 4
 Failed Devices : 0
  Spare Devices : 1


         Layout : left-symmetric
     Chunk Size : 512K


           Name : OMV3-VM:RAID5  (local to host OMV3-VM)
           UUID : c78d3f3b:694049fe:87674a93:25445edf
         Events : 20


    Number   Major   Minor   RaidDevice State
       0       8       16        0      active sync   /dev/sdb
       1       8       32        1      active sync   /dev/sdc
       2       8       48        2      active sync   /dev/sdd


       3       8       64        -      spare   /dev/sde

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.