Hi there,
I had remote filesystem not unmounting during shutdown so I hit the reboot
button. Did so a couple of times in the past. 3.6.8-1-ARCH, btrfs-progs
0.19.20121005-4, don''t remember the exact version I used when creating
the
filesystem (0.19 something).
btrfsck looks like this:
checking extents
checking fs roots
parent transid verify failed on 167047168 wanted 713090 found 713088
parent transid verify failed on 167047168 wanted 713090 found 713088
parent transid verify failed on 167047168 wanted 713090 found 713088
parent transid verify failed on 167047168 wanted 713090 found 713088
Ignoring transid failure
parent transid verify failed on 167047168 wanted 713090 found 713088
Ignoring transid failure
(repeating ~1800 times, always with the same IDs)
root 5 inode 8156558 errors 400
root 5 inode 9930070 errors 800
root 5 inode 9930168 errors 800
Tried -o recovery, mounts instantly and apparently doesn''t change
anything;
tried btrfs --repair, doesn''t appear to change anything as well.
Did mkfs.btrfs in order to restore from backup but mounting failed (broken
superblock something). How can a freshly mkfs''ed fs not mount?! I
restored a dd
dump I took beforehand, mounts, boots but is broken.
Any suggestions?
thx
tcn
BTW what do multiple root nodes mean actually? That I do have 3 different
trees with individual nodes pointing to different versions of data?
--
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
