* can't read superblock (but could mount)
@ 2012-02-10 19:30 btrfs
2012-02-10 22:18 ` Chris Mason
0 siblings, 1 reply; 14+ messages in thread
From: btrfs @ 2012-02-10 19:30 UTC (permalink / raw)
To: linux-btrfs
Hi!
I used to have arch linux running on 1 btrfs partition (sda1, incl. /boot).
When switching to 3.2.5 recently the system fails to boot:
(after udevd)
/etc/rc.sysinit: line 15: 117 Bus error mountpoint -q /proc
and so on, no idea.
It used to boot with 3.2.4, but
1) I obviously had some corruption in the tree, when I tried to delete a
certain file I hit e.g. "kernel BUG at fs/btrfs/extent-tree.c" message.
2) Even while running 3.2.4 I was unable to mount the partition from a
parallel gentoo or live USB install and I still am:
# mount /dev/sda1 /mnt/arch/
mount: /dev/sda1: can't read superblock
The strange thing is: when trying to boot from the partition the boot
loader (syslinux) is
obviously still able load the kernel from that partition.
Tried btrfs-zero-log and some deperate other things. Result: I can now
actually
execute btrfsck which previously used to fail:
# btrfsck /dev/sda1
Extent back ref already exists for 9872289792 parent 0 root 5
leaf parent key incorrect 9872289792
bad block 9872289792
ref mismatch on [9872289792 4096] extent item 1, found 2
Incorrect global backref count on 9872289792 found 1 wanted 2
backpointer mismatch on [9872289792 4096]
owner ref check failed [9872289792 4096]
ref mismatch on [9889067008 4096] extent item 1, found 0
Backref 9889067008 root 5 not referenced
Incorrect global backref count on 9889067008 found 1 wanted 0
backpointer mismatch on [9889067008 4096]
owner ref check failed [9889067008 4096]
ref mismatch on [37163102208 65536] extent item 1, found 0
Incorrect local backref count on 37163102208 root 5 owner 3360937
offset 0 found 0 wanted 1
backpointer mismatch on [37163102208 65536]
owner ref check failed [37163102208 65536]
ref mismatch on [37163814912 36864] extent item 0, found 1
Backref 37163814912 root 5 owner 3360939 offset 0 num_refs 0 not found
in extent tree
Incorrect local backref count on 37163814912 root 5 owner 3360939
offset 0 found 1 wanted 0
backpointer mismatch on [37163814912 36864]
found 15491117056 bytes used err is 1
total csum bytes: 14764500
total tree bytes: 366956544
total fs tree bytes: 317714432
btree space waste bytes: 90628933
file data blocks allocated: 16182484992
referenced 17813028864
Btrfs Btrfs v0.19-dirty
However this doesn't seem to fix anything. Can run it over and over
again with same output.
btrfs-show does recognize the partition...
# btrfs-show /dev/sda1
**
** WARNING: this program is considered deprecated
** Please consider to switch to the btrfs utility
**
failed to read /dev/sde: No medium found
Label: none uuid: 9e9886fc-3e60-4c59-a246-727662769ee2
Total devices 1 FS bytes used 14.43GB
devid 1 size 37.27GB used 34.52GB path /dev/sda1
Btrfs Btrfs v0.19-dirty
...while device scan does not:
# btrfs device scan /dev/sda1
Scanning for Btrfs filesystems in '/dev/sda1'
Finally dmesg after a mount attempt:
[88124.390308] Btrfs detected SSD devices, enabling SSD mode
[88124.392354] parent transid verify failed on 9872289792 wanted
152893 found 120351
[88124.392357] parent transid verify failed on 9872289792 wanted
152893 found 120351
[88124.392359] parent transid verify failed on 9872289792 wanted
152893 found 120351
[88124.392360] parent transid verify failed on 9872289792 wanted
152893 found 120351
[88124.392361] parent transid verify failed on 9872289792 wanted
152893 found 120351
[88124.392370] BTRFS: inode 3392566 still on the orphan list
[88124.392372] btrfs: could not do orphan cleanup -5
[88124.688187] btrfs: open_ctree failed
Any chance to rescue the data?
thx
tcn
^ permalink raw reply [flat|nested] 14+ messages in thread* Re: can't read superblock (but could mount)
2012-02-10 19:30 can't read superblock (but could mount) btrfs
@ 2012-02-10 22:18 ` Chris Mason
2012-02-10 23:39 ` Chris Mason
0 siblings, 1 reply; 14+ messages in thread
From: Chris Mason @ 2012-02-10 22:18 UTC (permalink / raw)
To: btrfs; +Cc: linux-btrfs
On Fri, Feb 10, 2012 at 08:30:51PM +0100, btrfs@nentwig.biz wrote:
> Hi!
>
> I used to have arch linux running on 1 btrfs partition (sda1, incl. /boot).
> When switching to 3.2.5 recently the system fails to boot:
>
> (after udevd)
> /etc/rc.sysinit: line 15: 117 Bus error mountpoint -q /proc
> and so on, no idea.
>
> It used to boot with 3.2.4, but
>
> 1) I obviously had some corruption in the tree, when I tried to delete a
> certain file I hit e.g. "kernel BUG at fs/btrfs/extent-tree.c" message.
>
> 2) Even while running 3.2.4 I was unable to mount the partition from a
> parallel gentoo or live USB install and I still am:
>
> # mount /dev/sda1 /mnt/arch/
> mount: /dev/sda1: can't read superblock
>
> The strange thing is: when trying to boot from the partition the
> boot loader (syslinux) is
> obviously still able load the kernel from that partition.
>
> Tried btrfs-zero-log and some deperate other things. Result: I can
> now actually
> execute btrfsck which previously used to fail:
Ok, step one:
Pull down the dangerdonteveruse branch of btrfs-progs:
git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-progs.git dangerdonteveruse
Run btrfs-debug-tree -r /dev/sda1 and send the output here please.
This block with bad transid is from your FS root. We'll need to a root
that matches. But we should be able to patch things up!
-chris
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: can't read superblock (but could mount)
2012-02-10 22:18 ` Chris Mason
@ 2012-02-10 23:39 ` Chris Mason
2012-02-11 6:27 ` btrfs
0 siblings, 1 reply; 14+ messages in thread
From: Chris Mason @ 2012-02-10 23:39 UTC (permalink / raw)
To: btrfs; +Cc: linux-btrfs
On Fri, Feb 10, 2012 at 05:18:42PM -0500, Chris Mason wrote:
> On Fri, Feb 10, 2012 at 08:30:51PM +0100, btrfs@nentwig.biz wrote:
> > Hi!
> >
> > I used to have arch linux running on 1 btrfs partition (sda1, incl. /boot).
> > When switching to 3.2.5 recently the system fails to boot:
> >
> > (after udevd)
> > /etc/rc.sysinit: line 15: 117 Bus error mountpoint -q /proc
> > and so on, no idea.
> >
> > It used to boot with 3.2.4, but
> >
> > 1) I obviously had some corruption in the tree, when I tried to delete a
> > certain file I hit e.g. "kernel BUG at fs/btrfs/extent-tree.c" message.
> >
> > 2) Even while running 3.2.4 I was unable to mount the partition from a
> > parallel gentoo or live USB install and I still am:
> >
> > # mount /dev/sda1 /mnt/arch/
> > mount: /dev/sda1: can't read superblock
> >
> > The strange thing is: when trying to boot from the partition the
> > boot loader (syslinux) is
> > obviously still able load the kernel from that partition.
> >
> > Tried btrfs-zero-log and some deperate other things. Result: I can
> > now actually
> > execute btrfsck which previously used to fail:
>
> Ok, step one:
>
> Pull down the dangerdonteveruse branch of btrfs-progs:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-progs.git dangerdonteveruse
>
> Run btrfs-debug-tree -r /dev/sda1 and send the output here please.
Sorry, that's btrfs-debug-tree -R /dev/sda1
-chris
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: can't read superblock (but could mount)
2012-02-10 23:39 ` Chris Mason
@ 2012-02-11 6:27 ` btrfs
2012-02-13 13:09 ` Chris Mason
0 siblings, 1 reply; 14+ messages in thread
From: btrfs @ 2012-02-11 6:27 UTC (permalink / raw)
To: Chris Mason; +Cc: linux-btrfs
Quoting Chris Mason <chris.mason@oracle.com>:
> On Fri, Feb 10, 2012 at 05:18:42PM -0500, Chris Mason wrote:
>> Ok, step one:
>>
>> Pull down the dangerdonteveruse branch of btrfs-progs:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-progs.git
>> dangerdonteveruse
>>
>> Run btrfs-debug-tree -r /dev/sda1 and send the output here please.
>
> Sorry, that's btrfs-debug-tree -R /dev/sda1
# ./btrfs-debug-tree -R /dev/sda1
root tree: 10229936128 level 1
chunk tree: 10364125184 level 1
extent tree key (EXTENT_TREE ROOT_ITEM 0) 10229944320 level 3
device tree key (DEV_TREE ROOT_ITEM 0) 10192654336 level 0
fs tree key (FS_TREE ROOT_ITEM 0) 10103791616 level 3
checksum tree key (CSUM_TREE ROOT_ITEM 0) 10103156736 level 2
data reloc tree key (DATA_RELOC_TREE ROOT_ITEM 0) 10027970560 level 0
btrfs root backup slot 0
tree root gen 157090 block 10229907456
extent root gen 157090 block 10229911552
chunk root gen 124887 block 10364125184
device root gen 124887 block 10192654336
csum root gen 157032 block 10103156736
fs root gen 157032 block 10103791616
15491051520 used 40020631552 total 1 devices
btrfs root backup slot 1
tree root gen 157091 block 10229948416
extent root gen 157091 block 10229952512
chunk root gen 124887 block 10364125184
device root gen 124887 block 10192654336
csum root gen 157032 block 10103156736
fs root gen 157032 block 10103791616
15491051520 used 40020631552 total 1 devices
btrfs root backup slot 2
tree root gen 157092 block 10229907456
extent root gen 157092 block 10229911552
chunk root gen 124887 block 10364125184
device root gen 124887 block 10192654336
csum root gen 157032 block 10103156736
fs root gen 157032 block 10103791616
15491051520 used 40020631552 total 1 devices
btrfs root backup slot 3
tree root gen 157093 block 10229936128
extent root gen 157093 block 10229944320
chunk root gen 124887 block 10364125184
device root gen 124887 block 10192654336
csum root gen 157032 block 10103156736
fs root gen 157032 block 10103791616
15491051520 used 40020631552 total 1 devices
total bytes 40020631552
bytes used 15491051520
uuid 9e9886fc-3e60-4c59-a246-727662769ee2
Btrfs Btrfs v0.19
But we it is that the bootloader apparently is able to load (at least)
the kernel (and initrd) from the partition?
^ permalink raw reply [flat|nested] 14+ messages in thread* Re: can't read superblock (but could mount)
2012-02-11 6:27 ` btrfs
@ 2012-02-13 13:09 ` Chris Mason
2012-02-14 17:37 ` Timo Nentwig
0 siblings, 1 reply; 14+ messages in thread
From: Chris Mason @ 2012-02-13 13:09 UTC (permalink / raw)
To: btrfs; +Cc: linux-btrfs
On Sat, Feb 11, 2012 at 07:27:25AM +0100, btrfs@nentwig.biz wrote:
>
> Quoting Chris Mason <chris.mason@oracle.com>:
>
> >On Fri, Feb 10, 2012 at 05:18:42PM -0500, Chris Mason wrote:
> >>Ok, step one:
> >>
> >>Pull down the dangerdonteveruse branch of btrfs-progs:
> >>
> >>git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-progs.git
> >>dangerdonteveruse
> >>
> >>Run btrfs-debug-tree -r /dev/sda1 and send the output here please.
> >
> >Sorry, that's btrfs-debug-tree -R /dev/sda1
>
> # ./btrfs-debug-tree -R /dev/sda1
> root tree: 10229936128 level 1
> chunk tree: 10364125184 level 1
> extent tree key (EXTENT_TREE ROOT_ITEM 0) 10229944320 level 3
> device tree key (DEV_TREE ROOT_ITEM 0) 10192654336 level 0
> fs tree key (FS_TREE ROOT_ITEM 0) 10103791616 level 3
> checksum tree key (CSUM_TREE ROOT_ITEM 0) 10103156736 level 2
> data reloc tree key (DATA_RELOC_TREE ROOT_ITEM 0) 10027970560 level 0
Ok, I'm surprised our bad block wasn't one of the roots, we're looking
for 9872289792.
Could you please do:
btrfs-debug-tree -b 9872289792 /dev/xxx
Then please run the new fsck (without any args) on the device and send
the output here. Before we mount with -o recovery or try to repair
things, I just want to double check where this bad block lives.
>
> But we it is that the bootloader apparently is able to load (at
> least) the kernel (and initrd) from the partition?
The btrfs-debug-tree command above should answer this, but I'd guess
that syslinux either isn't checking the parent trans id or it just
doesn't need to read this block to find the files. That's a good sign
;)
-chris
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: can't read superblock (but could mount)
2012-02-13 13:09 ` Chris Mason
@ 2012-02-14 17:37 ` Timo Nentwig
2012-02-14 18:41 ` Chris Mason
2012-02-17 3:35 ` Timo Nentwig
0 siblings, 2 replies; 14+ messages in thread
From: Timo Nentwig @ 2012-02-14 17:37 UTC (permalink / raw)
To: linux-btrfs
On Mon, 13 Feb 2012, Chris Mason wrote:
> btrfs-debug-tree -b 9872289792 /dev/xxx
# btrfs-debug-tree -b 9872289792 /dev/loop1
leaf 9872289792 items 51 free space 0 generation 120351 owner 5
fs uuid 9e9886fc-3e60-4c59-a246-727662769ee2
chunk uuid f7e4ac1e-f4d6-436b-9bda-8409311dcdb6
item 0 key (923514 DIR_ITEM 2120090750) itemoff 3950 itemsize 45
location key (2722082 INODE_ITEM 0) type 1
namelen 15 datalen 0 name: UTBI__24.pcf.gz
item 1 key (923514 DIR_ITEM 2120348073) itemoff 3895 itemsize 55
location key (2722204 INODE_ITEM 0) type 1
namelen 25 datalen 0 name: helvB12-ISO8859-14.pcf.gz
item 2 key (923514 DIR_ITEM 2123806861) itemoff 3840 itemsize 55
location key (2723467 INODE_ITEM 0) type 1
namelen 25 datalen 0 name: lutRS08-ISO8859-15.pcf.gz
item 3 key (923514 DIR_ITEM 2124181825) itemoff 3787 itemsize 53
location key (2722901 INODE_ITEM 0) type 1
namelen 23 datalen 0 name: timB10-ISO8859-9.pcf.gz
item 4 key (923514 DIR_ITEM 2124481083) itemoff 3734 itemsize 53
location key (2723388 INODE_ITEM 0) type 1
namelen 23 datalen 0 name: luIS19-ISO8859-9.pcf.gz
item 5 key (923514 DIR_ITEM 2127941711) itemoff 3679 itemsize 55
location key (2722919 INODE_ITEM 0) type 1
namelen 25 datalen 0 name: courBO18-ISO8859-2.pcf.gz
item 6 key (923514 DIR_ITEM 2128786561) itemoff 3624 itemsize 55
location key (2721907 INODE_ITEM 0) type 1
namelen 25 datalen 0 name: helvBO24-ISO8859-1.pcf.gz
item 7 key (923514 DIR_ITEM 2131308727) itemoff 3569 itemsize 55
location key (2723365 INODE_ITEM 0) type 1
namelen 25 datalen 0 name: ncenBI10-ISO8859-2.pcf.gz
item 8 key (923514 DIR_ITEM 2131961491) itemoff 3515 itemsize 54
location key (2723113 INODE_ITEM 0) type 1
namelen 24 datalen 0 name: ncenI10-ISO8859-4.pcf.gz
item 9 key (923514 DIR_ITEM 2132458601) itemoff 3461 itemsize 54
location key (2722426 INODE_ITEM 0) type 1
namelen 24 datalen 0 name: timI24-ISO8859-13.pcf.gz
item 10 key (923514 DIR_ITEM 2132654723) itemoff 3406 itemsize 55
location key (2722242 INODE_ITEM 0) type 1
namelen 25 datalen 0 name: ncenB08-ISO8859-14.pcf.gz
item 11 key (923514 DIR_ITEM 2136131400) itemoff 3353 itemsize 53
location key (2722472 INODE_ITEM 0) type 1
namelen 23 datalen 0 name: lubR10-ISO8859-2.pcf.gz
item 12 key (923514 DIR_ITEM 2136302367) itemoff 3298 itemsize 55
location key (2721978 INODE_ITEM 0) type 1
namelen 25 datalen 0 name: helvR14-ISO8859-15.pcf.gz
item 13 key (923514 DIR_ITEM 2141157400) itemoff 3244 itemsize 54
location key (2721809 INODE_ITEM 0) type 1
namelen 24 datalen 0 name: luRS24-ISO8859-10.pcf.gz
item 14 key (923514 DIR_ITEM 2143920500) itemoff 3190 itemsize 54
location key (2722139 INODE_ITEM 0) type 1
namelen 24 datalen 0 name: lutRS10-ISO8859-4.pcf.gz
item 15 key (923514 DIR_ITEM 2145353946) itemoff 3137 itemsize 53
location key (2722006 INODE_ITEM 0) type 1
namelen 23 datalen 0 name: timR18-ISO8859-9.pcf.gz
item 16 key (923514 DIR_ITEM 2146914640) itemoff 3082 itemsize 55
location key (2723588 INODE_ITEM 0) type 1
namelen 25 datalen 0 name: lutBS12-ISO8859-14.pcf.gz
item 17 key (923514 DIR_ITEM 2153679091) itemoff 3026 itemsize 56
location key (2722231 INODE_ITEM 0) type 1
namelen 26 datalen 0 name: UTB___12-ISO8859-10.pcf.gz
item 18 key (923514 DIR_ITEM 2155361241) itemoff 2971 itemsize 55
location key (2721854 INODE_ITEM 0) type 1
namelen 25 datalen 0 name: UTRG__24-ISO8859-3.pcf.gz
item 19 key (923514 DIR_ITEM 2164008501) itemoff 2917 itemsize 54
location key (2723441 INODE_ITEM 0) type 1
namelen 24 datalen 0 name: lubR14-ISO8859-13.pcf.gz
item 20 key (923514 DIR_ITEM 2164058590) itemoff 2872 itemsize 45
location key (2722030 INODE_ITEM 0) type 1
namelen 15 datalen 0 name: courBO18.pcf.gz
item 21 key (923514 DIR_ITEM 2164312387) itemoff 2827 itemsize 45
location key (2722107 INODE_ITEM 0) type 1
namelen 15 datalen 0 name: ncenBI12.pcf.gz
item 22 key (923514 DIR_ITEM 2166794582) itemoff 2773 itemsize 54
location key (2722054 INODE_ITEM 0) type 1
namelen 24 datalen 0 name: timB08-ISO8859-10.pcf.gz
item 23 key (923514 DIR_ITEM 2168622352) itemoff 2718 itemsize 55
location key (2722318 INODE_ITEM 0) type 1
namelen 25 datalen 0 name: courB18-ISO8859-14.pcf.gz
item 24 key (923514 DIR_ITEM 2175186950) itemoff 2664 itemsize 54
location key (2722350 INODE_ITEM 0) type 1
namelen 24 datalen 0 name: lubBI24-ISO8859-1.pcf.gz
item 25 key (923514 DIR_ITEM 2176060521) itemoff 2609 itemsize 55
location key (2722198 INODE_ITEM 0) type 1
namelen 25 datalen 0 name: lubBI12-ISO8859-10.pcf.gz
item 26 key (923514 DIR_ITEM 2176776172) itemoff 2566 itemsize 43
location key (2721916 INODE_ITEM 0) type 1
namelen 13 datalen 0 name: luIS24.pcf.gz
item 27 key (923514 DIR_ITEM 2177776018) itemoff 2512 itemsize 54
location key (2721796 INODE_ITEM 0) type 1
namelen 24 datalen 0 name: courB12-ISO8859-2.pcf.gz
item 28 key (923514 DIR_ITEM 2178161982) itemoff 2458 itemsize 54
location key (2723465 INODE_ITEM 0) type 1
namelen 24 datalen 0 name: helvR14-ISO8859-3.pcf.gz
item 29 key (923514 DIR_ITEM 2180020900) itemoff 2402 itemsize 56
location key (2723052 INODE_ITEM 0) type 1
namelen 26 datalen 0 name: helvBO10-ISO8859-14.pcf.gz
item 30 key (923514 DIR_ITEM 2180297770) itemoff 2348 itemsize 54
location key (2722286 INODE_ITEM 0) type 1
namelen 24 datalen 0 name: helvO08-ISO8859-9.pcf.gz
item 31 key (923514 DIR_ITEM 2181853127) itemoff 2305 itemsize 43
location key (2722790 INODE_ITEM 0) type 1
namelen 13 datalen 0 name: timB18.pcf.gz
item 32 key (923514 DIR_ITEM 2184201970) itemoff 2250 itemsize 55
location key (2721881 INODE_ITEM 0) type 1
namelen 25 datalen 0 name: courBO12-ISO8859-9.pcf.gz
item 33 key (923514 DIR_ITEM 2194151326) itemoff 2196 itemsize 54
location key (2723089 INODE_ITEM 0) type 1
namelen 24 datalen 0 name: luIS24-ISO8859-14.pcf.gz
item 34 key (923514 DIR_ITEM 2195147416) itemoff 2142 itemsize 54
location key (2722430 INODE_ITEM 0) type 1
namelen 24 datalen 0 name: timB14-ISO8859-10.pcf.gz
item 35 key (923514 DIR_ITEM 2197069934) itemoff 2089 itemsize 53
location key (2723319 INODE_ITEM 0) type 1
namelen 23 datalen 0 name: lubB12-ISO8859-9.pcf.gz
item 36 key (923514 DIR_ITEM 2198647210) itemoff 2034 itemsize 55
location key (2723014 INODE_ITEM 0) type 1
namelen 25 datalen 0 name: helvO18-ISO8859-14.pcf.gz
item 37 key (923514 DIR_ITEM 2198717947) itemoff 1980 itemsize 54
location key (2723004 INODE_ITEM 0) type 1
namelen 24 datalen 0 name: lubR08-ISO8859-13.pcf.gz
item 38 key (923514 DIR_ITEM 2199518165) itemoff 1925 itemsize 55
location key (2722585 INODE_ITEM 0) type 1
namelen 25 datalen 0 name: UTB___12-ISO8859-1.pcf.gz
item 39 key (923514 DIR_ITEM 2201622119) itemoff 1872 itemsize 53
location key (2723195 INODE_ITEM 0) type 1
namelen 23 datalen 0 name: timR12-ISO8859-2.pcf.gz
item 40 key (923514 DIR_ITEM 2203625663) itemoff 1817 itemsize 55
location key (2722069 INODE_ITEM 0) type 1
namelen 25 datalen 0 name: UTBI__10-ISO8859-1.pcf.gz
item 41 key (923514 DIR_ITEM 2208277171) itemoff 1763 itemsize 54
location key (2723509 INODE_ITEM 0) type 1
namelen 24 datalen 0 name: courO10-ISO8859-3.pcf.gz
item 42 key (923514 DIR_ITEM 2218325165) itemoff 1708 itemsize 55
location key (2723549 INODE_ITEM 0) type 1
namelen 25 datalen 0 name: helvB12-ISO8859-13.pcf.gz
item 43 key (923514 DIR_ITEM 2220510505) itemoff 1654 itemsize 54
location key (2722209 INODE_ITEM 0) type 1
namelen 24 datalen 0 name: helvR08-ISO8859-4.pcf.gz
item 44 key (923514 DIR_ITEM 2222221654) itemoff 1599 itemsize 55
location key (2722620 INODE_ITEM 0) type 1
namelen 25 datalen 0 name: luBIS12-ISO8859-14.pcf.gz
item 45 key (923514 DIR_ITEM 2229258471) itemoff 1546 itemsize 53
location key (2723152 INODE_ITEM 0) type 1
namelen 23 datalen 0 name: timR08-ISO8859-1.pcf.gz
item 46 key (923514 DIR_ITEM 2234719731) itemoff 1492 itemsize 54
location key (2723557 INODE_ITEM 0) type 1
namelen 24 datalen 0 name: luBIS08-ISO8859-9.pcf.gz
item 47 key (923514 DIR_ITEM 2235808109) itemoff 1438 itemsize 54
location key (2723080 INODE_ITEM 0) type 1
namelen 24 datalen 0 name: timI24-ISO8859-14.pcf.gz
item 48 key (923514 DIR_ITEM 2235875207) itemoff 1383 itemsize 55
location key (2723463 INODE_ITEM 0) type 1
namelen 25 datalen 0 name: ncenB08-ISO8859-13.pcf.gz
item 49 key (923514 DIR_ITEM 2236228503) itemoff 1329 itemsize 54
location key (2721755 INODE_ITEM 0) type 1
namelen 24 datalen 0 name: ncenI10-ISO8859-3.pcf.gz
item 50 key (923514 DIR_ITEM 2239005748) itemoff 1275 itemsize 54
location key (2721998 INODE_ITEM 0) type 1
namelen 24 datalen 0 name: lutBS10-ISO8859-9.pcf.gz
# btrfsck /dev/loop1
Extent back ref already exists for 9872289792 parent 0 root 5
leaf parent key incorrect 9872289792
bad block 9872289792
ref mismatch on [9872289792 4096] extent item 1, found 2
Incorrect global backref count on 9872289792 found 1 wanted 2
backpointer mismatch on [9872289792 4096]
owner ref check failed [9872289792 4096]
ref mismatch on [9889067008 4096] extent item 1, found 0
Backref 9889067008 root 5 not referenced
Incorrect global backref count on 9889067008 found 1 wanted 0
backpointer mismatch on [9889067008 4096]
owner ref check failed [9889067008 4096]
ref mismatch on [37163102208 65536] extent item 1, found 0
Incorrect local backref count on 37163102208 root 5 owner 3360937 offset 0 found
0 wanted 1
backpointer mismatch on [37163102208 65536]
owner ref check failed [37163102208 65536]
ref mismatch on [37163814912 36864] extent item 0, found 1
Backref 37163814912 root 5 owner 3360939 offset 0 num_refs 0 not found in extent
tree
Incorrect local backref count on 37163814912 root 5 owner 3360939 offset 0 found
1 wanted 0
backpointer mismatch on [37163814912 36864]
found 15491117056 bytes used err is 1
total csum bytes: 14764500
total tree bytes: 366956544
total fs tree bytes: 317714432
btree space waste bytes: 90628933
file data blocks allocated: 16182484992
referenced 17813028864
Btrfs Btrfs v0.19
# mount /dev/loop1 /tmp/b
mount: block device /dev/loop1 is write-protected, mounting read-only
# ls /tmp/b
bin boot dev etc home lib lib64 media mnt opt proc root run sbin
srv sys tmp usr var vm
# echo "hooray!"
Please explain :)
^ permalink raw reply [flat|nested] 14+ messages in thread* Re: can't read superblock (but could mount)
2012-02-14 17:37 ` Timo Nentwig
@ 2012-02-14 18:41 ` Chris Mason
2012-02-14 18:54 ` Timo Nentwig
2012-02-17 3:35 ` Timo Nentwig
1 sibling, 1 reply; 14+ messages in thread
From: Chris Mason @ 2012-02-14 18:41 UTC (permalink / raw)
To: Timo Nentwig; +Cc: linux-btrfs
On Tue, Feb 14, 2012 at 06:37:16PM +0100, Timo Nentwig wrote:
> On Mon, 13 Feb 2012, Chris Mason wrote:
>
> >btrfs-debug-tree -b 9872289792 /dev/xxx
>
> # btrfs-debug-tree -b 9872289792 /dev/loop1
> leaf 9872289792 items 51 free space 0 generation 120351 owner 5
Ok, so this block is full of directory items, definitely not crucial to
mounting.
>
> # btrfsck /dev/loop1
> Extent back ref already exists for 9872289792 parent 0 root 5
> leaf parent key incorrect 9872289792
> bad block 9872289792
The block is also corrupted, as in the keys in the block aren't what we
expect.
> ref mismatch on [9872289792 4096] extent item 1, found 2
> Incorrect global backref count on 9872289792 found 1 wanted 2
> backpointer mismatch on [9872289792 4096]
> owner ref check failed [9872289792 4096]
> ref mismatch on [9889067008 4096] extent item 1, found 0
> Backref 9889067008 root 5 not referenced
> Incorrect global backref count on 9889067008 found 1 wanted 0
> backpointer mismatch on [9889067008 4096]
> owner ref check failed [9889067008 4096]
> ref mismatch on [37163102208 65536] extent item 1, found 0
> Incorrect local backref count on 37163102208 root 5 owner 3360937
> offset 0 found 0 wanted 1
> backpointer mismatch on [37163102208 65536]
> owner ref check failed [37163102208 65536]
> ref mismatch on [37163814912 36864] extent item 0, found 1
> Backref 37163814912 root 5 owner 3360939 offset 0 num_refs 0 not
> found in extent tree
> Incorrect local backref count on 37163814912 root 5 owner 3360939
> offset 0 found 1 wanted 0
> backpointer mismatch on [37163814912 36864]
And then we have a few other blocks with incorrect reference counts.
> found 15491117056 bytes used err is 1
> total csum bytes: 14764500
> total tree bytes: 366956544
> total fs tree bytes: 317714432
> btree space waste bytes: 90628933
> file data blocks allocated: 16182484992
> referenced 17813028864
> Btrfs Btrfs v0.19
>
> # mount /dev/loop1 /tmp/b
> mount: block device /dev/loop1 is write-protected, mounting read-only
>
> # ls /tmp/b
> bin boot dev etc home lib lib64 media mnt opt proc root
> run sbin srv sys tmp usr var vm
>
> # echo "hooray!"
>
> Please explain :)
I didn't do it ;) All the commands I asked you to run were readonly.
The block is still corrupted. You've switched from /dev/sda to
/dev/loop0, and loop0 is readonly. So the readonly mount may be
stopping us from going into that bad branch of your tree (orphan cleanup
perhaps).
Regardless, the corrupt block isn't crucial, you should easily be able to
copy things off.
As for how we got here, I think you said you were originally running
something older than 3.2 when these problems started, correct?
-chris
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: can't read superblock (but could mount)
2012-02-14 18:41 ` Chris Mason
@ 2012-02-14 18:54 ` Timo Nentwig
2012-02-14 21:14 ` Chris Mason
0 siblings, 1 reply; 14+ messages in thread
From: Timo Nentwig @ 2012-02-14 18:54 UTC (permalink / raw)
To: linux-btrfs
On Tue, 14 Feb 2012, Chris Mason wrote:
> As for how we got here, I think you said you were originally running
> something older than 3.2 when these problems started, correct?
Nope, I was already on 3.2.1 or 3.2.4. I restored a backup in the meantime
and already had to soft-reset the box:
# ls -ltr ~/.kde4/share/config/
ls: reading directory /home/foo/.kde4/share/config/: Input/output error
Sigh...
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: can't read superblock (but could mount)
2012-02-14 18:54 ` Timo Nentwig
@ 2012-02-14 21:14 ` Chris Mason
2012-02-15 6:03 ` Timo Nentwig
0 siblings, 1 reply; 14+ messages in thread
From: Chris Mason @ 2012-02-14 21:14 UTC (permalink / raw)
To: Timo Nentwig; +Cc: linux-btrfs
On Tue, Feb 14, 2012 at 07:54:43PM +0100, Timo Nentwig wrote:
>
>
> On Tue, 14 Feb 2012, Chris Mason wrote:
>
> >As for how we got here, I think you said you were originally running
> >something older than 3.2 when these problems started, correct?
>
> Nope, I was already on 3.2.1 or 3.2.4. I restored a backup in the meantime
> and already had to soft-reset the box:
Ok, 3.2 shouldn't have done this. Was this an external drive? What
else do you have on the system?
>
> # ls -ltr ~/.kde4/share/config/
> ls: reading directory /home/foo/.kde4/share/config/: Input/output error
>
> Sigh...
Is this the same FS that was corrupted or a different one?
-chris
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: can't read superblock (but could mount)
2012-02-14 21:14 ` Chris Mason
@ 2012-02-15 6:03 ` Timo Nentwig
2012-02-15 13:23 ` Chris Mason
0 siblings, 1 reply; 14+ messages in thread
From: Timo Nentwig @ 2012-02-15 6:03 UTC (permalink / raw)
To: linux-btrfs
On Tue, 14 Feb 2012, Chris Mason wrote:
> Ok, 3.2 shouldn't have done this. Was this an external drive? What
> else do you have on the system?
Nothing special actually. Standard arch linux with virtualbox kernel modules.
It's a SSD if this should matter. Mounted with ssd,compress=lzo,noatime.
> Is this the same FS that was corrupted or a different one?
Different one. Created from an old 3.2.1 gentoo install (btrfs 0.19-dirty).
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: can't read superblock (but could mount)
2012-02-15 6:03 ` Timo Nentwig
@ 2012-02-15 13:23 ` Chris Mason
2012-02-16 17:04 ` Timo Nentwig
0 siblings, 1 reply; 14+ messages in thread
From: Chris Mason @ 2012-02-15 13:23 UTC (permalink / raw)
To: Timo Nentwig; +Cc: linux-btrfs
On Wed, Feb 15, 2012 at 07:03:49AM +0100, Timo Nentwig wrote:
>
>
> On Tue, 14 Feb 2012, Chris Mason wrote:
>
> >Ok, 3.2 shouldn't have done this. Was this an external drive? What
> >else do you have on the system?
>
> Nothing special actually. Standard arch linux with virtualbox kernel modules.
> It's a SSD if this should matter. Mounted with ssd,compress=lzo,noatime.
Ok, it sounds like we've got some memory corruption problems in here.
Hopefully not from virtualbox, but I'd start with an memtest.
>
> >Is this the same FS that was corrupted or a different one?
>
> Different one. Created from an old 3.2.1 gentoo install (btrfs 0.19-dirty).
Different FS, same machine? Please include all the kernel messages.
-chris
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: can't read superblock (but could mount)
2012-02-15 13:23 ` Chris Mason
@ 2012-02-16 17:04 ` Timo Nentwig
2012-02-16 18:14 ` Chris Mason
0 siblings, 1 reply; 14+ messages in thread
From: Timo Nentwig @ 2012-02-16 17:04 UTC (permalink / raw)
To: linux-btrfs
On Wed, 15 Feb 2012, Chris Mason wrote:
> Date: Wed, 15 Feb 2012 08:23:22 -0500
> From: Chris Mason <chris.mason@oracle.com>
> To: Timo Nentwig <btrfs@nentwig.biz>
> Cc: linux-btrfs@vger.kernel.org
> Subject: Re: can't read superblock (but could mount)
>
> On Wed, Feb 15, 2012 at 07:03:49AM +0100, Timo Nentwig wrote:
>> On Tue, 14 Feb 2012, Chris Mason wrote:
>>
>>> Ok, 3.2 shouldn't have done this. Was this an external drive? What
>>> else do you have on the system?
>>
>> Nothing special actually. Standard arch linux with virtualbox kernel modules.
>> It's a SSD if this should matter. Mounted with ssd,compress=lzo,noatime.
>
> Ok, it sounds like we've got some memory corruption problems in here.
> Hopefully not from virtualbox, but I'd start with an memtest.
Wow, now I'm really impressed! :) You are probably right. I overclocked memory
and ran memtest for like 1-2h without errors and had a rock solid system for
quite a while when I recently started to witness all kinds of random and
reoccuring crashes. Actually blamed the broken FS rather than to run memtest
again. Mea culpa.
So, I hit 1 error after a while, somewhat lowered clock freq and no error in
17h straight. I'll recreate the FS on that box.
Thanks a lot for your support!
>>> Is this the same FS that was corrupted or a different one?
>>
>> Different one. Created from an old 3.2.1 gentoo install (btrfs 0.19-dirty).
>
> Different FS, same machine? Please include all the kernel messages.
Yes, same machine, same SSD drive, new mkfs.btrfs.
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: can't read superblock (but could mount)
2012-02-16 17:04 ` Timo Nentwig
@ 2012-02-16 18:14 ` Chris Mason
0 siblings, 0 replies; 14+ messages in thread
From: Chris Mason @ 2012-02-16 18:14 UTC (permalink / raw)
To: Timo Nentwig; +Cc: linux-btrfs
On Thu, Feb 16, 2012 at 06:04:47PM +0100, Timo Nentwig wrote:
>
>
> On Wed, 15 Feb 2012, Chris Mason wrote:
>
> >Date: Wed, 15 Feb 2012 08:23:22 -0500
> >From: Chris Mason <chris.mason@oracle.com>
> >To: Timo Nentwig <btrfs@nentwig.biz>
> >Cc: linux-btrfs@vger.kernel.org
> >Subject: Re: can't read superblock (but could mount)
> >
> >On Wed, Feb 15, 2012 at 07:03:49AM +0100, Timo Nentwig wrote:
> >>On Tue, 14 Feb 2012, Chris Mason wrote:
> >>
> >>>Ok, 3.2 shouldn't have done this. Was this an external drive? What
> >>>else do you have on the system?
> >>
> >>Nothing special actually. Standard arch linux with virtualbox kernel modules.
> >>It's a SSD if this should matter. Mounted with ssd,compress=lzo,noatime.
> >
> >Ok, it sounds like we've got some memory corruption problems in here.
> >Hopefully not from virtualbox, but I'd start with an memtest.
>
> Wow, now I'm really impressed! :) You are probably right. I overclocked memory
> and ran memtest for like 1-2h without errors and had a rock solid
> system for quite a while when I recently started to witness all
> kinds of random and reoccuring crashes. Actually blamed the broken
> FS rather than to run memtest again. Mea culpa.
>
> So, I hit 1 error after a while, somewhat lowered clock freq and no
> error in 17h straight. I'll recreate the FS on that box.
Grin, never be impressed when kernel guys blame the memory. We might as
well be saying its cosmic rays.
Really though, for this particular type of corruption it is usually some
hardware problem, or a memory corruption bug in the kernel. Thanks for
humoring me and running the memtest.
-chris
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: can't read superblock (but could mount)
2012-02-14 17:37 ` Timo Nentwig
2012-02-14 18:41 ` Chris Mason
@ 2012-02-17 3:35 ` Timo Nentwig
1 sibling, 0 replies; 14+ messages in thread
From: Timo Nentwig @ 2012-02-17 3:35 UTC (permalink / raw)
To: linux-btrfs
On Tue, 14 Feb 2012, Timo Nentwig wrote:
> Date: Tue, 14 Feb 2012 18:37:16 +0100 (CET)
> From: Timo Nentwig <btrfs@nentwig.biz>
> To: linux-btrfs@vger.kernel.org
> Subject: Re: can't read superblock (but could mount)
>
> On Mon, 13 Feb 2012, Chris Mason wrote:
>
>> btrfs-debug-tree -b 9872289792 /dev/xxx
Hm, just did it again and this time it fails (?!):
[root@server tcn]# losetup /dev/loop0 /mnt/foo/sda1
[root@server tcn]# btrfs-debug-tree -b 9872289792 /dev/loop0
leaf 9872289792 items 51 free space 0 generation 120351 owner 5
fs uuid 9e9886fc-3e60-4c59-a246-727662769ee2
chunk uuid f7e4ac1e-f4d6-436b-9bda-8409311dcdb6
item 0 key (923514 DIR_ITEM 2120090750) itemoff 3950 itemsize 45
location key (2722082 INODE_ITEM 0) type 1
namelen 15 datalen 0 name: UTBI__24.pcf.gz
item 1 key (923514 DIR_ITEM 2120348073) itemoff 3895 itemsize 55
location key (2722204 INODE_ITEM 0) type 1
namelen 25 datalen 0 name: helvB12-ISO8859-14.pcf.gz
item 2 key (923514 DIR_ITEM 2123806861) itemoff 3840 itemsize 55
location key (2723467 INODE_ITEM 0) type 1
namelen 25 datalen 0 name: lutRS08-ISO8859-15.pcf.gz
item 3 key (923514 DIR_ITEM 2124181825) itemoff 3787 itemsize 53
location key (2722901 INODE_ITEM 0) type 1
namelen 23 datalen 0 name: timB10-ISO8859-9.pcf.gz
item 4 key (923514 DIR_ITEM 2124481083) itemoff 3734 itemsize 53
location key (2723388 INODE_ITEM 0) type 1
namelen 23 datalen 0 name: luIS19-ISO8859-9.pcf.gz
item 5 key (923514 DIR_ITEM 2127941711) itemoff 3679 itemsize 55
location key (2722919 INODE_ITEM 0) type 1
namelen 25 datalen 0 name: courBO18-ISO8859-2.pcf.gz
item 6 key (923514 DIR_ITEM 2128786561) itemoff 3624 itemsize 55
location key (2721907 INODE_ITEM 0) type 1
namelen 25 datalen 0 name: helvBO24-ISO8859-1.pcf.gz
item 7 key (923514 DIR_ITEM 2131308727) itemoff 3569 itemsize 55
location key (2723365 INODE_ITEM 0) type 1
namelen 25 datalen 0 name: ncenBI10-ISO8859-2.pcf.gz
item 8 key (923514 DIR_ITEM 2131961491) itemoff 3515 itemsize 54
location key (2723113 INODE_ITEM 0) type 1
namelen 24 datalen 0 name: ncenI10-ISO8859-4.pcf.gz
item 9 key (923514 DIR_ITEM 2132458601) itemoff 3461 itemsize 54
location key (2722426 INODE_ITEM 0) type 1
namelen 24 datalen 0 name: timI24-ISO8859-13.pcf.gz
item 10 key (923514 DIR_ITEM 2132654723) itemoff 3406 itemsize 55
location key (2722242 INODE_ITEM 0) type 1
namelen 25 datalen 0 name: ncenB08-ISO8859-14.pcf.gz
item 11 key (923514 DIR_ITEM 2136131400) itemoff 3353 itemsize 53
location key (2722472 INODE_ITEM 0) type 1
namelen 23 datalen 0 name: lubR10-ISO8859-2.pcf.gz
item 12 key (923514 DIR_ITEM 2136302367) itemoff 3298 itemsize 55
location key (2721978 INODE_ITEM 0) type 1
namelen 25 datalen 0 name: helvR14-ISO8859-15.pcf.gz
item 13 key (923514 DIR_ITEM 2141157400) itemoff 3244 itemsize 54
location key (2721809 INODE_ITEM 0) type 1
namelen 24 datalen 0 name: luRS24-ISO8859-10.pcf.gz
item 14 key (923514 DIR_ITEM 2143920500) itemoff 3190 itemsize 54
location key (2722139 INODE_ITEM 0) type 1
namelen 24 datalen 0 name: lutRS10-ISO8859-4.pcf.gz
item 15 key (923514 DIR_ITEM 2145353946) itemoff 3137 itemsize 53
location key (2722006 INODE_ITEM 0) type 1
namelen 23 datalen 0 name: timR18-ISO8859-9.pcf.gz
item 16 key (923514 DIR_ITEM 2146914640) itemoff 3082 itemsize 55
location key (2723588 INODE_ITEM 0) type 1
namelen 25 datalen 0 name: lutBS12-ISO8859-14.pcf.gz
item 17 key (923514 DIR_ITEM 2153679091) itemoff 3026 itemsize 56
location key (2722231 INODE_ITEM 0) type 1
namelen 26 datalen 0 name: UTB___12-ISO8859-10.pcf.gz
item 18 key (923514 DIR_ITEM 2155361241) itemoff 2971 itemsize 55
location key (2721854 INODE_ITEM 0) type 1
namelen 25 datalen 0 name: UTRG__24-ISO8859-3.pcf.gz
item 19 key (923514 DIR_ITEM 2164008501) itemoff 2917 itemsize 54
location key (2723441 INODE_ITEM 0) type 1
namelen 24 datalen 0 name: lubR14-ISO8859-13.pcf.gz
item 20 key (923514 DIR_ITEM 2164058590) itemoff 2872 itemsize 45
location key (2722030 INODE_ITEM 0) type 1
namelen 15 datalen 0 name: courBO18.pcf.gz
item 21 key (923514 DIR_ITEM 2164312387) itemoff 2827 itemsize 45
location key (2722107 INODE_ITEM 0) type 1
namelen 15 datalen 0 name: ncenBI12.pcf.gz
item 22 key (923514 DIR_ITEM 2166794582) itemoff 2773 itemsize 54
location key (2722054 INODE_ITEM 0) type 1
namelen 24 datalen 0 name: timB08-ISO8859-10.pcf.gz
item 23 key (923514 DIR_ITEM 2168622352) itemoff 2718 itemsize 55
location key (2722318 INODE_ITEM 0) type 1
namelen 25 datalen 0 name: courB18-ISO8859-14.pcf.gz
item 24 key (923514 DIR_ITEM 2175186950) itemoff 2664 itemsize 54
location key (2722350 INODE_ITEM 0) type 1
namelen 24 datalen 0 name: lubBI24-ISO8859-1.pcf.gz
item 25 key (923514 DIR_ITEM 2176060521) itemoff 2609 itemsize 55
location key (2722198 INODE_ITEM 0) type 1
namelen 25 datalen 0 name: lubBI12-ISO8859-10.pcf.gz
item 26 key (923514 DIR_ITEM 2176776172) itemoff 2566 itemsize 43
location key (2721916 INODE_ITEM 0) type 1
namelen 13 datalen 0 name: luIS24.pcf.gz
item 27 key (923514 DIR_ITEM 2177776018) itemoff 2512 itemsize 54
location key (2721796 INODE_ITEM 0) type 1
namelen 24 datalen 0 name: courB12-ISO8859-2.pcf.gz
item 28 key (923514 DIR_ITEM 2178161982) itemoff 2458 itemsize 54
location key (2723465 INODE_ITEM 0) type 1
namelen 24 datalen 0 name: helvR14-ISO8859-3.pcf.gz
item 29 key (923514 DIR_ITEM 2180020900) itemoff 2402 itemsize 56
location key (2723052 INODE_ITEM 0) type 1
namelen 26 datalen 0 name: helvBO10-ISO8859-14.pcf.gz
item 30 key (923514 DIR_ITEM 2180297770) itemoff 2348 itemsize 54
location key (2722286 INODE_ITEM 0) type 1
namelen 24 datalen 0 name: helvO08-ISO8859-9.pcf.gz
item 31 key (923514 DIR_ITEM 2181853127) itemoff 2305 itemsize 43
location key (2722790 INODE_ITEM 0) type 1
namelen 13 datalen 0 name: timB18.pcf.gz
item 32 key (923514 DIR_ITEM 2184201970) itemoff 2250 itemsize 55
location key (2721881 INODE_ITEM 0) type 1
namelen 25 datalen 0 name: courBO12-ISO8859-9.pcf.gz
item 33 key (923514 DIR_ITEM 2194151326) itemoff 2196 itemsize 54
location key (2723089 INODE_ITEM 0) type 1
namelen 24 datalen 0 name: luIS24-ISO8859-14.pcf.gz
item 34 key (923514 DIR_ITEM 2195147416) itemoff 2142 itemsize 54
location key (2722430 INODE_ITEM 0) type 1
namelen 24 datalen 0 name: timB14-ISO8859-10.pcf.gz
item 35 key (923514 DIR_ITEM 2197069934) itemoff 2089 itemsize 53
location key (2723319 INODE_ITEM 0) type 1
namelen 23 datalen 0 name: lubB12-ISO8859-9.pcf.gz
item 36 key (923514 DIR_ITEM 2198647210) itemoff 2034 itemsize 55
location key (2723014 INODE_ITEM 0) type 1
namelen 25 datalen 0 name: helvO18-ISO8859-14.pcf.gz
item 37 key (923514 DIR_ITEM 2198717947) itemoff 1980 itemsize 54
location key (2723004 INODE_ITEM 0) type 1
namelen 24 datalen 0 name: lubR08-ISO8859-13.pcf.gz
item 38 key (923514 DIR_ITEM 2199518165) itemoff 1925 itemsize 55
location key (2722585 INODE_ITEM 0) type 1
namelen 25 datalen 0 name: UTB___12-ISO8859-1.pcf.gz
item 39 key (923514 DIR_ITEM 2201622119) itemoff 1872 itemsize 53
location key (2723195 INODE_ITEM 0) type 1
namelen 23 datalen 0 name: timR12-ISO8859-2.pcf.gz
item 40 key (923514 DIR_ITEM 2203625663) itemoff 1817 itemsize 55
location key (2722069 INODE_ITEM 0) type 1
namelen 25 datalen 0 name: UTBI__10-ISO8859-1.pcf.gz
item 41 key (923514 DIR_ITEM 2208277171) itemoff 1763 itemsize 54
location key (2723509 INODE_ITEM 0) type 1
namelen 24 datalen 0 name: courO10-ISO8859-3.pcf.gz
item 42 key (923514 DIR_ITEM 2218325165) itemoff 1708 itemsize 55
location key (2723549 INODE_ITEM 0) type 1
namelen 25 datalen 0 name: helvB12-ISO8859-13.pcf.gz
item 43 key (923514 DIR_ITEM 2220510505) itemoff 1654 itemsize 54
location key (2722209 INODE_ITEM 0) type 1
namelen 24 datalen 0 name: helvR08-ISO8859-4.pcf.gz
item 44 key (923514 DIR_ITEM 2222221654) itemoff 1599 itemsize 55
location key (2722620 INODE_ITEM 0) type 1
namelen 25 datalen 0 name: luBIS12-ISO8859-14.pcf.gz
item 45 key (923514 DIR_ITEM 2229258471) itemoff 1546 itemsize 53
location key (2723152 INODE_ITEM 0) type 1
namelen 23 datalen 0 name: timR08-ISO8859-1.pcf.gz
item 46 key (923514 DIR_ITEM 2234719731) itemoff 1492 itemsize 54
location key (2723557 INODE_ITEM 0) type 1
namelen 24 datalen 0 name: luBIS08-ISO8859-9.pcf.gz
item 47 key (923514 DIR_ITEM 2235808109) itemoff 1438 itemsize 54
location key (2723080 INODE_ITEM 0) type 1
namelen 24 datalen 0 name: timI24-ISO8859-14.pcf.gz
item 48 key (923514 DIR_ITEM 2235875207) itemoff 1383 itemsize 55
location key (2723463 INODE_ITEM 0) type 1
namelen 25 datalen 0 name: ncenB08-ISO8859-13.pcf.gz
item 49 key (923514 DIR_ITEM 2236228503) itemoff 1329 itemsize 54
location key (2721755 INODE_ITEM 0) type 1
namelen 24 datalen 0 name: ncenI10-ISO8859-3.pcf.gz
item 50 key (923514 DIR_ITEM 2239005748) itemoff 1275 itemsize 54
location key (2721998 INODE_ITEM 0) type 1
namelen 24 datalen 0 name: lutBS10-ISO8859-9.pcf.gz
[root@server tcn]# btrfsck /dev/loop0
Extent back ref already exists for 9872289792 parent 0 root 5
leaf parent key incorrect 9872289792
bad block 9872289792
ref mismatch on [9872289792 4096] extent item 1, found 2
Incorrect global backref count on 9872289792 found 1 wanted 2
backpointer mismatch on [9872289792 4096]
owner ref check failed [9872289792 4096]
ref mismatch on [9889067008 4096] extent item 1, found 0
Backref 9889067008 root 5 not referenced
Incorrect global backref count on 9889067008 found 1 wanted 0
backpointer mismatch on [9889067008 4096]
owner ref check failed [9889067008 4096]
ref mismatch on [37163102208 65536] extent item 1, found 0
Incorrect local backref count on 37163102208 root 5 owner 3360937 offset 0 found
0 wanted 1
backpointer mismatch on [37163102208 65536]
owner ref check failed [37163102208 65536]
ref mismatch on [37163814912 36864] extent item 0, found 1
Backref 37163814912 root 5 owner 3360939 offset 0 num_refs 0 not found in extent
tree
Incorrect local backref count on 37163814912 root 5 owner 3360939 offset 0 found
1 wanted 0
backpointer mismatch on [37163814912 36864]
found 15491117056 bytes used err is 1
total csum bytes: 14764500
total tree bytes: 366956544
total fs tree bytes: 317714432
btree space waste bytes: 90628933
file data blocks allocated: 16182484992
referenced 17813028864
Btrfs Btrfs v0.19
[root@server tcn]# mount /dev/loop0 /tmp/b
mount: /dev/loop0: can't read superblock
> # btrfs-debug-tree -b 9872289792 /dev/loop1
> leaf 9872289792 items 51 free space 0 generation 120351 owner 5
> fs uuid 9e9886fc-3e60-4c59-a246-727662769ee2
> chunk uuid f7e4ac1e-f4d6-436b-9bda-8409311dcdb6
> item 0 key (923514 DIR_ITEM 2120090750) itemoff 3950 itemsize 45
> location key (2722082 INODE_ITEM 0) type 1
> namelen 15 datalen 0 name: UTBI__24.pcf.gz
> item 1 key (923514 DIR_ITEM 2120348073) itemoff 3895 itemsize 55
> location key (2722204 INODE_ITEM 0) type 1
> namelen 25 datalen 0 name: helvB12-ISO8859-14.pcf.gz
> item 2 key (923514 DIR_ITEM 2123806861) itemoff 3840 itemsize 55
> location key (2723467 INODE_ITEM 0) type 1
> namelen 25 datalen 0 name: lutRS08-ISO8859-15.pcf.gz
> item 3 key (923514 DIR_ITEM 2124181825) itemoff 3787 itemsize 53
> location key (2722901 INODE_ITEM 0) type 1
> namelen 23 datalen 0 name: timB10-ISO8859-9.pcf.gz
> item 4 key (923514 DIR_ITEM 2124481083) itemoff 3734 itemsize 53
> location key (2723388 INODE_ITEM 0) type 1
> namelen 23 datalen 0 name: luIS19-ISO8859-9.pcf.gz
> item 5 key (923514 DIR_ITEM 2127941711) itemoff 3679 itemsize 55
> location key (2722919 INODE_ITEM 0) type 1
> namelen 25 datalen 0 name: courBO18-ISO8859-2.pcf.gz
> item 6 key (923514 DIR_ITEM 2128786561) itemoff 3624 itemsize 55
> location key (2721907 INODE_ITEM 0) type 1
> namelen 25 datalen 0 name: helvBO24-ISO8859-1.pcf.gz
> item 7 key (923514 DIR_ITEM 2131308727) itemoff 3569 itemsize 55
> location key (2723365 INODE_ITEM 0) type 1
> namelen 25 datalen 0 name: ncenBI10-ISO8859-2.pcf.gz
> item 8 key (923514 DIR_ITEM 2131961491) itemoff 3515 itemsize 54
> location key (2723113 INODE_ITEM 0) type 1
> namelen 24 datalen 0 name: ncenI10-ISO8859-4.pcf.gz
> item 9 key (923514 DIR_ITEM 2132458601) itemoff 3461 itemsize 54
> location key (2722426 INODE_ITEM 0) type 1
> namelen 24 datalen 0 name: timI24-ISO8859-13.pcf.gz
> item 10 key (923514 DIR_ITEM 2132654723) itemoff 3406 itemsize 55
> location key (2722242 INODE_ITEM 0) type 1
> namelen 25 datalen 0 name: ncenB08-ISO8859-14.pcf.gz
> item 11 key (923514 DIR_ITEM 2136131400) itemoff 3353 itemsize 53
> location key (2722472 INODE_ITEM 0) type 1
> namelen 23 datalen 0 name: lubR10-ISO8859-2.pcf.gz
> item 12 key (923514 DIR_ITEM 2136302367) itemoff 3298 itemsize 55
> location key (2721978 INODE_ITEM 0) type 1
> namelen 25 datalen 0 name: helvR14-ISO8859-15.pcf.gz
> item 13 key (923514 DIR_ITEM 2141157400) itemoff 3244 itemsize 54
> location key (2721809 INODE_ITEM 0) type 1
> namelen 24 datalen 0 name: luRS24-ISO8859-10.pcf.gz
> item 14 key (923514 DIR_ITEM 2143920500) itemoff 3190 itemsize 54
> location key (2722139 INODE_ITEM 0) type 1
> namelen 24 datalen 0 name: lutRS10-ISO8859-4.pcf.gz
> item 15 key (923514 DIR_ITEM 2145353946) itemoff 3137 itemsize 53
> location key (2722006 INODE_ITEM 0) type 1
> namelen 23 datalen 0 name: timR18-ISO8859-9.pcf.gz
> item 16 key (923514 DIR_ITEM 2146914640) itemoff 3082 itemsize 55
> location key (2723588 INODE_ITEM 0) type 1
> namelen 25 datalen 0 name: lutBS12-ISO8859-14.pcf.gz
> item 17 key (923514 DIR_ITEM 2153679091) itemoff 3026 itemsize 56
> location key (2722231 INODE_ITEM 0) type 1
> namelen 26 datalen 0 name: UTB___12-ISO8859-10.pcf.gz
> item 18 key (923514 DIR_ITEM 2155361241) itemoff 2971 itemsize 55
> location key (2721854 INODE_ITEM 0) type 1
> namelen 25 datalen 0 name: UTRG__24-ISO8859-3.pcf.gz
> item 19 key (923514 DIR_ITEM 2164008501) itemoff 2917 itemsize 54
> location key (2723441 INODE_ITEM 0) type 1
> namelen 24 datalen 0 name: lubR14-ISO8859-13.pcf.gz
> item 20 key (923514 DIR_ITEM 2164058590) itemoff 2872 itemsize 45
> location key (2722030 INODE_ITEM 0) type 1
> namelen 15 datalen 0 name: courBO18.pcf.gz
> item 21 key (923514 DIR_ITEM 2164312387) itemoff 2827 itemsize 45
> location key (2722107 INODE_ITEM 0) type 1
> namelen 15 datalen 0 name: ncenBI12.pcf.gz
> item 22 key (923514 DIR_ITEM 2166794582) itemoff 2773 itemsize 54
> location key (2722054 INODE_ITEM 0) type 1
> namelen 24 datalen 0 name: timB08-ISO8859-10.pcf.gz
> item 23 key (923514 DIR_ITEM 2168622352) itemoff 2718 itemsize 55
> location key (2722318 INODE_ITEM 0) type 1
> namelen 25 datalen 0 name: courB18-ISO8859-14.pcf.gz
> item 24 key (923514 DIR_ITEM 2175186950) itemoff 2664 itemsize 54
> location key (2722350 INODE_ITEM 0) type 1
> namelen 24 datalen 0 name: lubBI24-ISO8859-1.pcf.gz
> item 25 key (923514 DIR_ITEM 2176060521) itemoff 2609 itemsize 55
> location key (2722198 INODE_ITEM 0) type 1
> namelen 25 datalen 0 name: lubBI12-ISO8859-10.pcf.gz
> item 26 key (923514 DIR_ITEM 2176776172) itemoff 2566 itemsize 43
> location key (2721916 INODE_ITEM 0) type 1
> namelen 13 datalen 0 name: luIS24.pcf.gz
> item 27 key (923514 DIR_ITEM 2177776018) itemoff 2512 itemsize 54
> location key (2721796 INODE_ITEM 0) type 1
> namelen 24 datalen 0 name: courB12-ISO8859-2.pcf.gz
> item 28 key (923514 DIR_ITEM 2178161982) itemoff 2458 itemsize 54
> location key (2723465 INODE_ITEM 0) type 1
> namelen 24 datalen 0 name: helvR14-ISO8859-3.pcf.gz
> item 29 key (923514 DIR_ITEM 2180020900) itemoff 2402 itemsize 56
> location key (2723052 INODE_ITEM 0) type 1
> namelen 26 datalen 0 name: helvBO10-ISO8859-14.pcf.gz
> item 30 key (923514 DIR_ITEM 2180297770) itemoff 2348 itemsize 54
> location key (2722286 INODE_ITEM 0) type 1
> namelen 24 datalen 0 name: helvO08-ISO8859-9.pcf.gz
> item 31 key (923514 DIR_ITEM 2181853127) itemoff 2305 itemsize 43
> location key (2722790 INODE_ITEM 0) type 1
> namelen 13 datalen 0 name: timB18.pcf.gz
> item 32 key (923514 DIR_ITEM 2184201970) itemoff 2250 itemsize 55
> location key (2721881 INODE_ITEM 0) type 1
> namelen 25 datalen 0 name: courBO12-ISO8859-9.pcf.gz
> item 33 key (923514 DIR_ITEM 2194151326) itemoff 2196 itemsize 54
> location key (2723089 INODE_ITEM 0) type 1
> namelen 24 datalen 0 name: luIS24-ISO8859-14.pcf.gz
> item 34 key (923514 DIR_ITEM 2195147416) itemoff 2142 itemsize 54
> location key (2722430 INODE_ITEM 0) type 1
> namelen 24 datalen 0 name: timB14-ISO8859-10.pcf.gz
> item 35 key (923514 DIR_ITEM 2197069934) itemoff 2089 itemsize 53
> location key (2723319 INODE_ITEM 0) type 1
> namelen 23 datalen 0 name: lubB12-ISO8859-9.pcf.gz
> item 36 key (923514 DIR_ITEM 2198647210) itemoff 2034 itemsize 55
> location key (2723014 INODE_ITEM 0) type 1
> namelen 25 datalen 0 name: helvO18-ISO8859-14.pcf.gz
> item 37 key (923514 DIR_ITEM 2198717947) itemoff 1980 itemsize 54
> location key (2723004 INODE_ITEM 0) type 1
> namelen 24 datalen 0 name: lubR08-ISO8859-13.pcf.gz
> item 38 key (923514 DIR_ITEM 2199518165) itemoff 1925 itemsize 55
> location key (2722585 INODE_ITEM 0) type 1
> namelen 25 datalen 0 name: UTB___12-ISO8859-1.pcf.gz
> item 39 key (923514 DIR_ITEM 2201622119) itemoff 1872 itemsize 53
> location key (2723195 INODE_ITEM 0) type 1
> namelen 23 datalen 0 name: timR12-ISO8859-2.pcf.gz
> item 40 key (923514 DIR_ITEM 2203625663) itemoff 1817 itemsize 55
> location key (2722069 INODE_ITEM 0) type 1
> namelen 25 datalen 0 name: UTBI__10-ISO8859-1.pcf.gz
> item 41 key (923514 DIR_ITEM 2208277171) itemoff 1763 itemsize 54
> location key (2723509 INODE_ITEM 0) type 1
> namelen 24 datalen 0 name: courO10-ISO8859-3.pcf.gz
> item 42 key (923514 DIR_ITEM 2218325165) itemoff 1708 itemsize 55
> location key (2723549 INODE_ITEM 0) type 1
> namelen 25 datalen 0 name: helvB12-ISO8859-13.pcf.gz
> item 43 key (923514 DIR_ITEM 2220510505) itemoff 1654 itemsize 54
> location key (2722209 INODE_ITEM 0) type 1
> namelen 24 datalen 0 name: helvR08-ISO8859-4.pcf.gz
> item 44 key (923514 DIR_ITEM 2222221654) itemoff 1599 itemsize 55
> location key (2722620 INODE_ITEM 0) type 1
> namelen 25 datalen 0 name: luBIS12-ISO8859-14.pcf.gz
> item 45 key (923514 DIR_ITEM 2229258471) itemoff 1546 itemsize 53
> location key (2723152 INODE_ITEM 0) type 1
> namelen 23 datalen 0 name: timR08-ISO8859-1.pcf.gz
> item 46 key (923514 DIR_ITEM 2234719731) itemoff 1492 itemsize 54
> location key (2723557 INODE_ITEM 0) type 1
> namelen 24 datalen 0 name: luBIS08-ISO8859-9.pcf.gz
> item 47 key (923514 DIR_ITEM 2235808109) itemoff 1438 itemsize 54
> location key (2723080 INODE_ITEM 0) type 1
> namelen 24 datalen 0 name: timI24-ISO8859-14.pcf.gz
> item 48 key (923514 DIR_ITEM 2235875207) itemoff 1383 itemsize 55
> location key (2723463 INODE_ITEM 0) type 1
> namelen 25 datalen 0 name: ncenB08-ISO8859-13.pcf.gz
> item 49 key (923514 DIR_ITEM 2236228503) itemoff 1329 itemsize 54
> location key (2721755 INODE_ITEM 0) type 1
> namelen 24 datalen 0 name: ncenI10-ISO8859-3.pcf.gz
> item 50 key (923514 DIR_ITEM 2239005748) itemoff 1275 itemsize 54
> location key (2721998 INODE_ITEM 0) type 1
> namelen 24 datalen 0 name: lutBS10-ISO8859-9.pcf.gz
>
> # btrfsck /dev/loop1
> Extent back ref already exists for 9872289792 parent 0 root 5
> leaf parent key incorrect 9872289792
> bad block 9872289792
> ref mismatch on [9872289792 4096] extent item 1, found 2
> Incorrect global backref count on 9872289792 found 1 wanted 2
> backpointer mismatch on [9872289792 4096]
> owner ref check failed [9872289792 4096]
> ref mismatch on [9889067008 4096] extent item 1, found 0
> Backref 9889067008 root 5 not referenced
> Incorrect global backref count on 9889067008 found 1 wanted 0
> backpointer mismatch on [9889067008 4096]
> owner ref check failed [9889067008 4096]
> ref mismatch on [37163102208 65536] extent item 1, found 0
> Incorrect local backref count on 37163102208 root 5 owner 3360937 offset 0
> found 0 wanted 1
> backpointer mismatch on [37163102208 65536]
> owner ref check failed [37163102208 65536]
> ref mismatch on [37163814912 36864] extent item 0, found 1
> Backref 37163814912 root 5 owner 3360939 offset 0 num_refs 0 not found in
> extent tree
> Incorrect local backref count on 37163814912 root 5 owner 3360939 offset 0
> found 1 wanted 0
> backpointer mismatch on [37163814912 36864]
> found 15491117056 bytes used err is 1
> total csum bytes: 14764500
> total tree bytes: 366956544
> total fs tree bytes: 317714432
> btree space waste bytes: 90628933
> file data blocks allocated: 16182484992
> referenced 17813028864
> Btrfs Btrfs v0.19
>
> # mount /dev/loop1 /tmp/b
> mount: block device /dev/loop1 is write-protected, mounting read-only
>
> # ls /tmp/b
> bin boot dev etc home lib lib64 media mnt opt proc root run sbin
> srv sys tmp usr var vm
>
> # echo "hooray!"
>
>
> Please explain :)
> --
> 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
>
>
^ permalink raw reply [flat|nested] 14+ messages in thread
end of thread, other threads:[~2012-02-17 3:35 UTC | newest]
Thread overview: 14+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-02-10 19:30 can't read superblock (but could mount) btrfs
2012-02-10 22:18 ` Chris Mason
2012-02-10 23:39 ` Chris Mason
2012-02-11 6:27 ` btrfs
2012-02-13 13:09 ` Chris Mason
2012-02-14 17:37 ` Timo Nentwig
2012-02-14 18:41 ` Chris Mason
2012-02-14 18:54 ` Timo Nentwig
2012-02-14 21:14 ` Chris Mason
2012-02-15 6:03 ` Timo Nentwig
2012-02-15 13:23 ` Chris Mason
2012-02-16 17:04 ` Timo Nentwig
2012-02-16 18:14 ` Chris Mason
2012-02-17 3:35 ` Timo Nentwig
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).