* BTRFS filesystem is not mountable after crash
@ 2012-08-20 21:42 Alfred Zastrow
2012-08-26 5:27 ` Alfred Zastrow
0 siblings, 1 reply; 6+ messages in thread
From: Alfred Zastrow @ 2012-08-20 21:42 UTC (permalink / raw)
To: linux-btrfs
Hi devs,
I've a serious problem with my 160 gb SSD which is not mountable
anymore. A backup for most of the date is there, but not for the latest
ones. :-(
The crash occurred during a download (system hangs totaly, hard reset)
with a Fedora 3.5.2 linux kernel. The btrfs partition was working quite
good for about one year.
here is a try to attach the device and mount manually:
-----------------------------------------------------
[ 3123.582387] sd 1:0:0:0: Attached scsi generic sg2 type 0
[ 3123.582833] sdb: sdb1
[ 3123.583085] sd 1:0:0:0: [sdb] Attached SCSI disk
[ 3169.789800] Btrfs loaded
[ 3169.791156] device fsid 4d00f0e6-e9d7-42d9-8514-827d8f01f7d3 devid 1
transid 192331 /dev/sdb1
[ 3169.796334] btrfs: bdev /dev/sdb1 errs: wr 0, rd 0, flush 0, corrupt
16, gen 0
[ 3169.840296] Btrfs detected SSD devices, enabling SSD mode
[ 3169.841541] btrfs bad tree block start 0 29450240
[ 3169.841545] btrfs: bdev /dev/sdb1 errs: wr 0, rd 0, flush 0, corrupt
17, gen 0
[ 3169.841605] btrfs bad tree block start 0 29450240
[ 3169.841609] btrfs: bdev /dev/sdb1 errs: wr 0, rd 0, flush 0, corrupt
18, gen 0
[ 3123.582387] sd 1:0:0:0: Attached scsi generic sg2 type 0
[ 3123.582833] sdb: sdb1
[ 3123.583085] sd 1:0:0:0: [sdb] Attached SCSI disk
[ 3169.789800] Btrfs loaded
[ 3169.791156] device fsid 4d00f0e6-e9d7-42d9-8514-827d8f01f7d3 devid 1
transid 192331 /dev/sdb1
[ 3169.796334] btrfs: bdev /dev/sdb1 errs: wr 0, rd 0, flush 0, corrupt
16, gen 0
[ 3169.840296] Btrfs detected SSD devices, enabling SSD mode
[ 3169.841541] btrfs bad tree block start 0 29450240
[ 3169.841545] btrfs: bdev /dev/sdb1 errs: wr 0, rd 0, flush 0, corrupt
17, gen 0
[ 3169.841605] btrfs bad tree block start 0 29450240
[ 3169.841609] btrfs: bdev /dev/sdb1 errs: wr 0, rd 0, flush 0, corrupt
18, gen 0
the latest btrfs-restore from Chris' GIT (same result with Josefs restore
----------------------------------
[root@z2 btrfs-progs-chris]# ./btrfs-restore -i /dev/sdb1 /mnt
Root objectid is 5
Check tree block failed, want=29450240, have=0
Check tree block failed, want=29450240, have=0
Check tree block failed, want=29450240, have=0
Check tree block failed, want=29450240, have=0
Check tree block failed, want=29450240, have=0
read block failed check_tree_block
Error searching -5
btrfsck (latest from Chris) shows a lot of these mismatches and crashes
at the end :-(
-----------------------------------------------------------
[...]
backpointer mismatch on [152106881024 12288]
owner ref check failed [152106881024 12288]
ref mismatch on [152106893312 12288] extent item 1, found 0
Incorrect local backref count on 152106893312 root 5 owner 267 offset
34226176 found 0 wanted 1 back 0x57024e0
backpointer mismatch on [152106893312 12288]
owner ref check failed [152106893312 12288]
ref mismatch on [152106905600 12288] extent item 1, found 0
Incorrect local backref count on 152106905600 root 5 owner 267 offset
34623488 found 0 wanted 1 back 0x57025c0
backpointer mismatch on [152106905600 12288]
owner ref check failed [152106905600 12288]
ref mismatch on [152106917888 12288] extent item 1, found 0
Incorrect local backref count on 152106917888 root 5 owner 267 offset
34672640 found 0 wanted 1 back 0x57026a0
backpointer mismatch on [152106917888 12288]
owner ref check failed [152106917888 12288]
ref mismatch on [152106930176 16384] extent item 1, found 0
Incorrect local backref count on 152106930176 root 5 owner 267 offset
34734080 found 0 wanted 1 back 0x5702780
backpointer mismatch on [152106930176 16384]
owner ref check failed [152106930176 16384]
ref mismatch on [152106946560 24576] extent item 1, found 0
Incorrect local backref count on 152106946560 root 5 owner 267 offset
36159488 found 0 wanted 1 back 0x5702860
backpointer mismatch on [152106946560 24576]
owner ref check failed [152106946560 24576]
ref mismatch on [152106971136 28672] extent item 1, found 0
Incorrect local backref count on 152106971136 root 5 owner 267 offset
37212160 found 0 wanted 1 back 0x5702940
backpointer mismatch on [152106971136 28672]
owner ref check failed [152106971136 28672]
ref mismatch on [152106999808 12288] extent item 1, found 0
Incorrect local backref count on 152106999808 root 5 owner 267 offset
37679104 found 0 wanted 1 back 0x5702a20
backpointer mismatch on [152106999808 12288]
owner ref check failed [152106999808 12288]
ref mismatch on [152107012096 8192] extent item 1, found 0
Incorrect local backref count on 152107012096 root 5 owner 267 offset
37707776 found 0 wanted 1 back 0x5702b00
backpointer mismatch on [152107012096 8192]
owner ref check failed [152107012096 8192]
ref mismatch on [152107020288 36864] extent item 1, found 0
Incorrect local backref count on 152107020288 root 5 owner 267 offset
37777408 found 0 wanted 1 back 0x5702be0
backpointer mismatch on [152107020288 36864]
owner ref check failed [152107020288 36864]
ref mismatch on [152107057152 24576] extent item 1, found 0
Incorrect local backref count on 152107057152 root 5 owner 267 offset
38776832 found 0 wanted 1 back 0x5702cc0
backpointer mismatch on [152107057152 24576]
owner ref check failed [152107057152 24576]
ref mismatch on [152107081728 8192] extent item 1, found 0
Incorrect local backref count on 152107081728 root 5 owner 267 offset
39444480 found 0 wanted 1 back 0x5702da0
backpointer mismatch on [152107081728 8192]
owner ref check failed [152107081728 8192]
ref mismatch on [152107089920 16384] extent item 1, found 0
Incorrect local backref count on 152107089920 root 5 owner 267 offset
39817216 found 0 wanted 1 back 0x5702e80
backpointer mismatch on [152107089920 16384]
owner ref check failed [152107089920 16384]
ref mismatch on [152107126784 12288] extent item 1, found 0
Incorrect local backref count on 152107126784 root 5 owner 267 offset
41345024 found 0 wanted 1 back 0x5702f60
backpointer mismatch on [152107126784 12288]
owner ref check failed [152107126784 12288]
ref mismatch on [152107139072 4096] extent item 1, found 0
Incorrect local backref count on 152107139072 root 5 owner 267 offset
41631744 found 0 wanted 1 back 0x5706510
backpointer mismatch on [152107139072 4096]
owner ref check failed [152107139072 4096]
ref mismatch on [152107241472 49152] extent item 1, found 0
Incorrect local backref count on 152107241472 root 5 owner 267 offset
44765184 found 0 wanted 1 back 0x57065f0
backpointer mismatch on [152107241472 49152]
owner ref check failed [152107241472 49152]
Errors found in extent allocation tree
checking fs roots
Check tree block failed, want=29450240, have=0
Check tree block failed, want=29450240, have=0
Check tree block failed, want=29450240, have=0
Check tree block failed, want=29450240, have=0
Check tree block failed, want=29450240, have=0
read block failed check_tree_block
Speicherzugriffsfehler (Speicherabzug geschrieben)
find-root from Joseph:
-----------------------
[root@z2 btrfs-progs-josef]# ./find-root /dev/sdb1
Super think's the tree root is at 32030720, chunk root 20971520
Generation: 192331 Root bytenr: 29446144 Root objectid: 2
Generation: 192331 Root bytenr: 32464896 Root objectid: 4
Generation: 192331 Root bytenr: 29360128 Root objectid: 5
Generation: 192331 Root bytenr: 29581312 Root objectid: 7
Generation: 192331 Root bytenr: 29380608 Root objectid: 18446744073709551607
Well block 29437952 seems great, but generation doesn't match,
have=192331, want=192333
Generation: 192332 Root bytenr: 30793728 Root objectid: 2
Generation: 192332 Root bytenr: 31121408 Root objectid: 4
Generation: 192332 Root bytenr: 29360128 Root objectid: 5
Generation: 192332 Root bytenr: 29581312 Root objectid: 7
Generation: 192332 Root bytenr: 29380608 Root objectid: 18446744073709551607
Well block 30732288 seems great, but generation doesn't match,
have=192332, want=192333
Generation: 192333 Root bytenr: 32432128 Root objectid: 2
Generation: 192333 Root bytenr: 31121408 Root objectid: 4
Generation: 192333 Root bytenr: 29360128 Root objectid: 5
Generation: 192333 Root bytenr: 29581312 Root objectid: 7
Generation: 192333 Root bytenr: 29380608 Root objectid: 18446744073709551607
Found tree root at 32030720
debug-tree shows the same problematic block on the console, the
generated list is written up to the end without crash
-------------------------------------------
[root@z2 btrfs-progs-chris]# ./btrfs-debug-tree /dev/sdb1 >123
Check tree block failed, want=29450240, have=0
Check tree block failed, want=29450240, have=0
Check tree block failed, want=29450240, have=0
Check tree block failed, want=29450240, have=0
Check tree block failed, want=29450240, have=0
read block failed check_tree_block
failed to read 29450240 in tree 5
[...]
310797516/296M 100%
item 0 key (EXTENT_CSUM EXTENT_CSUM 156340977664) itemoff 563
itemsize 3432
extent csum item
leaf 75816960 items 2 free space 2081 generation 190286 owner 7
fs uuid 4d00f0e6-e9d7-42d9-8514-827d8f01f7d3
chunk uuid 7e64d936-3686-4e79-890e-aa9a090eb95d
item 0 key (EXTENT_CSUM EXTENT_CSUM 156344492032) itemoff 2643
itemsize 1352
extent csum item
item 1 key (EXTENT_CSUM EXTENT_CSUM 156345876480) itemoff 2131
itemsize 512
extent csum item
leaf 75796480 items 1 free space 178 generation 190286 owner 7
fs uuid 4d00f0e6-e9d7-42d9-8514-827d8f01f7d3
chunk uuid 7e64d936-3686-4e79-890e-aa9a090eb95d
item 0 key (EXTENT_CSUM EXTENT_CSUM 156346400768) itemoff 203
itemsize 3792
extent csum item
data reloc tree key (DATA_RELOC_TREE ROOT_ITEM 0)
leaf 29380608 items 2 free space 3773 generation 5 owner
18446744073709551607
fs uuid 4d00f0e6-e9d7-42d9-8514-827d8f01f7d3
chunk uuid 7e64d936-3686-4e79-890e-aa9a090eb95d
item 0 key (256 INODE_ITEM 0) itemoff 3835 itemsize 160
inode generation 4 transid 0 size 0 block group 0 mode
40555 links 1
item 1 key (256 INODE_REF 256) itemoff 3823 itemsize 12
inode ref index 0 namelen 2 name: ..
total bytes 160039960576
bytes used 103460102144
uuid 4d00f0e6-e9d7-42d9-8514-827d8f01f7d3
Btrfs Btrfs v0.19
Is there any hope for me?
best regards
Alfred
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: BTRFS filesystem is not mountable after crash
2012-08-20 21:42 BTRFS filesystem is not mountable after crash Alfred Zastrow
@ 2012-08-26 5:27 ` Alfred Zastrow
2012-08-26 6:17 ` Liu Bo
0 siblings, 1 reply; 6+ messages in thread
From: Alfred Zastrow @ 2012-08-26 5:27 UTC (permalink / raw)
To: linux-btrfs
Am 20.08.2012 23:42, schrieb Alfred Zastrow:
> Hi devs,
>
> I've a serious problem with my 160 gb SSD which is not mountable
> anymore. A backup for most of the date is there, but not for the latest
> ones. :-(
> The crash occurred during a download (system hangs totaly, hard reset)
> with a Fedora 3.5.2 linux kernel. The btrfs partition was working quite
> good for about one year.
>
> here is a try to attach the device and mount manually:
> -----------------------------------------------------
> [ 3123.582387] sd 1:0:0:0: Attached scsi generic sg2 type 0
> [ 3123.582833] sdb: sdb1
> [ 3123.583085] sd 1:0:0:0: [sdb] Attached SCSI disk
> [ 3169.789800] Btrfs loaded
> [ 3169.791156] device fsid 4d00f0e6-e9d7-42d9-8514-827d8f01f7d3 devid 1
> transid 192331 /dev/sdb1
> [ 3169.796334] btrfs: bdev /dev/sdb1 errs: wr 0, rd 0, flush 0, corrupt
> 16, gen 0
> [ 3169.840296] Btrfs detected SSD devices, enabling SSD mode
> [ 3169.841541] btrfs bad tree block start 0 29450240
> [ 3169.841545] btrfs: bdev /dev/sdb1 errs: wr 0, rd 0, flush 0, corrupt
> 17, gen 0
> [ 3169.841605] btrfs bad tree block start 0 29450240
> [ 3169.841609] btrfs: bdev /dev/sdb1 errs: wr 0, rd 0, flush 0, corrupt
> 18, gen 0
> [ 3123.582387] sd 1:0:0:0: Attached scsi generic sg2 type 0
> [ 3123.582833] sdb: sdb1
> [ 3123.583085] sd 1:0:0:0: [sdb] Attached SCSI disk
> [ 3169.789800] Btrfs loaded
> [ 3169.791156] device fsid 4d00f0e6-e9d7-42d9-8514-827d8f01f7d3 devid 1
> transid 192331 /dev/sdb1
> [ 3169.796334] btrfs: bdev /dev/sdb1 errs: wr 0, rd 0, flush 0, corrupt
> 16, gen 0
> [ 3169.840296] Btrfs detected SSD devices, enabling SSD mode
> [ 3169.841541] btrfs bad tree block start 0 29450240
> [ 3169.841545] btrfs: bdev /dev/sdb1 errs: wr 0, rd 0, flush 0, corrupt
> 17, gen 0
> [ 3169.841605] btrfs bad tree block start 0 29450240
> [ 3169.841609] btrfs: bdev /dev/sdb1 errs: wr 0, rd 0, flush 0, corrupt
> 18, gen 0
>
>
> the latest btrfs-restore from Chris' GIT (same result with Josefs restore
> ----------------------------------
> [root@z2 btrfs-progs-chris]# ./btrfs-restore -i /dev/sdb1 /mnt
> Root objectid is 5
> Check tree block failed, want=29450240, have=0
> Check tree block failed, want=29450240, have=0
> Check tree block failed, want=29450240, have=0
> Check tree block failed, want=29450240, have=0
> Check tree block failed, want=29450240, have=0
> read block failed check_tree_block
> Error searching -5
>
>
>
>
> btrfsck (latest from Chris) shows a lot of these mismatches and crashes
> at the end :-(
> -----------------------------------------------------------
> [...]
> backpointer mismatch on [152106881024 12288]
> owner ref check failed [152106881024 12288]
> ref mismatch on [152106893312 12288] extent item 1, found 0
> Incorrect local backref count on 152106893312 root 5 owner 267 offset
> 34226176 found 0 wanted 1 back 0x57024e0
> backpointer mismatch on [152106893312 12288]
> owner ref check failed [152106893312 12288]
> ref mismatch on [152106905600 12288] extent item 1, found 0
> Incorrect local backref count on 152106905600 root 5 owner 267 offset
> 34623488 found 0 wanted 1 back 0x57025c0
> backpointer mismatch on [152106905600 12288]
> owner ref check failed [152106905600 12288]
> ref mismatch on [152106917888 12288] extent item 1, found 0
> Incorrect local backref count on 152106917888 root 5 owner 267 offset
> 34672640 found 0 wanted 1 back 0x57026a0
> backpointer mismatch on [152106917888 12288]
> owner ref check failed [152106917888 12288]
> ref mismatch on [152106930176 16384] extent item 1, found 0
> Incorrect local backref count on 152106930176 root 5 owner 267 offset
> 34734080 found 0 wanted 1 back 0x5702780
> backpointer mismatch on [152106930176 16384]
> owner ref check failed [152106930176 16384]
> ref mismatch on [152106946560 24576] extent item 1, found 0
> Incorrect local backref count on 152106946560 root 5 owner 267 offset
> 36159488 found 0 wanted 1 back 0x5702860
> backpointer mismatch on [152106946560 24576]
> owner ref check failed [152106946560 24576]
> ref mismatch on [152106971136 28672] extent item 1, found 0
> Incorrect local backref count on 152106971136 root 5 owner 267 offset
> 37212160 found 0 wanted 1 back 0x5702940
> backpointer mismatch on [152106971136 28672]
> owner ref check failed [152106971136 28672]
> ref mismatch on [152106999808 12288] extent item 1, found 0
> Incorrect local backref count on 152106999808 root 5 owner 267 offset
> 37679104 found 0 wanted 1 back 0x5702a20
> backpointer mismatch on [152106999808 12288]
> owner ref check failed [152106999808 12288]
> ref mismatch on [152107012096 8192] extent item 1, found 0
> Incorrect local backref count on 152107012096 root 5 owner 267 offset
> 37707776 found 0 wanted 1 back 0x5702b00
> backpointer mismatch on [152107012096 8192]
> owner ref check failed [152107012096 8192]
> ref mismatch on [152107020288 36864] extent item 1, found 0
> Incorrect local backref count on 152107020288 root 5 owner 267 offset
> 37777408 found 0 wanted 1 back 0x5702be0
> backpointer mismatch on [152107020288 36864]
> owner ref check failed [152107020288 36864]
> ref mismatch on [152107057152 24576] extent item 1, found 0
> Incorrect local backref count on 152107057152 root 5 owner 267 offset
> 38776832 found 0 wanted 1 back 0x5702cc0
> backpointer mismatch on [152107057152 24576]
> owner ref check failed [152107057152 24576]
> ref mismatch on [152107081728 8192] extent item 1, found 0
> Incorrect local backref count on 152107081728 root 5 owner 267 offset
> 39444480 found 0 wanted 1 back 0x5702da0
> backpointer mismatch on [152107081728 8192]
> owner ref check failed [152107081728 8192]
> ref mismatch on [152107089920 16384] extent item 1, found 0
> Incorrect local backref count on 152107089920 root 5 owner 267 offset
> 39817216 found 0 wanted 1 back 0x5702e80
> backpointer mismatch on [152107089920 16384]
> owner ref check failed [152107089920 16384]
> ref mismatch on [152107126784 12288] extent item 1, found 0
> Incorrect local backref count on 152107126784 root 5 owner 267 offset
> 41345024 found 0 wanted 1 back 0x5702f60
> backpointer mismatch on [152107126784 12288]
> owner ref check failed [152107126784 12288]
> ref mismatch on [152107139072 4096] extent item 1, found 0
> Incorrect local backref count on 152107139072 root 5 owner 267 offset
> 41631744 found 0 wanted 1 back 0x5706510
> backpointer mismatch on [152107139072 4096]
> owner ref check failed [152107139072 4096]
> ref mismatch on [152107241472 49152] extent item 1, found 0
> Incorrect local backref count on 152107241472 root 5 owner 267 offset
> 44765184 found 0 wanted 1 back 0x57065f0
> backpointer mismatch on [152107241472 49152]
> owner ref check failed [152107241472 49152]
> Errors found in extent allocation tree
> checking fs roots
> Check tree block failed, want=29450240, have=0
> Check tree block failed, want=29450240, have=0
> Check tree block failed, want=29450240, have=0
> Check tree block failed, want=29450240, have=0
> Check tree block failed, want=29450240, have=0
> read block failed check_tree_block
> Speicherzugriffsfehler (Speicherabzug geschrieben)
>
>
> find-root from Joseph:
> -----------------------
> [root@z2 btrfs-progs-josef]# ./find-root /dev/sdb1
> Super think's the tree root is at 32030720, chunk root 20971520
> Generation: 192331 Root bytenr: 29446144 Root objectid: 2
> Generation: 192331 Root bytenr: 32464896 Root objectid: 4
> Generation: 192331 Root bytenr: 29360128 Root objectid: 5
> Generation: 192331 Root bytenr: 29581312 Root objectid: 7
> Generation: 192331 Root bytenr: 29380608 Root objectid:
> 18446744073709551607
> Well block 29437952 seems great, but generation doesn't match,
> have=192331, want=192333
> Generation: 192332 Root bytenr: 30793728 Root objectid: 2
> Generation: 192332 Root bytenr: 31121408 Root objectid: 4
> Generation: 192332 Root bytenr: 29360128 Root objectid: 5
> Generation: 192332 Root bytenr: 29581312 Root objectid: 7
> Generation: 192332 Root bytenr: 29380608 Root objectid:
> 18446744073709551607
> Well block 30732288 seems great, but generation doesn't match,
> have=192332, want=192333
> Generation: 192333 Root bytenr: 32432128 Root objectid: 2
> Generation: 192333 Root bytenr: 31121408 Root objectid: 4
> Generation: 192333 Root bytenr: 29360128 Root objectid: 5
> Generation: 192333 Root bytenr: 29581312 Root objectid: 7
> Generation: 192333 Root bytenr: 29380608 Root objectid:
> 18446744073709551607
> Found tree root at 32030720
>
>
> debug-tree shows the same problematic block on the console, the
> generated list is written up to the end without crash
> -------------------------------------------
> [root@z2 btrfs-progs-chris]# ./btrfs-debug-tree /dev/sdb1 >123
> Check tree block failed, want=29450240, have=0
> Check tree block failed, want=29450240, have=0
> Check tree block failed, want=29450240, have=0
> Check tree block failed, want=29450240, have=0
> Check tree block failed, want=29450240, have=0
> read block failed check_tree_block
> failed to read 29450240 in tree 5
>
>
>
>
> [...]
>
> 310797516/296M 100%
> item 0 key (EXTENT_CSUM EXTENT_CSUM 156340977664) itemoff 563
> itemsize 3432
> extent csum item
> leaf 75816960 items 2 free space 2081 generation 190286 owner 7
> fs uuid 4d00f0e6-e9d7-42d9-8514-827d8f01f7d3
> chunk uuid 7e64d936-3686-4e79-890e-aa9a090eb95d
> item 0 key (EXTENT_CSUM EXTENT_CSUM 156344492032) itemoff 2643
> itemsize 1352
> extent csum item
> item 1 key (EXTENT_CSUM EXTENT_CSUM 156345876480) itemoff 2131
> itemsize 512
> extent csum item
> leaf 75796480 items 1 free space 178 generation 190286 owner 7
> fs uuid 4d00f0e6-e9d7-42d9-8514-827d8f01f7d3
> chunk uuid 7e64d936-3686-4e79-890e-aa9a090eb95d
> item 0 key (EXTENT_CSUM EXTENT_CSUM 156346400768) itemoff 203
> itemsize 3792
> extent csum item
> data reloc tree key (DATA_RELOC_TREE ROOT_ITEM 0)
> leaf 29380608 items 2 free space 3773 generation 5 owner
> 18446744073709551607
> fs uuid 4d00f0e6-e9d7-42d9-8514-827d8f01f7d3
> chunk uuid 7e64d936-3686-4e79-890e-aa9a090eb95d
> item 0 key (256 INODE_ITEM 0) itemoff 3835 itemsize 160
> inode generation 4 transid 0 size 0 block group 0 mode
> 40555 links 1
> item 1 key (256 INODE_REF 256) itemoff 3823 itemsize 12
> inode ref index 0 namelen 2 name: ..
> total bytes 160039960576
> bytes used 103460102144
> uuid 4d00f0e6-e9d7-42d9-8514-827d8f01f7d3
> Btrfs Btrfs v0.19
>
>
>
> Is there any hope for me?
>
> best regards
> Alfred
>
> --
> 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
>
Hello,
has realy nobody a hint for me?
br
Alfred
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: BTRFS filesystem is not mountable after crash
2012-08-26 5:27 ` Alfred Zastrow
@ 2012-08-26 6:17 ` Liu Bo
2012-10-13 17:51 ` Alfred Zastrow
0 siblings, 1 reply; 6+ messages in thread
From: Liu Bo @ 2012-08-26 6:17 UTC (permalink / raw)
To: Alfred Zastrow; +Cc: linux-btrfs
On 08/26/2012 01:27 PM, Alfred Zastrow wrote:
>>
>
>
> Hello,
>
> has realy nobody a hint for me?
>
Is compiling chris's latest for-linus helpful?
git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git
thanks,
liubo
> br
> Alfred
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: BTRFS filesystem is not mountable after crash
2012-08-26 6:17 ` Liu Bo
@ 2012-10-13 17:51 ` Alfred Zastrow
2012-10-13 22:56 ` cwillu
0 siblings, 1 reply; 6+ messages in thread
From: Alfred Zastrow @ 2012-10-13 17:51 UTC (permalink / raw)
To: Liu Bo; +Cc: linux-btrfs
Am 26.08.2012 08:17, schrieb Liu Bo:
> On 08/26/2012 01:27 PM, Alfred Zastrow wrote:
>
>
> Hello,
>
> has realy nobody a hint for me?
>
> Is compiling chris's latest for-linus helpful?
>
> git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git
>
> thanks,
> liubo
Hi dev's
I was not able to install chris's latest for-linus under F17, but I
tried with the latest 3.6.1-Kernel with was recently released.
Same shit.. :-(
[root@z2 alfred]# mount /dev/sdb1 /mnt -o recovery,ro
mount: mount /dev/sdb1 on /mnt failed: Veraltete NFS-Dateizugriffsnummer
[root@z2 alfred]# dmesg
[...]
[41005.694357] device fsid 4d00f0e6-e9d7-42d9-8514-827d8f01f7d3 devid 1
transid 192347 /dev/sdb1
[41005.696173] btrfs: enabling auto recovery
[41005.698539] btrfs: mismatching generation and generation_v2 found in
root item. This root was probably mounted with an older kernel.
Resetting all new fields.
[41005.698732] btrfs: mismatching generation and generation_v2 found in
root item. This root was probably mounted with an older kernel.
Resetting all new fields.
[41005.699307] btrfs: bdev /dev/sdb1 errs: wr 0, rd 0, flush 0, corrupt
20, gen 0
[41005.741978] Btrfs detected SSD devices, enabling SSD mode
[41005.742459] btrfs bad tree block start 0 29450240
[41005.742514] btrfs bad tree block start 0 29450240
All the other tools (btrfs-restore, btrfsck, restore from Josef) gave me
the same results as I have written in my 1st mail.
Sadly I have realized, that some of my vacation pictures are still on
the SSD - without backup... :-(
Best regards
Alfred
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: BTRFS filesystem is not mountable after crash
2012-10-13 17:51 ` Alfred Zastrow
@ 2012-10-13 22:56 ` cwillu
2012-10-14 15:48 ` Alfred Zastrow
0 siblings, 1 reply; 6+ messages in thread
From: cwillu @ 2012-10-13 22:56 UTC (permalink / raw)
To: Alfred Zastrow; +Cc: Liu Bo, linux-btrfs
On Sat, Oct 13, 2012 at 11:51 AM, Alfred Zastrow <ml@zastrow4u.de> wrote:
> Am 26.08.2012 08:17, schrieb Liu Bo:
>
>> On 08/26/2012 01:27 PM, Alfred Zastrow wrote:
>>
>>
>> Hello,
>>
>> has realy nobody a hint for me?
>>
>> Is compiling chris's latest for-linus helpful?
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git
>>
>> thanks,
>> liubo
>
>
> Hi dev's
>
> I was not able to install chris's latest for-linus under F17, but I tried
> with the latest 3.6.1-Kernel with was recently released.
> Same shit.. :-(
Chris's for-linus is currently all the btrfs changes that will be
going into 3.7. 3.6.1 won't likely have any of them.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: BTRFS filesystem is not mountable after crash
2012-10-13 22:56 ` cwillu
@ 2012-10-14 15:48 ` Alfred Zastrow
0 siblings, 0 replies; 6+ messages in thread
From: Alfred Zastrow @ 2012-10-14 15:48 UTC (permalink / raw)
To: cwillu; +Cc: Liu Bo, linux-btrfs
Am 14.10.2012 00:56, schrieb cwillu:
> Chris's for-linus is currently all the btrfs changes that will be
> going into 3.7. 3.6.1 won't likely have any of them.
Hi,
same thing, no success :-(
I've checked out this tree:
git clone
git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git
The version show me "3.6.0+"
I took my original Fedora Kernel-config to compile (btrfs as module)
[root@z2 alfred]# modinfo btrfs
filename: /lib/modules/3.6.0+/kernel/fs/btrfs/btrfs.ko
license: GPL
alias: devname:btrfs-control
alias: char-major-10-234
depends: libcrc32c,zlib_deflate
intree: Y
vermagic: 3.6.0+ SMP mod_unload
Result:
[ 281.637120] Btrfs loaded
[ 305.059449] device fsid 4d00f0e6-e9d7-42d9-8514-827d8f01f7d3 devid 1
transid 192347 /dev/sdc1
[ 305.060341] btrfs: enabling auto recovery
[ 305.062283] btrfs: mismatching generation and generation_v2 found in
root item. This root was probably mounted with an older kernel.
Resetting all new fields.
[ 305.062496] btrfs: mismatching generation and generation_v2 found in
root item. This root was probably mounted with an older kernel.
Resetting all new fields.
[ 305.063114] btrfs: bdev /dev/sdc1 errs: wr 0, rd 0, flush 0, corrupt
20, gen 0
[ 305.107040] Btrfs detected SSD devices, enabling SSD mode
[ 305.107497] btrfs bad tree block start 0 29450240
[ 305.107557] btrfs bad tree block start 0 29450240
Do you have an other hint for me?
best regards
Alfred
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2012-10-14 15:48 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-08-20 21:42 BTRFS filesystem is not mountable after crash Alfred Zastrow
2012-08-26 5:27 ` Alfred Zastrow
2012-08-26 6:17 ` Liu Bo
2012-10-13 17:51 ` Alfred Zastrow
2012-10-13 22:56 ` cwillu
2012-10-14 15:48 ` Alfred Zastrow
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).