Some problems with auto repair of btrfs about btrfs HOT 7 CLOSED

If it's happening on both OSes, it sounds like your filesystem might be corrupt. Could you post the output of btrfs check please?

from btrfs.

I forgot to add that - after first crash - btrfs is corrupted and I used "btrfsck --repair" from System Rescue CD. All problems are fixed. Debian start again. But when I copy again such file, the system crashes again. This is the output for "btrfsck /dev/sda3 --repair":

enabling repair mode
Checking filesystem on /dev/sda3
UUID: ba962ffa-b744-4d06-93f6-7ffd4a43ef06
checking extents
Fixed 0 roots
checking free space cache
cache and super generation don't match, space cache will be invalidated
checking fs roots
checking csums
checking root refs
found 65385836544 bytes used err is 0
total csum bytes: 63564722
total tree bytes: 270139392
total fs tree bytes: 191217664
total extent tree bytes: 10502144
btree space waste bytes: 44674695
file data blocks allocated: 65124974592
referenced 65111736320

from btrfs.

That makes things more interesting... It doesn't rule out corruption entirely though, as I've found many instances where a filesystem was corrupt but btrfs check didn't pick it up.

Could you make Windows BSOD, please, and send me a crash dump?

from btrfs.

Do you want a complete memory dump or only kernel memory dump?

from btrfs.

Kernel should do, I think

from btrfs.

Sorry... the error doesn't occur anymore. So, btrfsck doesn't work very well. Deleting and writing other files and repeat fs check, it solves that error. There could be something wrong on auto repair of btrfs...

I have seen that Windows has created a minidump on the first crash. I put it here.
Minidump.zip

from btrfs.

I looked for the first HD damaged sectors. That HD with NTFS has corrupted the file system btrfs during the file copy (on healthy internal HD). There were some damaged sectors on HD with NTFS.

However, it remains an open problem related to self-repair of btrfs.

So, the title of this issue is misleading. Feel free to close the issue or give it a different title. Thank you.

from btrfs.