"Yan, Zheng " <[email protected]> writes: > You can try mounting the FS in read only mode and copying files out. > If you still get that error, try making verify_parent_transid() in disk-io.c > always return 0. These are all we can do now.
Tried mounting it in read only mode, same problem: [176994.933016] __ratelimit: 92171 callbacks suppressed [176994.933021] parent transid verify failed on 39669760 wanted 5946 found 5944 However, I will keep the filesystem in storage, so you can tell me when you wish to start working on the btrfsck side of things. I can run different test versions and help debug things until btrfsck is able to fix the filesystem. Personally, I consider the biggest barrier in adopting new filesystems for use to be the quality of their fsck. Checksums and metadata checksums do not help against programmatic corruption of data structures - and in my opinion, that will happen at some point, either via bugs in the code or memory corruption - and a filesystem needs to be able to survive that. -- Naked -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
