Re: fix for ERROR: cannot read chunk root

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

 



additional info: it's a simple partition on a samsung 840evo ssd, no
encryption, no md, no raid
 mount flags rw,relatime,ssd,space_cache,subvolid=5,subvol=/ mounted as /home
and it's pretty old(couple of years) and i'm like 70% sure it was
converted from ext4

On Wed, Nov 6, 2019 at 6:21 PM Sergiu Cozma <lssjbrolli@xxxxxxxxx> wrote:
>
> btrfs inspect-internal dump-super -af /dev/sdb4 | grep chunk_root
> chunk_root_generation   687369
> chunk_root              856119312384
> chunk_root_level        1
>                backup_chunk_root:      856119312384    gen: 687369     level: 1
>                backup_chunk_root:      856119312384    gen: 687369     level: 1
>                backup_chunk_root:      856119312384    gen: 687369     level: 1
>                backup_chunk_root:      856119312384    gen: 687369     level: 1
> chunk_root_generation   687369
> chunk_root              856119312384
> chunk_root_level        1
>                backup_chunk_root:      856119312384    gen: 687369     level: 1
>                backup_chunk_root:      856119312384    gen: 687369     level: 1
>                backup_chunk_root:      856119312384    gen: 687369     level: 1
>                backup_chunk_root:      856119312384    gen: 687369     level: 1
> chunk_root_generation   687369
> chunk_root              856119312384
> chunk_root_level        1
>                backup_chunk_root:      856119312384    gen: 687369     level: 1
>                backup_chunk_root:      856119312384    gen: 687369     level: 1
>                backup_chunk_root:      856119312384    gen: 687369     level: 1
>                backup_chunk_root:      856119312384    gen: 687369     level: 1
>
> if i understand this correctly there is only one copy of the chunk
> root in the whole fs and mine is corrupted?
>
> On Wed, Nov 6, 2019 at 5:52 PM Sergiu Cozma <lssjbrolli@xxxxxxxxx> wrote:
> >
> > Hi, thanks for taking the time to help me out with this.
> >
> > The history is kinda bad, I tried to resize the partition but gparted
> > failed saying that the the fs has errors and after throwing some
> > commands found on the internet at it now I'm here :(
> >
> > Any chance to recover or rebuild the chunk tree?
> >
> >
> > On Wed, Nov 6, 2019, 13:34 Qu Wenruo <quwenruo.btrfs@xxxxxxx> wrote:
> > >
> > >
> > >
> > > On 2019/11/5 下午11:04, Sergiu Cozma wrote:
> > > > hi, i need some help to recover a btrfs partition
> > > > i use btrfs-progs v5.3.1
> > > >
> > > > btrfs rescue super-recover https://pastebin.com/mGEp6vjV
> > > > btrfs inspect-internal dump-super -a https://pastebin.com/S4WrPQm1
> > > > btrfs inspect-internal dump-tree https://pastebin.com/yX1zUDxa
> > > >
> > > > can't mount the partition with
> > > > BTRFS error (device sdb4): bad tree block start, want 856119312384 have 0
> > >
> > > Something wiped your fs on-disk data.
> > > And the wiped one belongs to one of the most essential tree, chunk tree.
> > >
> > > What's the history of the fs?
> > > It doesn't look like a bug in btrfs, but some external thing wiped it.
> > >
> > > Thanks,
> > > Qu
> > >
> > > > [ 2295.237145] BTRFS error (device sdb4): failed to read chunk root
> > > > [ 2295.301067] BTRFS error (device sdb4): open_ctree failed
> > > >
> > >




[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