Problem with disk space inscrease

  • Hello,


    I have a problem. I initially created a NAS with 3 Western Digital Red Pro 4 Tb disks in RAID 5.


    Everything went well, the space was 7.28 TB.


    I added a 4th disk, I enlarged the disk space but in the screen Storage -> Files System, I see 7.28 TB while if I go in the screen Storage -> Raid management, I see 10.92 TB (which is normal).


    How do I make so that these 11 TB are actually used by the NAS ?


    I don't understand where's the problem ;(


    Thanks fo you help.


    Kind regards,


    Christophe

  • Hi,


    Here's the result :

    Code
    Personalities : [raid6] [raid5] [raid4] [linear] [multipath] [raid0] [raid1] [raid10]
    md0 : active raid5 sda[0] sdb[3] sdc[1] sdd[2]
    11720658432 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4] [UUUU]
    bitmap: 0/30 pages [0KB], 65536KB chunk
    unused devices: <none>

    Thanks for your help.


    Christophe

  • ssh into omv as root and run mdadm --grow /dev/md0 --size=max for some reason you can expand the raid size but not the file system using the GUI

    Raid is not a backup! Would you go skydiving without a parachute?

  • Hi,


    Yes, it's strange :


    Code
    root@openmediavault:~# mdadm --grow /dev/md0 --size=max
    mdadm: component size of /dev/md0 has been set to 3906887680K
  • When I launch df -h, I've this :


  • Unfortunately, I can't change the format, I have too much data that I can't store anywhere else.


    Finally, will I have my 11 Tb or will I remain limited to 7.2 Tb?


    I'm not a Linux specialist at all :-(

  • OK I've found something on Xpenology after growing mdadm which you have done from the GUI and the command line it suggests you reboot, then ssh into omv and run btrfs filesystem resize max /dev/m0 will that work, I have no idea.

    Raid is not a backup! Would you go skydiving without a parachute?

  • I've got an error :

    Code
    root@openmediavault:~# btrfs filesystem resize max /dev/md0
    ERROR: resize works on mounted filesystems and accepts only
    directories as argument. Passing file containing a btrfs image
    would resize the underlying filesystem instead of the image.
  • Here's the result


    Code
    root@openmediavault:~# btrfs filesystem show
    Label: 'Device1' uuid: 2a3b4d97-9ede-4a99-85f2-7dd457283999
    Total devices 1 FS bytes used 2.75TiB
    devid 1 size 7.28TiB used 2.75TiB path /dev/md0
  • OK that returned something, perhaps you can figure this out from here but in respect of the error "accepts only directories as argument"


    Would suggest using btrfs filesystem resize max </path/to/md0> obviously without the <>

    Raid is not a backup! Would you go skydiving without a parachute?

  • I tried


    Code
    root@openmediavault:~# btrfs filesystem resize 1:max /dev/md0
    ERROR: resize works on mounted filesystems and accepts only
    directories as argument. Passing file containing a btrfs image
    would resize the underlying filesystem instead of the image.

    I also tried :


    Code
    root@openmediavault:~# btrfs filesystem resize max /dev/md0
    ERROR: resize works on mounted filesystems and accepts only
    directories as argument. Passing file containing a btrfs image
    would resize the underlying filesystem instead of the image.

    but without success ...

  • For test, I specified a value


    Code
    root@openmediavault:~# btrfs filesystem resize +100G /dev/md0
    ERROR: resize works on mounted filesystems and accepts only
    directories as argument. Passing file containing a btrfs image
    would resize the underlying filesystem instead of the image.
  • I tried

    None of that will work it needs to be the 'path' where the raid is, try looking under /srv it may not say md0 it might just be the device name, and it needs to be the complete path.


    For instance this is the path to one of my drives /srv/dev-disk-by-label-Docker

    Raid is not a backup! Would you go skydiving without a parachute?

  • Ok, I understood, I typed this :


    Code
    btrfs filesystem resize max /srv/dev-disk-by-label-Device1

    Now, it's ok, I've 10.92 Tb


    Greenshot-2021-01-19-14-11-20.png
    Many thanks for you help, I was completly lost !!!


    Christophe


  • that deserves something special


    I think we need to add more to the tags for future reference as I learnt something today as well, but glad you got it sorted.

    Raid is not a backup! Would you go skydiving without a parachute?

  • geaves

    Added the Label resolved

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!