From: covici@ccs.covici.com
To: linux-btrfs@vger.kernel.org
Subject: btrfs problems on new file system
Date: Fri, 25 Dec 2015 05:03:10 -0500 [thread overview]
Message-ID: <16107.1451037790@ccs.covici.com> (raw)
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.
Thanks in advance for any suggestions.
--
Your life is like a penny. You're going to lose it. The question is:
How do
you spend it?
John Covici
covici@ccs.covici.com
next reply other threads:[~2015-12-25 10:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-25 10:03 covici [this message]
2015-12-25 19:01 ` btrfs problems on new file system Henk Slager
2015-12-25 21:14 ` covici
2015-12-26 3:53 ` Chris Murphy
2015-12-26 7:29 ` covici
2015-12-26 10:47 ` Duncan
2015-12-26 11:38 ` covici
2015-12-26 19:07 ` Chris Murphy
2015-12-26 19:22 ` covici
2015-12-26 19:50 ` Chris Murphy
2015-12-26 20:02 ` covici
2015-12-26 20:33 ` Chris Murphy
2015-12-26 5:20 ` Duncan
2015-12-26 7:44 ` covici
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=16107.1451037790@ccs.covici.com \
--to=covici@ccs.covici.com \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.