linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Levy <contact@ericlevy.name>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: parent transid verify failed
Date: Sat, 01 Jan 2022 16:58:58 -0500	[thread overview]
Message-ID: <59a9506eb880b054f8eff90d5b26ad0c673c7e1f.camel@ericlevy.name> (raw)
In-Reply-To: <YdDAGLU7M5mx7rL8@hungrycats.org>

Here is the new information:


1) Previously, the system log from R/W mount attempt, which failed:

Dec 31 15:15:48 hostname sudo[1477409]:      user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/mount -o skip_balance /dev/sdc1
Dec 31 15:15:48 hostname sudo[1477409]: pam_unix(sudo:session): session opened for user root by (uid=0)
Dec 31 15:15:48 hostname sudo[1477409]: pam_unix(sudo:session): session closed for user root
Dec 31 15:15:48 hostname kernel: BTRFS info (device sdc1): disk space caching is enabled
Dec 31 15:15:48 hostname kernel: BTRFS error (device sdc1): Remounting read-write after error is not allowed


2) Same, but in RO:

Dec 31 15:14:50 hostname sudo[1477248]:      user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/mount -o skip_balance,ro /dev/sdc1
Dec 31 15:14:50 hostname sudo[1477248]: pam_unix(sudo:session): session opened for user root by (uid=0)
Dec 31 15:14:50 hostname sudo[1477248]: pam_unix(sudo:session): session closed for user root
Dec 31 15:14:50 hostname kernel: BTRFS error (device sdc1): parent transid verify failed on 867434496 wanted 9212 found 8675
Dec 31 15:14:50 hostname kernel: BTRFS error (device sdc1): parent transid verify failed on 867434496 wanted 9212 found 8675
Dec 31 15:14:50 hostname kernel: BTRFS error (device sdc1): parent transid verify failed on 867434496 wanted 9212 found 8675
Dec 31 15:14:50 hostname kernel: BTRFS error (device sdc1): parent transid verify failed on 867434496 wanted 9212 found 8675
Dec 31 15:14:50 hostname kernel: BTRFS error (Device sdc1): parent transid verify failed on 867434496 wanted 9212 found 8675
Dec 31 15:14:50 hostname kernel: BTRFS error (device sdc1): parent transid verify failed on 867434496 wanted 9212 found 8675
Dec 31 15:14:50 hostname kernel: BTRFS error (device sdc1): parent transid verify failed on 867434496 wanted 9212 found 8675
Dec 31 15:14:50 hostname kernel: BTRFS error (device sdc1): parent transid verify failed on 867434496 wanted 9212 found 8675
Dec 31 15:14:50 hostname kernel: BTRFS error (device sdc1): parent transid verify failed on 867434496 wanted 9212 found 8675
Dec 31 15:14:50 hostname kernel: BTRFS error (device sdc1): parent transid verify failed on 867434496 wanted 9212 found 8675


3) After running iSCSI logout, and login, the devices were assigned new
names (sdc -> sdf, sdd -> sde). Then checking with readonly flag, using
admin tools, while unmounted:

$ sudo btrfs check --readonly /dev/sdf1
Opening filesystem to check...
Checking filesystem on /dev/sdf1
UUID: c6f83d24-1ac3-4417-bdd9-6249c899604d
[1/7] checking root items
[2/7] checking extents
[3/7] checking free space cache
[4/7] checking fs roots
[5/7] checking only csums items (without verifying data)
[6/7] checking root refs
[7/7] checking quota groups skipped (not enabled on this FS)
found 266107584512 bytes used, no error found
total csum bytes: 259546380
total tree bytes: 586268672
total fs tree bytes: 214188032
total extent tree bytes: 52609024
btree space waste bytes: 89657360
file data blocks allocated: 1019677446144
 referenced 300654301184


4) However, mount still fails. Here is log output from trying to mount
/dev/sdf1:

kernel: BTRFS warning: duplicate device /dev/sdf1 devid 1 generation 9211 scanned by mount (1641108)


5) Same kind of results for /dev/sde:

kernel: BTRFS warning: duplicate device /dev/sde devid 2 generation 9211 scanned by mount (1642247)


  reply	other threads:[~2022-01-01 21:59 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-30 21:10 parent transid verify failed Eric Levy
2021-12-30 21:47 ` Chris Murphy
2022-01-01 15:11   ` devel
2021-12-31 19:14 ` Zygo Blaxell
2021-12-31 20:33   ` Eric Levy
2021-12-31 23:09     ` Chris Murphy
2022-01-01  7:33       ` Eric Levy
2022-01-01 20:49         ` Chris Murphy
2022-01-01 21:57           ` Eric Levy
2022-01-01 20:56     ` Zygo Blaxell
2022-01-01 21:58       ` Eric Levy [this message]
2022-01-02  0:15         ` Zygo Blaxell
2022-01-02  0:55           ` Eric Levy
2022-01-02  3:27             ` Zygo Blaxell
2022-01-02  4:03               ` Eric Levy
2022-01-02  5:57                 ` Zygo Blaxell
2022-01-02 10:17                   ` Eric Levy
2022-01-03  7:41                 ` Chris Murphy
2022-01-02  7:31     ` Andrei Borzenkov
  -- strict thread matches above, loose matches on Subject: below --
2017-05-11 10:01 Massimo B.
     [not found] <E18363B1-CD81-41F4-A03C-4D09AA669915@plack.net>
2015-04-28 12:34 ` Anthony Plack
2010-09-06 17:28 Jan Steffens

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=59a9506eb880b054f8eff90d5b26ad0c673c7e1f.camel@ericlevy.name \
    --to=contact@ericlevy.name \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).