On Fri, Dec 25, 2015 at 11:03 AM, <covici@xxxxxxxxxxxxxx> wrote: > Hi. I created a file system using 4.3.1 version of btrfsprogs and have > been using it for some three days. I have gotten the following errors > in the log this morning: > Dec 25 04:10:16 ccs.covici.com kernel: BTRFS (device dm-20): parent > transid verify failed on 51776421888 wanted 4983 found 4981 > Dec 25 04:10:16 ccs.covici.com kernel: BTRFS (device dm-20): parent > transid verify failed on 51776421888 wanted 4983 found 4981 > Dec 25 04:10:16 ccs.covici.com kernel: BTRFS (device dm-20): parent > transid verify failed on 51776421888 wanted 4983 found 4981 > Dec 25 04:10:16 ccs.covici.com kernel: BTRFS (device dm-20): parent > transid verify failed on 51776421888 wanted 4983 found 4981 > Dec 25 04:10:16 ccs.covici.com kernel: BTRFS (device dm-20): parent > transid verify failed on 51776421888 wanted 4983 found 4981 > Dec 25 04:10:16 ccs.covici.com kernel: BTRFS (device dm-20): parent > transid verify failed on 51776421888 wanted 4983 found 4981 > Dec 25 04:10:16 ccs.covici.com kernel: BTRFS (device dm-20): parent > transid verify failed on 51776421888 wanted 4983 found 4981 > Dec 25 04:10:16 ccs.covici.com kernel: BTRFS (device dm-20): parent > transid verify failed on 51776421888 wanted 4983 found 4981 > Dec 25 04:10:16 ccs.covici.com kernel: BTRFS (device dm-20): parent > transid verify failed on 51776421888 wanted 4983 found 4981 > Dec 25 04:10:16 ccs.covici.com kernel: BTRFS (device dm-20): parent > transid verify failed on 51776421888 wanted 4983 found 4981 > > The file system was then made read only. I unmounted, did a check > without repair which said it was fine, and remounted successfully in > read/write mode, but am I in trouble? This was on a solid state drive > using lvm. What kernel version are you using? I think you might have some hardware error or glitch somewhere, otherwise I don't know why you have such errors. These kind of errors remind me of SATA/cable failures over quite a period of time (multipe days). Or something with lvm or trim of SSD. Any unusual with the SSD if you run smartctl? A btrfs check will indeed likely result in an OK for this case. What about running read-only scrub? Maybe running memtest86+ can rule-out the worst case. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
