September 29, 20232 yr I'm trying to move my domains share from one cache pool to another (via the array) using the mover but keep getting a "Device or resource busy" error. I've disabled VM and Docker services in Settings and tried booting in safe mode too to eliminate the possibility of any plugins accessing the VMs but still says "Device or resource busy". I've successfully moved domains, appdata and system shares in the past following this method. Is there any way to see what process is using the file? Quote Sep 28 17:17:32 Phoebe emhttpd: shcmd (132): /usr/local/sbin/mover |& logger -t move & Sep 28 17:17:32 Phoebe move: mover: started Sep 28 17:17:32 Phoebe move: file: /mnt/cache_nvme/domains/Windows 10 Pro/vdisk1.img Sep 28 17:17:32 Phoebe move: create_parent: /mnt/cache_nvme/domains/Windows 10 Pro error: Device or resource busy Sep 28 17:17:32 Phoebe move: move_object: /mnt/cache_nvme/domains/Windows 10 Pro: Device or resource busy Sep 28 17:17:32 Phoebe move: file: /mnt/cache_nvme/domains/Abbay/vdisk1.img Sep 28 17:17:32 Phoebe move: create_parent: /mnt/cache_nvme/domains/Abbay error: Device or resource busy Sep 28 17:17:32 Phoebe move: move_object: /mnt/cache_nvme/domains/Abbay: Device or resource busy Sep 28 17:17:32 Phoebe move: file: /mnt/cache_nvme/domains/Windows 11 Pro/vdisk1.img Sep 28 17:17:32 Phoebe move: create_parent: /mnt/cache_nvme/domains/Windows 11 Pro error: Device or resource busy Sep 28 17:17:32 Phoebe move: move_object: /mnt/cache_nvme/domains/Windows 11 Pro: Device or resource busy Sep 28 17:17:33 Phoebe move: mover: finished
September 29, 20232 yr Author Sorry, forgot to attach them. Here you go. The only thing I've changed since I've been able to successfully move my domains folder with the mover is the format of the vm cache disk from btrfs to zfs. Could it be something with zfs? Thanks. phoebe-diagnostics-20230929-1036.zip
September 29, 20232 yr Community Expert 35 minutes ago, lazant said: Could it be something with zfs? That should be fine, but don't see why it's not working, let me try and a similar move.
September 30, 20232 yr Author Were you able to replicate the problem? Quote root@Phoebe:~# fuser -v /mnt/cache_nvme/domains/Abbay USER PID ACCESS COMMAND /mnt/cache_nvme/domains/Abbay: root kernel mount /mnt/cache_nvme/domains/Abbay
September 30, 20232 yr Community Expert 10 hours ago, lazant said: Were you able to replicate the problem? Nope, are you using nested datasets? In doubt post the output of: zfs list -t all
September 30, 20232 yr Author I do have nested datasets. Would that cause the problem? root@Phoebe:~# zfs list -t all NAME USED AVAIL REFER MOUNTPOINT cache_nvme 338G 6.98T 104K /mnt/cache_nvme cache_nvme/domains 338G 6.98T 112K /mnt/cache_nvme/domains cache_nvme/domains@2023-09-20-160630 8K - 112K - cache_nvme/domains/Abbay 138G 6.98T 100G /mnt/cache_nvme/domains/Abbay cache_nvme/domains/Abbay@2023-09-20-160133 2.59G - 100G - cache_nvme/domains/Abbay@2023-09-20-170610 2.13G - 100G - cache_nvme/domains/Abbay@2023-09-20-222020 3.80G - 100G - cache_nvme/domains/Abbay@2023-09-24-193824 7.74G - 100G - cache_nvme/domains/Windows 10 Pro 100G 6.98T 100G /mnt/cache_nvme/domains/Windows 10 Pro cache_nvme/domains/Windows 10 Pro@2023-09-20-160535 0B - 100G - cache_nvme/domains/Windows 11 Pro 100G 6.98T 100G /mnt/cache_nvme/domains/Windows 11 Pro cache_nvme/domains/Windows 11 Pro@2023-09-20-160541 0B - 100G - cache_nvme_vm 6.08M 3.60T 96K /mnt/cache_nvme_vm cache_ssd 2.75T 4.37T 120K /mnt/cache_ssd cache_ssd/appdata 214M 4.37T 112K /mnt/cache_ssd/appdata cache_ssd/appdata@2023-09-20-160600 0B - 112K - cache_ssd/appdata/DiskSpeed 8.56M 4.37T 8.56M /mnt/cache_ssd/appdata/DiskSpeed cache_ssd/appdata/DiskSpeed@2023-09-20-160600 0B - 8.56M - cache_ssd/appdata/firefox 205M 4.37T 205M /mnt/cache_ssd/appdata/firefox cache_ssd/appdata/firefox@2023-09-20-160600 0B - 205M - cache_ssd/asteriabackup 2.74T 4.37T 2.74T /mnt/cache_ssd/asteriabackup cache_ssd/system 6.16G 4.37T 2.66G /mnt/cache_ssd/system cache_ssd/system@2023-09-20-160606 3.50G - 5.75G - disk1 85.9G 16.2T 112K /mnt/disk1 disk1/backup 70.2G 16.2T 70.2G /mnt/disk1/backup disk1/domains 96K 16.2T 96K /mnt/disk1/domains disk1/isos 15.7G 16.2T 15.7G /mnt/disk1/isos disk2 11.6M 16.2T 96K /mnt/disk2 disk3 7.71T 8.53T 7.71T /mnt/disk3 disk4 13.5T 2.77T 96K /mnt/disk4 disk4/TV Shows 13.5T 2.77T 13.5T /mnt/disk4/TV Shows disk5 9.70T 6.53T 104K /mnt/disk5 disk5/TV Shows 9.70T 6.53T 9.70T /mnt/disk5/TV Shows Edited September 30, 20232 yr by lazant
October 1, 20232 yr Community Expert 14 hours ago, lazant said: Would that cause the problem? It will, mover does not support nested datasets, so it won't be able to move those, and likely the cause of errors you are seeing.
October 1, 20232 yr Community Expert Solution For your case I would suggest using send/receive with the replication option, it will replicate the filesystem together with all nested datasets, and you can send that directly to the final destination, assuming it's also zfs.
October 3, 20232 yr Author Thanks Jorge, I'm away right now but will try this weekend. I appreciate the help.
October 20, 20232 yr Author I'm still new to zfs so this took me awhile to read up on and get the confidence to do but I've moved the nested datasets with the VMs from my old cache to my new one using: zfs send -wR cache_nvme/domains/Abbay@2023-09-24-193824 | zfs receive -Fdu cache_nvme_vm zfs send -wR cache_nvme/domains/Windows\ 10\ Pro@2023-10-20-102957 | zfs receive -Fdu cache_nvme_vm zfs send -wR cache_nvme/domains/Windows\ 11\ Pro@2023-10-20-103005 | zfs receive -Fdu cache_nvme_vm Here is my new dataset structure: NAME USED AVAIL REFER MOUNTPOINT cache_nvme 345G 6.98T 104K /mnt/cache_nvme cache_nvme/domains 345G 6.98T 112K /mnt/cache_nvme/domains cache_nvme/domains@2023-09-20-160630 64K - 112K - cache_nvme/domains/Abbay 145G 6.98T 100G /mnt/cache_nvme/domains/Abbay cache_nvme/domains/Abbay@2023-09-20-160133 2.59G - 100G - cache_nvme/domains/Abbay@2023-09-20-170610 2.13G - 100G - cache_nvme/domains/Abbay@2023-09-20-222020 3.80G - 100G - cache_nvme/domains/Abbay@2023-09-24-193824 8.49G - 100G - cache_nvme/domains/Abbay@2023-10-19-214718 2.50G - 100G - cache_nvme/domains/Windows 10 Pro 100G 6.98T 100G /mnt/cache_nvme/domains/Windows 10 Pro cache_nvme/domains/Windows 10 Pro@2023-09-20-160535 56K - 100G - cache_nvme/domains/Windows 10 Pro@2023-10-20-102957 0B - 100G - cache_nvme/domains/Windows 11 Pro 100G 6.98T 100G /mnt/cache_nvme/domains/Windows 11 Pro cache_nvme/domains/Windows 11 Pro@2023-09-20-160541 56K - 100G - cache_nvme/domains/Windows 11 Pro@2023-10-20-103005 0B - 100G - cache_nvme_vm 342G 3.27T 104K /mnt/cache_nvme_vm cache_nvme_vm/domains 342G 3.27T 96K /mnt/cache_nvme_vm/domains cache_nvme_vm/domains/Abbay 142G 3.27T 100G /mnt/cache_nvme_vm/domains/Abbay cache_nvme_vm/domains/Abbay@2023-09-20-160133 2.59G - 100G - cache_nvme_vm/domains/Abbay@2023-09-20-170610 2.13G - 100G - cache_nvme_vm/domains/Abbay@2023-09-20-222020 3.80G - 100G - cache_nvme_vm/domains/Abbay@2023-09-24-193824 8.49G - 100G - cache_nvme_vm/domains/Abbay@2023-10-19-214718 0B - 100G - cache_nvme_vm/domains/Windows 10 Pro 100G 3.27T 100G /mnt/cache_nvme_vm/domains/Windows 10 Pro cache_nvme_vm/domains/Windows 10 Pro@2023-09-20-160535 56K - 100G - cache_nvme_vm/domains/Windows 10 Pro@2023-10-20-102957 0B - 100G - cache_nvme_vm/domains/Windows 11 Pro 100G 3.27T 100G /mnt/cache_nvme_vm/domains/Windows 11 Pro cache_nvme_vm/domains/Windows 11 Pro@2023-09-20-160541 56K - 100G - cache_nvme_vm/domains/Windows 11 Pro@2023-10-20-103005 0B - 100G - cache_ssd 6.49G 7.12T 120K /mnt/cache_ssd cache_ssd/appdata 214M 7.12T 112K /mnt/cache_ssd/appdata cache_ssd/appdata@2023-09-20-160600 0B - 112K - cache_ssd/appdata/DiskSpeed 8.56M 7.12T 8.56M /mnt/cache_ssd/appdata/DiskSpeed cache_ssd/appdata/DiskSpeed@2023-09-20-160600 0B - 8.56M - cache_ssd/appdata/firefox 205M 7.12T 205M /mnt/cache_ssd/appdata/firefox cache_ssd/appdata/firefox@2023-09-20-160600 0B - 205M - cache_ssd/asteriabackup 436K 7.12T 436K /mnt/cache_ssd/asteriabackup cache_ssd/system 6.15G 7.12T 2.65G /mnt/cache_ssd/system cache_ssd/system@2023-09-20-160606 3.50G - 5.75G - disk1 4.37T 11.9T 112K /mnt/disk1 disk1/asteriabackup 4.28T 11.9T 4.28T /mnt/disk1/asteriabackup disk1/backup 70.2G 11.9T 70.2G /mnt/disk1/backup disk1/isos 15.7G 11.9T 15.7G /mnt/disk1/isos disk2 13.9M 16.2T 96K /mnt/disk2 disk3 7.71T 8.53T 7.71T /mnt/disk3 disk4 13.5T 2.77T 96K /mnt/disk4 disk4/TV Shows 13.5T 2.77T 13.5T /mnt/disk4/TV Shows disk5 9.70T 6.53T 104K /mnt/disk5 disk5/TV Shows 9.70T 6.53T 9.70T /mnt/disk5/TV Shows My question now is how to go about switching the domains share from cache_nvme/domains to cache_nvme_vm/domains? Thanks again for your help.
October 20, 20232 yr Community Expert You should just need to go to VM settings and the VMs page and update all the relevant paths.
October 30, 20232 yr Author Thanks Jorge, all I needed to do was delete the dataset with the VMs on the old pool and I was good to go off the new pool. I'm curious how unraid handles there being duplicate file names on two different drives across one share? When I sent the VM dataset to the new drive using zfs send it looked like this: cache_nvme/domains/Abbay cache_nvme_vm/domains/Abbay
October 31, 20232 yr Community Expert 10 hours ago, lazant said: I'm curious how unraid handles there being duplicate file names on two different drives across one share? It will show the ones on the fist pool, it's alphabetical.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.