Problem with disk space inscrease

crahier · Jan 18th 2021

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

geaves · Jan 19th 2021

You need to expand the file system, what's the output of cat /proc/mdstat

crahier · Jan 19th 2021

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

geaves · Jan 19th 2021

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

crahier · Jan 19th 2021

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

geaves · Jan 19th 2021

I take it it's OK now

crahier · Jan 19th 2021

It's strange because in the GUI, I don't see the 10.9 Tb :

I can see it in the RAID Management :

is it normal ?

crahier · Jan 19th 2021

When I launch df -h, I've this :

Code

root@openmediavault:~# df -h
Filesystem      Size  Used Avail Use% Mounted on
udev            3.7G     0  3.7G   0% /dev
tmpfs           768M   35M  734M   5% /run
/dev/sde2        49G  6.8G   40G  15% /
tmpfs           3.8G     0  3.8G   0% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs           3.8G     0  3.8G   0% /sys/fs/cgroup
/dev/sde1       511M  140K  511M   1% /boot/efi
tmpfs           3.8G   12K  3.8G   1% /tmp
/dev/md0        7.3T  2.8T  4.6T  38% /srv/dev-disk-by-label-Device1
overlay          49G  6.8G   40G  15% /var/lib/docker/overlay2/52eae51a14907df545adf956ba13159e2b3e1677ca4fb91457f8fd47fbbafdd3/merged
overlay          49G  6.8G   40G  15% /var/lib/docker/overlay2/6483803965bd87115c3fea12060e9e17bb1c69f243c5427f5342f7add6b255f1/merged
tmpfs           768M     0  768M   0% /run/user/0

Display More

geaves · Jan 19th 2021

Quote from crahier

is it normal

No, but now I can see what might be the cause, you've formatted the raid with btrfs, there was some discussion in respect of using btrfs on mdadm.

crahier · Jan 19th 2021

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

geaves · Jan 19th 2021

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.

crahier · Jan 19th 2021

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.

geaves · Jan 19th 2021

Quote from crahier

I've got an error

Then that doesn't work in this case, try btrfs filesystem show

crahier · Jan 19th 2021

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

geaves · Jan 19th 2021

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 <>

crahier · Jan 19th 2021

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 ...

crahier · Jan 19th 2021

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.

geaves · Jan 19th 2021

Quote from crahier

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

crahier · Jan 19th 2021

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

Many thanks for you help, I was completly lost !!!

Christophe

geaves · Jan 19th 2021

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.

Problem with disk space inscrease

geaves Jan 19th 2021

Participate now!

Tags