"open_ctree failed", unable to mount the fs

I got a "power cycle", after which I'm no longer able to mount btrfs filesystem:

device fsid xxxxx-yyyyy devid 1 transid 169686 /dev/vda3 device fsid xxxxx-yyyyy devid 1 transid 169686 /dev/vda3 parent transid verify failed on 3260289024 wanted 169686 found 169685 parent transid verify failed on 3260289024 wanted 169686 found 169685 parent transid verify failed on 3260289024 wanted 169686 found 169685
btrfs: open_ctree failed

Tried to get that mounted with 2.6.35 and 2.6.37, without success.

Is there a way to fix it?

Tomasz Chmielewski
http://wpkg.org

The forthcoming[1] btrfsck tool should handle that particular
error, I believe.

To prevent it from happening again, ensure that you have working
barriers on your disks, or that you turn off write caching on the drives at every boot.

Hugo.

[1] out "real soon now"

=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
  PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
        --- Well, sir, the floor is yours.  But remember, the ---        
                              roof is ours!                              

[...]

I tried it with the btrfsck in the git repo (last week), and wound up with... a brandy-new, blank btrfs partition. Not *quite* what I was looking for. But at least it mounted.

-K

s

s

btrfsck in git hasn't been updated since October; the upcoming fsck work isn't public, presumably to avoid making things worse until it's working right. The current btrfsck doesn't write to the partition as far as I'm aware.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" = in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html