http://bugzilla.novell.com/show_bug.cgi?id=985580 Bug ID: 985580 Summary: utility program to swap 2 nodes over given the Node number and 2 'Wrong order of keys' ? [reiser4progs-1.1.0] Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening@forge.provo.novell.com Reporter: doiggl@velocitynet.com.au QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Hello, Question: Can a utility program be written to swap 2 nodes over given the Node number and 2 'Wrong order of keys' ? [reiser4progs] fsck.reiser4 commands fail to repair file system [1] is the reason I ask for this. [1] --build-sb --build-fs --fix e.g # fsck.reiser4 --build-sb --build-sb /dev/sdb # fsck.reiser4 --build-fs --build-fs /dev/sdb # fsck.reiser4 --fix /dev/sdb # fsck.reiser4 --fix --help Usage: fsck.reiser4 [ options ] FILE Fsck options: --check checks the consistency (default) --fix fixes minor corruptions --build-sb rebuilds the super block --build-fs rebuilds the filesystem . . . a copy of [reiser4 /dev/sdb] meta-data see: http://www.4shared.com/file/-RA17cXlba/metadata-sdb.html metadata-sdb.bz2 2,049,018 KB | 2016-05-30 Using: # rpm -qa |grep -i reiser4progs |sort reiser4progs-1.1.0-35.1.x86_64 Thank you --Glenn using # fsck.reiser4 -V fsck.reiser4 1.1.0 Format release: 4.0.1 # rpm -qa |grep -i reiser4 |sort kernel-reiser4-4.1.6-7.1.gd2bbe7f.x86_64 libreiser4-1_1-0-1.1.0-14.1.x86_64 reiser4progs-1.1.0-14.1.x86_64 # rpm -qlp reiser4progs-1.1.0-13.1.x86_64.rpm warning: reiser4progs-1.1.0-13.1.x86_64.rpm: Header V3 RSA/SHA1 Signature, key ID 324e6311: NOKEY /usr/sbin/debugfs.reiser4 /usr/sbin/fsck.reiser4 /usr/sbin/make_reiser4 /usr/sbin/measurefs.reiser4 /usr/sbin/mkfs.reiser4 /usr/share/doc/packages/reiser4progs /usr/share/doc/packages/reiser4progs/BUGS /usr/share/doc/packages/reiser4progs/COPYING /usr/share/doc/packages/reiser4progs/ChangeLog /usr/share/doc/packages/reiser4progs/NEWS /usr/share/doc/packages/reiser4progs/README /usr/share/doc/packages/reiser4progs/TODO /usr/share/man/man8/debugfs.reiser4.8.gz /usr/share/man/man8/fsck.reiser4.8.gz /usr/share/man/man8/measurefs.reiser4.8.gz /usr/share/man/man8/mkfs.reiser4.8.gz Examples: # repair_node_item 43828275 0 1 # repair_node_item 52697435 79 80 # repair_node_item 63227569 24 25 # repair_node_item 63227571 73 74 # repair_node_item 116595727 20 21 # repair_node_item 227923161 22 23 # repair_node_item 284305753 61 62 Syntax: repair_node_items <Node number> <item-key number> <item-key number> Output taken from: # fsck.reiser4 --build-fs /dev/sdb # CHECKING THE STORAGE TREE Read nodes 197008413 Nodes left in the tree 197008413 Leaves of them 194764277, Twigs of them 2217790 Time interval: Sun Jan 17 18:22:12 2016 - Mon Jan 18 02:10:12 2016 CHECKING EXTENT REGIONS. Read twigs 2217790 Time interval: Mon Jan 18 02:10:12 2016 - Mon Jan 18 04:19:49 2016 LOOKING FOR UNCONNECTED NODES FSCK: node.c: 108: repair_node_items_check: Node (43828275), items (0) and (1): Wrong order of keys. FSCK: node.c: 108: repair_node_items_check: Node (52697435), items (79) and (80): Wrong order of keys. FSCK: node.c: 108: repair_node_items_check: Node (63227569), items (24) and (25): Wrong order of keys. FSCK: node.c: 108: repair_node_items_check: Node (63227571), items (73) and (74): Wrong order of keys. FSCK: node.c: 108: repair_node_items_check: Node (116595727), items (20) and (21): Wrong order of keys. FSCK: node.c: 108: repair_node_items_check: Node (227923161), items (22) and (23): Wrong order of keys. FSCK: node.c: 108: repair_node_items_check: Node (284305753), items (61) and (62): Wrong order of keys. Read nodes 1481038 Good nodes 471512 Leaves of them 466164, Twigs of them 5348 Time interval: Mon Jan 18 04:20:04 2016 - Mon Jan 18 04:23:48 2016 ***** fsck.reiser4 finished at Mon Jan 18 04:23:48 2016 -- -- You are receiving this mail because: You are on the CC list for the bug.