Linux-BTRFS Archive on lore.kernel.org
 help / color / Atom feed
* fix for ERROR: cannot read chunk root
@ 2019-11-05 15:04 Sergiu Cozma
  2019-11-06 10:48 ` Sergiu Cozma
  2019-11-06 11:34 ` Qu Wenruo
  0 siblings, 2 replies; 10+ messages in thread
From: Sergiu Cozma @ 2019-11-05 15:04 UTC (permalink / raw)
  To: linux-btrfs

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
[ 2295.237145] BTRFS error (device sdb4): failed to read chunk root
[ 2295.301067] BTRFS error (device sdb4): open_ctree failed

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: fix for ERROR: cannot read chunk root
  2019-11-05 15:04 fix for ERROR: cannot read chunk root Sergiu Cozma
@ 2019-11-06 10:48 ` Sergiu Cozma
  2019-11-06 11:34 ` Qu Wenruo
  1 sibling, 0 replies; 10+ messages in thread
From: Sergiu Cozma @ 2019-11-06 10:48 UTC (permalink / raw)
  To: linux-btrfs

also btrfs check --readonly /dev/sdb4
Opening filesystem to check...
checksum verify failed on 856119312384 found 000000B6 wanted 00000000
checksum verify failed on 856119312384 found 000000B6 wanted 00000000
bad tree block 856119312384, bytenr mismatch, want=856119312384, have=0
ERROR: cannot read chunk root
ERROR: cannot open file system

On Tue, Nov 5, 2019 at 5:04 PM Sergiu Cozma <lssjbrolli@gmail.com> 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
> [ 2295.237145] BTRFS error (device sdb4): failed to read chunk root
> [ 2295.301067] BTRFS error (device sdb4): open_ctree failed

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: fix for ERROR: cannot read chunk root
  2019-11-05 15:04 fix for ERROR: cannot read chunk root Sergiu Cozma
  2019-11-06 10:48 ` Sergiu Cozma
@ 2019-11-06 11:34 ` Qu Wenruo
  2019-11-06 15:52   ` Sergiu Cozma
  1 sibling, 1 reply; 10+ messages in thread
From: Qu Wenruo @ 2019-11-06 11:34 UTC (permalink / raw)
  To: Sergiu Cozma, linux-btrfs

[-- Attachment #1.1: Type: text/plain, Size: 824 bytes --]



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
> 


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: fix for ERROR: cannot read chunk root
  2019-11-06 11:34 ` Qu Wenruo
@ 2019-11-06 15:52   ` Sergiu Cozma
  2019-11-06 16:21     ` Sergiu Cozma
  2019-11-07  0:44     ` Qu Wenruo
  0 siblings, 2 replies; 10+ messages in thread
From: Sergiu Cozma @ 2019-11-06 15:52 UTC (permalink / raw)
  To: Qu Wenruo; +Cc: linux-btrfs

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@gmx.com> 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
> >
>

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: fix for ERROR: cannot read chunk root
  2019-11-06 15:52   ` Sergiu Cozma
@ 2019-11-06 16:21     ` Sergiu Cozma
  2019-11-06 22:19       ` Sergiu Cozma
  2019-11-07  0:44     ` Qu Wenruo
  1 sibling, 1 reply; 10+ messages in thread
From: Sergiu Cozma @ 2019-11-06 16:21 UTC (permalink / raw)
  To: Qu Wenruo; +Cc: linux-btrfs

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@gmail.com> 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@gmx.com> 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
> > >
> >

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: fix for ERROR: cannot read chunk root
  2019-11-06 16:21     ` Sergiu Cozma
@ 2019-11-06 22:19       ` Sergiu Cozma
  0 siblings, 0 replies; 10+ messages in thread
From: Sergiu Cozma @ 2019-11-06 22:19 UTC (permalink / raw)
  To: Qu Wenruo; +Cc: linux-btrfs

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@gmail.com> 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@gmail.com> 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@gmx.com> 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
> > > >
> > >

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: fix for ERROR: cannot read chunk root
  2019-11-06 15:52   ` Sergiu Cozma
  2019-11-06 16:21     ` Sergiu Cozma
@ 2019-11-07  0:44     ` Qu Wenruo
  2019-11-07  7:16       ` Sergiu Cozma
  1 sibling, 1 reply; 10+ messages in thread
From: Qu Wenruo @ 2019-11-07  0:44 UTC (permalink / raw)
  To: Sergiu Cozma; +Cc: linux-btrfs

[-- Attachment #1.1: Type: text/plain, Size: 1544 bytes --]



On 2019/11/6 下午11:52, Sergiu Cozma 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 :(

Not sure how gparted handle resize, but I guess it should use
btrfs-progs to do the resize?

> 
> Any chance to recover or rebuild the chunk tree?

I don't think so. Since it's wiped, there is no guarantee that only
chunk tree is wiped.

THanks,
Qu


> 
> 
> On Wed, Nov 6, 2019, 13:34 Qu Wenruo <quwenruo.btrfs@gmx.com> 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
>>>
>>


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: fix for ERROR: cannot read chunk root
  2019-11-07  0:44     ` Qu Wenruo
@ 2019-11-07  7:16       ` Sergiu Cozma
  2019-11-10 15:40         ` Sergiu Cozma
  0 siblings, 1 reply; 10+ messages in thread
From: Sergiu Cozma @ 2019-11-07  7:16 UTC (permalink / raw)
  To: Qu Wenruo; +Cc: linux-btrfs

Well nothing to lose now so if you come up with any exotic ideas you
wanna try please let me know, I will keep the partition for the next
couple of days.

Thank you for your time.

On Thu, Nov 7, 2019 at 2:44 AM Qu Wenruo <quwenruo.btrfs@gmx.com> wrote:
>
>
>
> On 2019/11/6 下午11:52, Sergiu Cozma 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 :(
>
> Not sure how gparted handle resize, but I guess it should use
> btrfs-progs to do the resize?
>
> >
> > Any chance to recover or rebuild the chunk tree?
>
> I don't think so. Since it's wiped, there is no guarantee that only
> chunk tree is wiped.
>
> THanks,
> Qu
>
>
> >
> >
> > On Wed, Nov 6, 2019, 13:34 Qu Wenruo <quwenruo.btrfs@gmx.com> 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
> >>>
> >>
>

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: fix for ERROR: cannot read chunk root
  2019-11-07  7:16       ` Sergiu Cozma
@ 2019-11-10 15:40         ` Sergiu Cozma
  2019-11-11  1:46           ` Qu Wenruo
  0 siblings, 1 reply; 10+ messages in thread
From: Sergiu Cozma @ 2019-11-10 15:40 UTC (permalink / raw)
  To: Qu Wenruo; +Cc: linux-btrfs

root   856153161728
chunk_root     856119312384

Aren't those nr too high for a 416GB partition?

On Thu, Nov 7, 2019 at 9:16 AM Sergiu Cozma <lssjbrolli@gmail.com> wrote:
>
> Well nothing to lose now so if you come up with any exotic ideas you
> wanna try please let me know, I will keep the partition for the next
> couple of days.
>
> Thank you for your time.
>
> On Thu, Nov 7, 2019 at 2:44 AM Qu Wenruo <quwenruo.btrfs@gmx.com> wrote:
> >
> >
> >
> > On 2019/11/6 下午11:52, Sergiu Cozma 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 :(
> >
> > Not sure how gparted handle resize, but I guess it should use
> > btrfs-progs to do the resize?
> >
> > >
> > > Any chance to recover or rebuild the chunk tree?
> >
> > I don't think so. Since it's wiped, there is no guarantee that only
> > chunk tree is wiped.
> >
> > THanks,
> > Qu
> >
> >
> > >
> > >
> > > On Wed, Nov 6, 2019, 13:34 Qu Wenruo <quwenruo.btrfs@gmx.com> 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
> > >>>
> > >>
> >

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: fix for ERROR: cannot read chunk root
  2019-11-10 15:40         ` Sergiu Cozma
@ 2019-11-11  1:46           ` Qu Wenruo
  0 siblings, 0 replies; 10+ messages in thread
From: Qu Wenruo @ 2019-11-11  1:46 UTC (permalink / raw)
  To: Sergiu Cozma; +Cc: linux-btrfs

[-- Attachment #1.1: Type: text/plain, Size: 2769 bytes --]



On 2019/11/10 下午11:40, Sergiu Cozma wrote:
> root   856153161728
> chunk_root     856119312384
> 
> Aren't those nr too high for a 416GB partition?

It's btrfs logical address, they can be any aligned numbers in the range
of (0, U64-1).

So no problem at all.

Just check this:
# mkfs.btrfs -f -b 1G $dev
# mount $dev $mnt
# for i in $(seq 5); do
    btrfs balance --full $mnt
$ btrfs ins dump-super /dev/nvme/btrfs | grep chunk_root
chunk_root_generation   132
chunk_root              2018525184  << Way beyond 1G.
chunk_root_level        0


According to "have 0" errors, they are wiped somehow, and it's not
caused by btrfs kernel module.

Thanks,
Qu

> 
> On Thu, Nov 7, 2019 at 9:16 AM Sergiu Cozma <lssjbrolli@gmail.com> wrote:
>>
>> Well nothing to lose now so if you come up with any exotic ideas you
>> wanna try please let me know, I will keep the partition for the next
>> couple of days.
>>
>> Thank you for your time.
>>
>> On Thu, Nov 7, 2019 at 2:44 AM Qu Wenruo <quwenruo.btrfs@gmx.com> wrote:
>>>
>>>
>>>
>>> On 2019/11/6 下午11:52, Sergiu Cozma 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 :(
>>>
>>> Not sure how gparted handle resize, but I guess it should use
>>> btrfs-progs to do the resize?
>>>
>>>>
>>>> Any chance to recover or rebuild the chunk tree?
>>>
>>> I don't think so. Since it's wiped, there is no guarantee that only
>>> chunk tree is wiped.
>>>
>>> THanks,
>>> Qu
>>>
>>>
>>>>
>>>>
>>>> On Wed, Nov 6, 2019, 13:34 Qu Wenruo <quwenruo.btrfs@gmx.com> 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
>>>>>>
>>>>>
>>>


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 10+ messages in thread

end of thread, back to index

Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-11-05 15:04 fix for ERROR: cannot read chunk root Sergiu Cozma
2019-11-06 10:48 ` Sergiu Cozma
2019-11-06 11:34 ` Qu Wenruo
2019-11-06 15:52   ` Sergiu Cozma
2019-11-06 16:21     ` Sergiu Cozma
2019-11-06 22:19       ` Sergiu Cozma
2019-11-07  0:44     ` Qu Wenruo
2019-11-07  7:16       ` Sergiu Cozma
2019-11-10 15:40         ` Sergiu Cozma
2019-11-11  1:46           ` Qu Wenruo

Linux-BTRFS Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-btrfs/0 linux-btrfs/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-btrfs linux-btrfs/ https://lore.kernel.org/linux-btrfs \
		linux-btrfs@vger.kernel.org
	public-inbox-index linux-btrfs

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-btrfs


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git