Re: failed to read log tree, open_ctree failed

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Aug 27, 2013 at 02:47:48AM +0800, Tomasz Chmielewski wrote:
> On Mon, 26 Aug 2013 19:34:19 +0100
> Hugo Mills <hugo@xxxxxxxxxxxxx> wrote:
> 
> > > corrupt 0, gen 0 [   56.209412] parent transid verify failed on
> > > 3321036099584 wanted 97967 found 97966 [   56.225990] parent
> > > transid verify failed on 3321036099584 wanted 97967 found 97966
> > > [   56.226128] btrfs: failed to read log tree [   56.344483] btrfs:
> > > open_ctree failed
> > > 
> > > 
> > > I've tried with 3.11-rc7, but it gives the same result.
> > > 
> > > Any hints how to recover from that?
> > > I have backups, but it would be nice if the filesystem just mounted.
> > 
> >    Try mounting with both -orecovery and -oro,recovery.
> 
> Neither worked, same error.
> 
> Anything else I can try?

   Oh, hang on... that's the log tree.

   btrfs-zero-log may help. If you can take a btrfs-image of the
filesystem before running that, josef would like to see it.

   Hugo.

-- 
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
  PGP key: 65E74AC0 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
              --- Python is executable pseudocode; perl ---              
                        is executable line-noise.                        

Attachment: signature.asc
Description: Digital signature


[Index of Archives]     [Linux Filesystem Development]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux