eins

Have you been able to fix this? I'm facing exactly the same problem. /Edit: Seems like this issue is a little older... here is a fix from 1 year ago.

I pressed "y" like 50 times and some files still seem to loop, so i went with "n"... after some research "a" seems to be the right answer to keep looping until the file is restored... looking into this and the (non existent) documentation on this topic makes me really loose trust in btrfs. Why is "a" even keep looping (figured it was "abort"), and why can't i pass this as an option when running restore, but have to do it for every single file? Seems like there even is a open bug ticket about exactly this behavoir for over 1 year... what the hell btrfs?

Thank you. I just tried these, as written above, #1 didnt work at all, and #2 seems to "loop" on any file bigger than a few megabyte (like all the vm disk files...)

Hi, i noticed that one of my VMs had a filesystem error (filesystem in read only mode), so i tried restarting it. It did not come back up and started in an EFI shell, so i went into the VM config and wanted to remove some attached disks... well after saving the VM was gone from Unraid. I was also not able to re-create it, so i went into to console and noticed the whole cache filesystem was in read-only mode. I completely restarted Unraid, and after i started the array i got the "Unmountable: No file system" error for my cache. Diagnostics is attached The two cache drives are Samsung_SSD_850_PRO_512GB_S2BENWAJ803574W - 512 GB (sdg) 2CT500BX100SSD1_1452F000F1C4 - 500 GB (sdj) EDIT: I tried the part about unmountable btrfs filesystems from the FAQ btrfs restore seems to mostly work, but every file thats bigger than a few Megabytes seems to hang with an "We seem to be looping a lot on /mnt/disk3/restore2/appdata/pihole/pihole/pihole-FTL.db, do you want to keep going on ? (y/N/a)" error... einsserv-diagnostics-20210512-1653.zip

I triggered a full rebalance from the cache options and this seems to have resolved it. Seems like the displayed storage was always that of the configuration before that (so my above values were pretty much switched). Still weird.

Hello, i can't make sense of how the Unraid cache drive size behaves. With 1 drive its the size of the drive. Thats clear. With 2 drives its a bigger than the bigger of the 2 drives... thats werid, i expected less, because as i unterstood it changes so some "kind of raid1" (simply spoken) I currently have a 500GB and a 512GB SSD, and this gives me a cache drive of... 644GB. And it says it is protected (which should be impossible, since no single of the 2 drives can hold that much). Now comes the really weird part. I add another 275GB drive... and cache pool capacity goes down to 522GB. What the? Can anyone explain this to me or lead me in the right direction?