I don't think it's memory corruption as my modules test out fine, and
the problem began when i ran the btrfs check
--repair. Someone responded that they thought that the missing files
that are playable by the media player were still in memory, but they
still play after a reboot and they're not in
Bearcat Şándor gmail.com> writes:
> Is there a fix for the bad tree block error, which seems to be the
> root (pun intended) of all this?
I think the root cause is some memory corruption. It might be known case,
maybe someone else recognizes something.
Anyhow, if you can't and won't reproduce
Thank you for that info Ducan! I did the restore on the whole drive
and it errored out on me. I'll try the restore on some key files (audo
mostly) and see what i can get off of it.
Is there a fix for the bad tree block error, which seems to be the
root (pun intended) of all this?
On Sat, Jun 11,
Bearcat Şándor posted on Sat, 11 Jun 2016 13:54:44 -0600 as excerpted:
> I'm about to try a btrfs restore to see what it can do for me. Any
> pointers or help here? I don't want to fsck things up further.
FWIW, btrfs restore doesn't write anything at all to the filesystem it's
restoring from --
Hello folks,
I was getting
jaguarundi kernel: BTRFS (device sdb1): bad tree block start
18404062518368034137 2697991438336 and
csum failed .. no csum. found for inode ..
messages. Following instructions online, i've tried a scrub which
aborts before 200mb, a mount -o recovery rw, and a btrfs
