Kall Posted May 31, 2019 #1 Posted May 31, 2019 (edited) Hi guys, For some of you who wish to expand btrfs Syno volume after disk space increased. Before: df -Th btrfs fi show mdadm --detail /dev/md2 SSH commands: syno_poweroff_task -d mdadm --stop /dev/md2 parted /dev/sda resizepart 3 100% mdadm --assemble --update=devicesize /dev/md2 /dev/sda3 mdadm --grow /dev/md2 --size=max reboot btrfs filesystem resize max /dev/md2 After: df -Th btrfs fi show mdadm --detail /dev/md2 Voila Kall Edited June 4, 2019 by Polanskiman Added proper code tags. Please use them in the future. 2 Quote
polanskiman Posted June 4, 2019 #2 Posted June 4, 2019 Hello. How is this a question? I am moving this topic from the General Questions section to the Tutorials and Guides section of the forum. Also in the future please use proper code tags. Quote
Kall Posted June 4, 2019 Author #3 Posted June 4, 2019 1 hour ago, Polanskiman said: Hello. How is this a question? I am moving this topic from the General Questions section to the Tutorials and Guides section of the forum. Also in the future please use proper code tags. Your right!, Thanks Kall Quote
XTIAN Posted July 17, 2019 #4 Posted July 17, 2019 On 5/31/2019 at 3:59 PM, Kall said: Hi guys, For some of you who wish to expand btrfs Syno volume after disk space increased. Before: df -Th btrfs fi show mdadm --detail /dev/md2 SSH commands: syno_poweroff_task -d mdadm --stop /dev/md2 parted /dev/sda resizepart 3 100% mdadm --assemble --update=devicesize /dev/md2 /dev/sda3 mdadm --grow /dev/md2 --size=max reboot btrfs filesystem resize max /dev/md2 After: df -Th btrfs fi show mdadm --detail /dev/md2 Voila Kall FANTASTIC!! Thanks for your feed! Xtian Quote
ilovepancakes Posted November 4, 2019 #5 Posted November 4, 2019 (edited) On 5/31/2019 at 9:59 AM, Kall said: mdadm --grow /dev/md2 --size=max @Kall So after this command I get an error that the type of array cannot have its size adjusted/expanded but if I follow the rest of the steps anyway, it all seems to work and the volume is expanded. What is this non-working command actually supposed to do and do I have any side effects of not being able to use it? EDIT: I was using JBOD mode with a single disk on the volume I tried this with. Confirming that trying this on a Basic mode volume, the above command works and returns a normal output. So I guess on JBOD volumes this command doesn't do anything. That being said, is Basic or JBOD better performing with 1 disk? Edited November 4, 2019 by ilovepancakes Quote
SmokinCuppaJoe Posted May 30, 2020 #6 Posted May 30, 2020 Kall that looks to be a pain in the butt. On VMware you might as well make the .VMDK thin provisioned. Make the VMDK disk size the max your storage will support, i.e. if you have 30TB of space on it use 80% or 24TB and then on the DSM Volume configure that to what you need for the moment, i.e. Allocate Size 1000GB. In this way if you need to allocate more space on that Volume you just re configure the volume and key in the new Allocate size you need. The Pool could be Basic(one disk ), JBOD(two or more disks) or RAID0(two or more disks). I really thing with VMware it will not matter the number of disks as you do not have multiple virtual SAS/SCSI controllers to spread the IO across. Quote
Balrog Posted September 14, 2020 #7 Posted September 14, 2020 Hello! I just expand a vmdk in a virtual Xpenology (a simple basic volume). The instructions are working very good besides two little differences: 1. After "mdadm --grow /dev/md2 --size=max" I have to use "lvextend -l +100%FREE /dev/vg1/volume_1" to grow the volume itself. 2. "btrfs filesystem resize max ..." does not work for me. I have to use "Storage Manager - Volume - Action - Expand" instead in DSM itself. But after all, the expanding works very well. Thanks very much for the information! Quote
Burny Posted December 22, 2022 #8 Posted December 22, 2022 Hey guys, i know this topic is quite old, but i also like to extend my volume on DSM 7.1.1. Unfortunately the command "syno_poweroff_task -d" isn't available anymore in DSM 7. I have found something similar, but it's still not working for me. It's this one: "synostgvolume --unmount -p volume1". When i then try to run "mdadm --stop /dev/md2", it tells me "mdadm: Cannot get exclusive access to /dev/md2:Perhaps a running process, mounted filesystem or active volume group?". Do you guys know any solution for that? Thank you very much! With kind regards, Burny Quote
cwiggs Posted December 29, 2022 #9 Posted December 29, 2022 On 12/22/2022 at 4:11 AM, Burny said: Hey guys, i know this topic is quite old, but i also like to extend my volume on DSM 7.1.1. Unfortunately the command "syno_poweroff_task -d" isn't available anymore in DSM 7. I have found something similar, but it's still not working for me. It's this one: "synostgvolume --unmount -p volume1". When i then try to run "mdadm --stop /dev/md2", it tells me "mdadm: Cannot get exclusive access to /dev/md2:Perhaps a running process, mounted filesystem or active volume group?". Do you guys know any solution for that? Thank you very much! With kind regards, Burny I ran into this same issue and I just skipped the `mdadm --stop` command. Also after you reboot you will have to expand the filesystem via the gui since in 7.1.1 it seems like the `brtfs` command is missing in the cli. Quote
Oliveiras Posted July 2, 2023 #10 Posted July 2, 2023 On 12/22/2022 at 11:11 AM, Burny said: Hey guys, i know this topic is quite old, but i also like to extend my volume on DSM 7.1.1. Unfortunately the command "syno_poweroff_task -d" isn't available anymore in DSM 7. I have found something similar, but it's still not working for me. It's this one: "synostgvolume --unmount -p volume1". When i then try to run "mdadm --stop /dev/md2", it tells me "mdadm: Cannot get exclusive access to /dev/md2:Perhaps a running process, mounted filesystem or active volume group?". Do you guys know any solution for that? Thank you very much! With kind regards, Burny I'm on the same boat ! Any one done it on DSM 7.1 ? I also tried to skipp the `mdadm --stop` command as @cwiggs mentioned but no luck! Quote
dj_nsk Posted July 3, 2023 #11 Posted July 3, 2023 4 часа назад, Oliveiras сказал: Any one done it on DSM 7.1 ? Do you use virtual disks in ESXi for the DSM virtual machine? How did you manage to increase its size? And why don't you want to do it in a simple way: make a backup - delete the old disk - add a new disk - restore from backup? Quote
Oliveiras Posted July 3, 2023 #12 Posted July 3, 2023 17 hours ago, dj_nsk said: Do you use virtual disks in ESXi for the DSM virtual machine? How did you manage to increase its size? And why don't you want to do it in a simple way: make a backup - delete the old disk - add a new disk - restore from backup? I'm using proxmox but the principles are the same. I'm not trying to expand data volumes, it's the main system drive because a docker container fill the drive with logs. So I cannot copy the xpenology system volume to other drive. Quote
dj_nsk Posted July 4, 2023 #13 Posted July 4, 2023 4 часа назад, Oliveiras сказал: I'm using proxmox but the principles are the same. I'm not trying to expand data volumes, it's the main system drive because a docker container fill the drive with logs. So I cannot copy the xpenology system volume to other drive. then it's not clear at all - what kind of problem are you solving with using mdadm?? Quote
Oliveiras Posted July 4, 2023 #14 Posted July 4, 2023 21 hours ago, dj_nsk said: then it's not clear at all - what kind of problem are you solving with using mdadm?? I need to expand volume 1 that includes base system files: /dev/mapper/cachedev_1 btrfs 21G 21G 0 100% /volume1 Label: '2023.01.15-18:30:06 v42962' uuid: 2b590ef9-e408-48dd-bed5-e407b5b9bff2 Total devices 1 FS bytes used 20.13GiB devid 1 size 21.00GiB used 21.00GiB path /dev/mapper/cachedev_1 The comands mentioned on this topic don't work on DSM 7.1 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.