Jordan Windsor
2012-Dec-28 18:09 UTC
parent transid verify failed on -- After moving btrfs closer to the beginning of drive with dd
Hello, I moved my btrfs to the beginning of my drive & updated the partition table & also restarted, I''m currently unable to mount it, here''s the output in dmesg. [ 481.513432] device label Storage devid 1 transid 116023 /dev/sdb1 [ 481.514277] btrfs: disk space caching is enabled [ 481.522611] parent transid verify failed on 1229060423680 wanted 116023 found 116027 [ 481.522789] parent transid verify failed on 1229060423680 wanted 116023 found 116027 [ 481.522790] btrfs: failed to read tree root on sdb1 [ 481.523656] btrfs: open_ctree failed What command should I run from here? Thanks. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
cwillu
2012-Dec-28 18:59 UTC
Re: parent transid verify failed on -- After moving btrfs closer to the beginning of drive with dd
On Fri, Dec 28, 2012 at 12:09 PM, Jordan Windsor <jordanw2@gmail.com> wrote:> Hello, > I moved my btrfs to the beginning of my drive & updated the partition > table & also restarted, I''m currently unable to mount it, here''s the > output in dmesg. > > [ 481.513432] device label Storage devid 1 transid 116023 /dev/sdb1 > [ 481.514277] btrfs: disk space caching is enabled > [ 481.522611] parent transid verify failed on 1229060423680 wanted > 116023 found 116027 > [ 481.522789] parent transid verify failed on 1229060423680 wanted > 116023 found 116027 > [ 481.522790] btrfs: failed to read tree root on sdb1 > [ 481.523656] btrfs: open_ctree failed > > What command should I run from here?The filesystem wasn''t uncleanly unmounted, likely on an older kernel. Try mounting with -o recovery -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Jordan Windsor
2012-Dec-28 19:34 UTC
Re: parent transid verify failed on -- After moving btrfs closer to the beginning of drive with dd
Hello, thanks for the response! Here''s the output of "-o recovery" [ 5473.725751] device label Storage devid 1 transid 116023 /dev/sdb1 [ 5473.726612] btrfs: enabling auto recovery [ 5473.726615] btrfs: disk space caching is enabled [ 5473.734581] parent transid verify failed on 1229060423680 wanted 116023 found 116027 [ 5473.734797] parent transid verify failed on 1229060423680 wanted 116023 found 116027 [ 5473.734801] btrfs: failed to read tree root on sdb1 [ 5473.735010] parent transid verify failed on 1229060423680 wanted 116023 found 116027 [ 5473.735259] parent transid verify failed on 1229060423680 wanted 116023 found 116027 [ 5473.735262] btrfs: failed to read tree root on sdb1 [ 5473.756367] parent transid verify failed on 1229060243456 wanted 116022 found 116028 [ 5473.761968] parent transid verify failed on 1229060243456 wanted 116022 found 116028 [ 5473.761975] btrfs: failed to read tree root on sdb1 [ 5475.561208] btrfs bad tree block start 7479324919942847850 1241518882816 [ 5475.567008] btrfs bad tree block start 13410158725948676859 1241518882816 [ 5475.567056] Failed to read block groups: -5 [ 5475.570200] btrfs: open_ctree failed I''m on kernel 3.6.10 and have been before this problem. Thanks. On Sat, Dec 29, 2012 at 5:29 AM, cwillu <cwillu@cwillu.com> wrote:> On Fri, Dec 28, 2012 at 12:09 PM, Jordan Windsor <jordanw2@gmail.com> wrote: >> Hello, >> I moved my btrfs to the beginning of my drive & updated the partition >> table & also restarted, I''m currently unable to mount it, here''s the >> output in dmesg. >> >> [ 481.513432] device label Storage devid 1 transid 116023 /dev/sdb1 >> [ 481.514277] btrfs: disk space caching is enabled >> [ 481.522611] parent transid verify failed on 1229060423680 wanted >> 116023 found 116027 >> [ 481.522789] parent transid verify failed on 1229060423680 wanted >> 116023 found 116027 >> [ 481.522790] btrfs: failed to read tree root on sdb1 >> [ 481.523656] btrfs: open_ctree failed >> >> What command should I run from here? > > The filesystem wasn''t uncleanly unmounted, likely on an older kernel. > > Try mounting with -o recovery-- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Jordan Windsor
2012-Dec-29 13:14 UTC
Re: parent transid verify failed on -- After moving btrfs closer to the beginning of drive with dd
Also here''s the output of btrfs-find-root: ./btrfs-find-root /dev/sdb1 Super think''s the tree root is at 1229060866048, chunk root 1259695439872 Went past the fs size, exiting Not sure where to go from here. On Sat, Dec 29, 2012 at 6:04 AM, Jordan Windsor <jordanw2@gmail.com> wrote:> Hello, > thanks for the response! > Here''s the output of "-o recovery" > > [ 5473.725751] device label Storage devid 1 transid 116023 /dev/sdb1 > [ 5473.726612] btrfs: enabling auto recovery > [ 5473.726615] btrfs: disk space caching is enabled > [ 5473.734581] parent transid verify failed on 1229060423680 wanted > 116023 found 116027 > [ 5473.734797] parent transid verify failed on 1229060423680 wanted > 116023 found 116027 > [ 5473.734801] btrfs: failed to read tree root on sdb1 > [ 5473.735010] parent transid verify failed on 1229060423680 wanted > 116023 found 116027 > [ 5473.735259] parent transid verify failed on 1229060423680 wanted > 116023 found 116027 > [ 5473.735262] btrfs: failed to read tree root on sdb1 > [ 5473.756367] parent transid verify failed on 1229060243456 wanted > 116022 found 116028 > [ 5473.761968] parent transid verify failed on 1229060243456 wanted > 116022 found 116028 > [ 5473.761975] btrfs: failed to read tree root on sdb1 > [ 5475.561208] btrfs bad tree block start 7479324919942847850 1241518882816 > [ 5475.567008] btrfs bad tree block start 13410158725948676859 1241518882816 > [ 5475.567056] Failed to read block groups: -5 > [ 5475.570200] btrfs: open_ctree failed > > I''m on kernel 3.6.10 and have been before this problem. > > Thanks. > > On Sat, Dec 29, 2012 at 5:29 AM, cwillu <cwillu@cwillu.com> wrote: >> On Fri, Dec 28, 2012 at 12:09 PM, Jordan Windsor <jordanw2@gmail.com> wrote: >>> Hello, >>> I moved my btrfs to the beginning of my drive & updated the partition >>> table & also restarted, I''m currently unable to mount it, here''s the >>> output in dmesg. >>> >>> [ 481.513432] device label Storage devid 1 transid 116023 /dev/sdb1 >>> [ 481.514277] btrfs: disk space caching is enabled >>> [ 481.522611] parent transid verify failed on 1229060423680 wanted >>> 116023 found 116027 >>> [ 481.522789] parent transid verify failed on 1229060423680 wanted >>> 116023 found 116027 >>> [ 481.522790] btrfs: failed to read tree root on sdb1 >>> [ 481.523656] btrfs: open_ctree failed >>> >>> What command should I run from here? >> >> The filesystem wasn''t uncleanly unmounted, likely on an older kernel. >> >> Try mounting with -o recovery-- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
cwillu
2012-Dec-29 15:38 UTC
Re: parent transid verify failed on -- After moving btrfs closer to the beginning of drive with dd
On Sat, Dec 29, 2012 at 7:14 AM, Jordan Windsor <jordanw2@gmail.com> wrote:> Also here''s the output of btrfs-find-root: > > ./btrfs-find-root /dev/sdb1 > Super think''s the tree root is at 1229060866048, chunk root 1259695439872 > Went past the fs size, exiting > > Not sure where to go from here.I can''t say for certain, but that suggests that the move-via-dd didn''t succeed / wasn''t correct, and/or the partitioning changes didn''t match, and/or the dd happened from a mounted filesystem (which would also explain the transid errors, if there wasn''t an unclean umount involved). btrfs-restore might be able to pick out files, but you may be in restore-from-backup territory. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Chris Murphy
2012-Dec-29 15:52 UTC
Re: parent transid verify failed on -- After moving btrfs closer to the beginning of drive with dd
On Dec 29, 2012, at 8:38 AM, cwillu <cwillu@cwillu.com> wrote:> On Sat, Dec 29, 2012 at 7:14 AM, Jordan Windsor <jordanw2@gmail.com> wrote: >> Also here''s the output of btrfs-find-root: >> >> ./btrfs-find-root /dev/sdb1 >> Super think''s the tree root is at 1229060866048, chunk root 1259695439872 >> Went past the fs size, exiting >> >> Not sure where to go from here. > > I can''t say for certain, but that suggests that the move-via-dd didn''t > succeed / wasn''t correct, and/or the partitioning changes didn''t > match, and/or the dd happened from a mounted filesystem (which would > also explain the transid errors, if there wasn''t an unclean umount > involved). > > btrfs-restore might be able to pick out files, but you may be in > restore-from-backup territory.Yeah I''m vaguely curious about how the move was done, in particular if it was dd''d from a mounted fs. Chris Murphy-- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html