* fsck.reiser4 does not fix corruption
@ 2010-10-01 4:32 Volker Armin Hemmann
2010-10-04 15:12 ` Edward Shishkin
0 siblings, 1 reply; 2+ messages in thread
From: Volker Armin Hemmann @ 2010-10-01 4:32 UTC (permalink / raw)
To: reiserfs-devel
Hi,
I used 2.6.35 and after some BUG messages in dmesg appeared, I went back to
2.6.34. The damage was done, I did not want to make it worse.
fsck found errors and recommended running it with --build.fs
I did.
Afterwards I got this:
299.844055] reiser4[mlnet(2712)]: do_readpage_ctail
(fs/reiser4/plugin/item/ctail.c:677)[edward-1563]:
[ 299.844060] WARNING: orphan unprepped cluster 0 (inode 11052572). Fsck?
[ 299.844126] reiser4[mlnet(2712)]: do_readpage_ctail
(fs/reiser4/plugin/item/ctail.c:677)[edward-1563]:
[ 299.844130] WARNING: orphan unprepped cluster 0 (inode 11052572). Fsck?
[ 328.076637] reiser4[file(2740)]: do_readpage_ctail
(fs/reiser4/plugin/item/ctail.c:677)[edward-1563]:
[ 328.076641] WARNING: orphan unprepped cluster 0 (inode 11052572). Fsck?
[ 328.077674] reiser4[less(2733)]: do_readpage_ctail
(fs/reiser4/plugin/item/ctail.c:677)[edward-1563]:
[ 328.077679] WARNING: orphan unprepped cluster 0 (inode 11052572). Fsck?
[ 328.077806] reiser4[less(2733)]: do_readpage_ctail
(fs/reiser4/plugin/item/ctail.c:677)[edward-1563]:
[ 328.077810] WARNING: orphan unprepped cluster 0 (inode 11052572). Fsck?
I run fsck again:
fsck.reiser4 --fix /dev/md3
*******************************************************************
This is an EXPERIMENTAL version of fsck.reiser4. Read README first.
*******************************************************************
Fscking the /dev/md3 block device.
Will fix minor corruptions of the Reiser4 SuperBlock.
Will fix minor corruptions of the Reiser4 FileSystem.
Continue?
(Yes/No): Yes
***** fsck.reiser4 started at Wed Sep 29 21:32:22 2010
Reiser4 fs was detected on /dev/md3.
Master super block (16):
magic: ReIsEr4
blksize: 4096
format: 0x0 (format40)
uuid: 740b0c92-ca44-4e73-8b0f-9e592947f177
label: <none>
Format super block (17):
plugin: format40
description: Disk-format plugin.
version: 0
magic: ReIsEr40FoRmAt
mkfs id: 0x40eea310
flushes: 0
blocks: 210953472
free blocks: 63198340
root block: 203394053
tail policy: 0x2 (smart)
next oid: 0xa8a637
file count: 1460992
tree height: 6
key policy: LARGE
CHECKING THE STORAGE TREE
Read nodes 38125202
Nodes left in the tree 38125202
Leaves of them 37668676, Twigs of them 449202
Time interval: Wed Sep 29 21:33:07 2010 - Wed Sep 29 22:41:05 2010
CHECKING EXTENT REGIONS.
Read twigs 449202
Time interval: Wed Sep 29 22:41:05 2010 - Wed Sep 29 23:05:17 2010
CHECKING THE SEMANTIC TREE
FSCK: ccreg40_repair.c: 66: ccreg40_check_item: Found unprepped disk cluster
FSCK: ccreg40_repair.c: 98: ccreg40_check_item: (file
[9037f7:6b646577616c6c:9e52e9] (ccreg40), node [107285699], item [0]).
FSCK: ccreg40_repair.c: 66: ccreg40_check_item: Found unprepped disk cluster
FSCK: ccreg40_repair.c: 98: ccreg40_check_item: (file
[9041b5:626974746f7272:a8a629] (ccreg40), node [107356238], item [1]).
FSCK: ccreg40_repair.c: 66: ccreg40_check_item: Found unprepped disk cluster
FSCK: ccreg40_repair.c: 98: ccreg40_check_item: (file
[9041b5:64697265637463:a8a62e] (ccreg40), node [107356238], item [3]).
FSCK: ccreg40_repair.c: 66: ccreg40_check_item: Found unprepped disk cluster
FSCK: ccreg40_repair.c: 98: ccreg40_check_item: (file
[9041b5:646f6e6b65792e:a8a628] (ccreg40), node [107356256], item [1]).
FSCK: ccreg40_repair.c: 66: ccreg40_check_item: Found unprepped disk cluster
FSCK: ccreg40_repair.c: 98: ccreg40_check_item: (file
[9041b5:646f776e6c6f61:a8a61c] (ccreg40), node [107366117], item [1]).
FSCK: ccreg40_repair.c: 66: ccreg40_check_item: Found unprepped disk cluster
FSCK: ccreg40_repair.c: 98: ccreg40_check_item: (file
[9041b5:66617374747261:a8a62b] (ccreg40), node [107366121], item [1]).
FSCK: ccreg40_repair.c: 66: ccreg40_check_item: Found unprepped disk cluster
FSCK: ccreg40_repair.c: 98: ccreg40_check_item: (file
[9041b5:66696c6554502e:a8a62a] (ccreg40), node [107366121], item [3]).
FSCK: ccreg40_repair.c: 66: ccreg40_check_item: Found unprepped disk cluster
FSCK: ccreg40_repair.c: 98: ccreg40_check_item: (file
[9041b5:66696c65732e69:a8a622] (ccreg40), node [107826314], item [1]).
FSCK: ccreg40_repair.c: 66: ccreg40_check_item: Found unprepped disk cluster
FSCK: ccreg40_repair.c: 98: ccreg40_check_item: (file
[9041b5:667269656e6473:a8a624] (ccreg40), node [107826314], item [6]).
FSCK: ccreg40_repair.c: 66: ccreg40_check_item: Found unprepped disk cluster
FSCK: ccreg40_repair.c: 98: ccreg40_check_item: (file
[9041b5:676e7574656c6c:a8a62d] (ccreg40), node [107826315], item [3]).
FSCK: ccreg40_repair.c: 66: ccreg40_check_item: Found unprepped disk cluster
FSCK: ccreg40_repair.c: 98: ccreg40_check_item: (file
[9041b5:676e7574656c6c:a8a62c] (ccreg40), node [107826315], item [2]).
FSCK: ccreg40_repair.c: 66: ccreg40_check_item: Found unprepped disk cluster
FSCK: ccreg40_repair.c: 98: ccreg40_check_item: (file
[9041b5:6f6e6c696e6573:904276] (ccreg40), node [107820544], item [2]).
FSCK: ccreg40_repair.c: 66: ccreg40_check_item: Found unprepped disk cluster
FSCK: ccreg40_repair.c: 98: ccreg40_check_item: (file
[9041b5:73656172636865:a8a623] (ccreg40), node [107820544], item [4]).
FSCK: ccreg40_repair.c: 66: ccreg40_check_item: Found unprepped disk cluster
FSCK: ccreg40_repair.c: 98: ccreg40_check_item: (file
[9041b5:73657276657273:a8a625] (ccreg40), node [107820544], item [6]).
FSCK: obj40_repair.c: 146: obj40_check_bytes_report: Node (107356236), item
(18), [9041b5:7368617265645f:a8a626] (stat40): wrong bytes (1331200), Fixed to
(0).
FSCK: ccreg40_repair.c: 66: ccreg40_check_item: Found unprepped disk cluster
FSCK: ccreg40_repair.c: 98: ccreg40_check_item: (file
[9041b5:17368617265645f:a8a61e] (ccreg40), node [20383895], item [1]).
FSCK: ccreg40_repair.c: 66: ccreg40_check_item: Found unprepped disk cluster
FSCK: ccreg40_repair.c: 98: ccreg40_check_item: (file
[9041b5:73746174697374:a8a627] (ccreg40), node [107890282], item [1]).
FSCK: ccreg40_repair.c: 66: ccreg40_check_item: Found unprepped disk cluster
FSCK: ccreg40_repair.c: 98: ccreg40_check_item: (file
[9041b5:73746174732e69:a8a61f] (ccreg40), node [107890282], item [3]).
FSCK: ccreg40_repair.c: 66: ccreg40_check_item: Found unprepped disk cluster
FSCK: ccreg40_repair.c: 98: ccreg40_check_item: (file
[9041b5:73746174735f62:a8a621] (ccreg40), node [107890282], item [5]).
FSCK: ccreg40_repair.c: 66: ccreg40_check_item: Found unprepped disk cluster
FSCK: ccreg40_repair.c: 98: ccreg40_check_item: (file
[9041b5:73746174735f6d:a8a620] (ccreg40), node [107890282], item [7]).
FSCK: ccreg40_repair.c: 66: ccreg40_check_item: Found unprepped disk cluster
FSCK: ccreg40_repair.c: 98: ccreg40_check_item: (file
[9041b5:75736572732e69:a8a61d] (ccreg40), node [107833440], item [1]).
FSCK: obj40_repair.c: 146: obj40_check_bytes_report: Node (187761743), item
(31), [8aa6b9:35333536443444:8e9fa0] (stat40): wrong bytes (172032), Fixed to
(0).
FSCK: obj40_repair.c: 373: obj40_stat_lw_check: Node (187761743), item (31),
[8aa6b9:35333536443444:8e9fa0] (stat40): wrong size (171143), Fixed to (0).
FSCK: obj40_repair.c: 146: obj40_check_bytes_report: Node (187761743), item
(32), [8aa6b9:35334132323236:8fdbb5] (stat40): wrong bytes (327680), Fixed to
(0).
FSCK: obj40_repair.c: 373: obj40_stat_lw_check: Node (187761743), item (32),
[8aa6b9:35334132323236:8fdbb5] (stat40): wrong size (325122), Fixed to (0).
FSCK: obj40_repair.c: 146: obj40_check_bytes_report: Node (187761743), item
(33), [8aa6b9:35334339303934:8ec2e7] (stat40): wrong bytes (8355840), Fixed to
(0).
FSCK: obj40_repair.c: 373: obj40_stat_lw_check: Node (187761743), item (33),
[8aa6b9:35334339303934:8ec2e7] (stat40): wrong size (8352691), Fixed to (0).
FSCK: obj40_repair.c: 146: obj40_check_bytes_report: Node (187761743), item
(34), [8aa6b9:35334346423332:8d3687] (stat40): wrong bytes (413696), Fixed to
(0).
FSCK: obj40_repair.c: 373: obj40_stat_lw_check: Node (187761743), item (34),
[8aa6b9:35334346423332:8d3687] (stat40): wrong size (412494), Fixed to (0).
FSCK: obj40_repair.c: 146: obj40_check_bytes_report: Node (187761743), item
(38), [8aa6b9:35334530433135:8e9fa1] (stat40): wrong bytes (626688), Fixed to
(0).
FSCK: obj40_repair.c: 373: obj40_stat_lw_check: Node (187761743), item (38),
[8aa6b9:35334530433135:8e9fa1] (stat40): wrong size (623467), Fixed to (0).
FSCK: obj40_repair.c: 146: obj40_check_bytes_report: Node (187761743), item
(39), [8aa6b9:35334638433931:8db91d] (stat40): wrong bytes (2056192), Fixed to
(0).
FSCK: obj40_repair.c: 373: obj40_stat_lw_check: Node (187761743), item (39),
[8aa6b9:35334638433931:8db91d] (stat40): wrong size (2053519), Fixed to (0).
FSCK: ccreg40_repair.c: 73: ccreg40_check_item: Found item with wrong cluster
shift 0, should be 16
FSCK: ccreg40_repair.c: 98: ccreg40_check_item: (file
[8aa6b9:35343035323043:8f4769] (ccreg40), node [751678], item [0]).
FSCK: ccreg40_repair.c: 187: ccreg40_check_cluster: The file
[6158d:16f70656e535553:4e2cca] (ccreg40): the cluster at [363397120] offset
65536 bytes long
is corrupted. Removed.
Found 1469098 objects (some could be encountered more then once).
Time interval: Wed Sep 29 23:05:17 2010 - Thu Sep 30 00:12:56 2010
FSCK: repair.c: 550: repair_sem_fini: On-disk used block bitmap and really used
block bitmap differ.
***** fsck.reiser4 finished at Thu Sep 30 00:12:56 2010
Closing fs...done
23 fatal corruptions were detected in FileSystem. Run with --build-fs option
to fix them.
energy ~ # fsck.reiser4 --build-fs /dev/md3
*******************************************************************
This is an EXPERIMENTAL version of fsck.reiser4. Read README first.
*******************************************************************
Fscking the /dev/md3 block device.
Will check the consistency of the Reiser4 SuperBlock.
Will build the Reiser4 FileSystem.
Continue?
(Yes/No): Yes
***** fsck.reiser4 started at Thu Sep 30 06:37:11 2010
Reiser4 fs was detected on /dev/md3.
Master super block (16):
magic: ReIsEr4
blksize: 4096
format: 0x0 (format40)
uuid: 740b0c92-ca44-4e73-8b0f-9e592947f177
label: <none>
Format super block (17):
plugin: format40
description: Disk-format plugin.
version: 0
magic: ReIsEr40FoRmAt
mkfs id: 0x40eea310
flushes: 0
blocks: 210953472
free blocks: 63198340
root block: 203394053
tail policy: 0x2 (smart)
next oid: 0xa8a637
file count: 1460992
tree height: 6
key policy: LARGE
CHECKING THE STORAGE TREE
Read nodes 38125202
Nodes left in the tree 38125202
Leaves of them 37668676, Twigs of them 449202
Time interval: Thu Sep 30 06:38:01 2010 - Thu Sep 30 07:37:03 2010
CHECKING EXTENT REGIONS.
Read twigs 449202
Time interval: Thu Sep 30 07:37:03 2010 - Thu Sep 30 08:01:21 2010
LOOKING FOR UNCONNECTED NODES
FSCK: node.c: 108: repair_node_items_check: Node (189713135), items (44) and
(45): Wrong order of keys.
Read nodes 1
Good nodes 0
Leaves of them 0, Twigs of them 0
Time interval: Thu Sep 30 08:01:26 2010 - Thu Sep 30 08:01:26 2010
***** fsck.reiser4 finished at Thu Sep 30 08:01:26 2010
Closing fs...done
FS is consistent.
and:
[75577.618768] reiser4: md3: found disk format 4.0.0.
[75664.731984] reiser4[cat(1669)]: do_readpage_ctail
(fs/reiser4/plugin/item/ctail.c:677)[edward-1563]:
[75664.731988] WARNING: orphan unprepped cluster 0 (inode 11052572). Fsck?
[75664.732040] reiser4[cat(1669)]: do_readpage_ctail
(fs/reiser4/plugin/item/ctail.c:677)[edward-1563]:
[75664.732044] WARNING: orphan unprepped cluster 0 (inode 11052572). Fsck?
and a third time:
umount /mnt/data
energy ~ # fsck.reiser4 --build-fs /dev/md3
*******************************************************************
This is an EXPERIMENTAL version of fsck.reiser4. Read README first.
*******************************************************************
Fscking the /dev/md3 block device.
Will check the consistency of the Reiser4 SuperBlock.
Will build the Reiser4 FileSystem.
Continue?
(Yes/No): Yes
***** fsck.reiser4 started at Thu Sep 30 18:46:11 2010
Reiser4 fs was detected on /dev/md3.
Master super block (16):
magic: ReIsEr4
blksize: 4096
format: 0x0 (format40)
uuid: 740b0c92-ca44-4e73-8b0f-9e592947f177
label: <none>
Format super block (17):
plugin: format40
description: Disk-format plugin.
version: 0
magic: ReIsEr40FoRmAt
mkfs id: 0x40eea310
flushes: 0
blocks: 210953472
free blocks: 63198340
root block: 203394053
tail policy: 0x2 (smart)
next oid: 0xa8a637
file count: 1460992
tree height: 6
key policy: LARGE
CHECKING THE STORAGE TREE
Read nodes 38125202
Nodes left in the tree 38125202
Leaves of them 37668676, Twigs of them 449202
Time interval: Thu Sep 30 18:46:57 2010 - Thu Sep 30 19:46:14 2010
CHECKING EXTENT REGIONS.
Read twigs 449202
Time interval: Thu Sep 30 19:46:14 2010 - Thu Sep 30 20:11:28 2010
LOOKING FOR UNCONNECTED NODES
FSCK: node.c: 108: repair_node_items_check: Node (189713135), items (44) and
(45): Wrong order of keys.
Read nodes 1
Good nodes 0
Leaves of them 0, Twigs of them 0
Time interval: Thu Sep 30 20:11:34 2010 - Thu Sep 30 20:11:34 2010
***** fsck.reiser4 finished at Thu Sep 30 20:11:34 2010
Closing fs...done
FS is consistent.
energy ~ # mount /mnt/data
82392.412972] reiser4: md3: found disk format 4.0.0.
[82891.509317] reiser4[cat(22737)]: do_readpage_ctail
(fs/reiser4/plugin/item/ctail.c:677)[edward-1563]:
[82891.509321] WARNING: orphan unprepped cluster 0 (inode 11052572). Fsck?
[82891.509382] reiser4[cat(22737)]: do_readpage_ctail
(fs/reiser4/plugin/item/ctail.c:677)[edward-1563]:
[82891.509386] WARNING: orphan unprepped cluster 0 (inode 11052572). Fsck?
reiser4progs 1.0.7 with a build patch for gcc 4.4 + the patch from here:
http://marc.info/?l=reiserfs-devel&m=127504471326353&w=2
md3 is a raid5 of 3 disks, which behaved normally until the 2.6.35 excercise.
Glück Auf,
Volker
--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" 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] 2+ messages in thread
* Re: fsck.reiser4 does not fix corruption
2010-10-01 4:32 fsck.reiser4 does not fix corruption Volker Armin Hemmann
@ 2010-10-04 15:12 ` Edward Shishkin
0 siblings, 0 replies; 2+ messages in thread
From: Edward Shishkin @ 2010-10-04 15:12 UTC (permalink / raw)
To: Volker Armin Hemmann; +Cc: reiserfs-devel
Volker Armin Hemmann wrote:
[...]
> 23 fatal corruptions were detected in FileSystem. Run with --build-fs option
> to fix them.
>
> energy ~ # fsck.reiser4 --build-fs /dev/md3
> *******************************************************************
> This is an EXPERIMENTAL version of fsck.reiser4. Read README first.
> *******************************************************************
>
> Fscking the /dev/md3 block device.
> Will check the consistency of the Reiser4 SuperBlock.
> Will build the Reiser4 FileSystem.
> Continue?
> (Yes/No): Yes
> ***** fsck.reiser4 started at Thu Sep 30 06:37:11 2010
> Reiser4 fs was detected on /dev/md3.
> Master super block (16):
> magic: ReIsEr4
> blksize: 4096
> format: 0x0 (format40)
> uuid: 740b0c92-ca44-4e73-8b0f-9e592947f177
> label: <none>
>
> Format super block (17):
> plugin: format40
> description: Disk-format plugin.
> version: 0
> magic: ReIsEr40FoRmAt
> mkfs id: 0x40eea310
> flushes: 0
> blocks: 210953472
> free blocks: 63198340
> root block: 203394053
> tail policy: 0x2 (smart)
> next oid: 0xa8a637
> file count: 1460992
> tree height: 6
> key policy: LARGE
>
>
> CHECKING THE STORAGE TREE
> Read nodes 38125202
> Nodes left in the tree 38125202
> Leaves of them 37668676, Twigs of them 449202
> Time interval: Thu Sep 30 06:38:01 2010 - Thu Sep 30 07:37:03 2010
> CHECKING EXTENT REGIONS.
> Read twigs 449202
> Time interval: Thu Sep 30 07:37:03 2010 - Thu Sep 30 08:01:21 2010
> LOOKING FOR UNCONNECTED NODES
> FSCK: node.c: 108: repair_node_items_check: Node (189713135), items (44) and
> (45): Wrong order of keys.
> Read nodes 1
> Good nodes 0
> Leaves of them 0, Twigs of them 0
> Time interval: Thu Sep 30 08:01:26 2010 - Thu Sep 30 08:01:26 2010
> ***** fsck.reiser4 finished at Thu Sep 30 08:01:26 2010
> Closing fs...done
>
> FS is consistent.
>
>
Could you please pack the metadata by
debugfs.reiser4 -P /dev/xxx | gzip > meta.gz
and let me download the file meta.gz
Thanks,
Edward.
P.S.:
If you don't want to wait a lot, you can try to figure out
(with gdb) why fsck falls to "consistent" branch instead
of fixing the key inconsistency. I don't think there is a big
deal here..
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2010-10-04 15:12 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-10-01 4:32 fsck.reiser4 does not fix corruption Volker Armin Hemmann
2010-10-04 15:12 ` Edward Shishkin
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).