reiserfs-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Is their a patch available for reiser4progs to fix  'Wrong order of keys'  [reiser4progs-1.1.0-14.1] [on /dev/sdb]
@ 2015-09-19  2:39 doiggl
  0 siblings, 0 replies; only message in thread
From: doiggl @ 2015-09-19  2:39 UTC (permalink / raw)
  To: reiserfs-devel

Hello,
A patch question:

Is their a patch available for reiser4progs to fix 'Wrong order of keys'
using [reiser4progs-1.1.0-14.1.x86_64]
[/dev/sdb]

Thanks
--Glenn


# 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

# patch can be applied in spec file -an example follows:
Patch1: fix-xxxxx.patch

%prep
%setup -q
%patch1 -p1

# full spec file:
https://build.opensuse.org/package/view_file/home:doiggl/reiser4progs/reiser4progs.spec?expand=1

 # 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

Background history
==================
 http://www.spinics.net/lists/reiserfs-devel/msg04206.html
 http://www.spinics.net/lists/reiserfs-devel/msg04682.html

[from url] previous run

#fsck.reiser4  --build-fs --force  /dev/sdb
.
.
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: Thu Sep  3 07:11:22 2015 - Thu Sep  3 07:14:56 2015

.
.
This is a bug in fsck: it jumps to wrong branch for some reasons.
Edward.




^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2015-09-19  2:39 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-09-19  2:39 Is their a patch available for reiser4progs to fix 'Wrong order of keys' [reiser4progs-1.1.0-14.1] [on /dev/sdb] doiggl

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).