maharmstone
Deadlock/Crash while transferring files onto drive
External SD crashes/deadlock while transferring large amounts of files. It works fine on Linux but crashes on Windows using version 1.9 on Windows 11
Any solutions?
Same issue here. It compoletely borked a windows install and I had to recover with a restore point
Just happened here too, fresh install on fresh created filesystem, while moving about 50 GiB of files from a NTFS drive to a btrfs one. Fortunately not crucial data in my case, but a critical issue nevertheless. Will try to revert to a previous version, as 1.9 is dangerous for one's data at the moment.
Just happened here too, fresh install on fresh created filesystem, while moving about 50 GiB of files from a NTFS drive to a btrfs one. Fortunately not crucial data in my case, but a critical issue nevertheless. Will try to revert to a previous version, as 1.9 is dangerous for one's data at the moment.
Unfortunately with 1.8.2 the exact same thing happened after transferring a bit less than 9GiB. In bothe cases rhe system became unstable even after trying to cancel the operation, windows would not shutdown (hung while attempting to do so, had to forcefully poweroff the machine by pressing the power button for a while).
Both drives are SSD SATA and have no hardware defects. Windows 11 fully updated.
I'll keep the setup for a while (although I won't use it for serious data, as it is an hazard), can't promise I'll do it for much long, but I'm available to test anything if you want for a while, so please tell me how can I help. Although I believe this should be easy to reproduce in a fully updated Windows 11 machine with a few NTFS drives and attempting to move some dozens of GB to a btrfs drive.
This just happened to me twice on my desktop and once on my laptop. At this point I am thinking of just formating my drives to exFAT since this project hasn't been updated for about a year now. This could also just be an issue with windows breaking something that used to work perfectly fine until now.
Wonder if it’s related to this: https://www.neowin.net/news/report-microsofts-latest-windows-11-24h2-update-breaks-ssdshdds-may-corrupt-your-data/
Both SSDs that have given me issues were Phison SSDs.
Mine started doing it in April, which is well before the August 12 release of the update.
Not saying the update caused it but that the bugs might be similar. Symptoms definitely match up.
This is happening for me as well on latest version copying from NTFS filesystem to BTRFS.
~~Solution is to limit file transfers to under 4Gb which is what is the limit, ironically, for FAT32.~~
Looks like if I limit the file size to below 1Gb, I can copy over large groups of files just fine.
The issue seems to be that this software shits the bed for any files that are larger than 1Gb.
Can anyone confirm?
It happens to me as well. A workaround so far is to disable compression via registry.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\btrfs]
"Compress"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\btrfs\<GUID>]
"Compress"=dword:00000000
After changes in the registry, reboot.
This way, mounted without compression, I don't have the issue. Maybe it still happens with even heavier write operations, not sure.
From the README
The driver will create subkeys in the registry under HKLM\SYSTEM\CurrentControlSet\Services\btrfs for each mounted filesystem, named after its UUID. If you're unsure which UUID refers to which volume, you can check using
btrfs fi showon Linux. You can add per-volume mount options to this subkey, which will take effect on reboot. If a value is set in the key above this, it will use this by default.
So seeing as @billbalm had to change the value for the parent key I'm assuming it does. I'm no longer using WinBTRFS so I can't test it.