From: <doiggl@velocitynet.com.au>
To: reiserfs-devel@vger.kernel.org
Cc: Ivan Shapovalov <intelfx100@gmail.com>, edward.shishkin@gmail.com
Subject: help with testing
Date: Fri, 13 Feb 2015 16:08:46 +1100 [thread overview]
Message-ID: <927eb13cbcde61cf5883293488f76fda@mail.velocitynet.com.au> (raw)
In-Reply-To: <1423796471.3303.5.camel@gmail.com>
Hello,
Regards "if you want to help with testing."
I could help with tests after a r4 partition/disk is recovered, using
#fsck.reiser4 --build-fs /dev/sdb
-But I need a patch to fix this problem first [see below]
--Cheers Glenn
--------------
Details:
--------
# 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: Wed Aug 27 03:35:57 2014 - Wed Aug 27 03:39:46
>> 2014
>>
>> ***** fsck.reiser4 finished at Wed Aug 27 03:39:46 2014
>> Closing fs...done
>>
>> FS is consistent.
>
>
> This is a bug in fsck: it jumps to wrong branch for some reasons.
> Not yet fixed.
>
> Edward.
> --
other info:
-----------
# fsck.reiser4 --print-profile /dev/sdb
Default profile:
create: "ccreg40" (id:0x4 type:0x0) [Regular file
plugin for creat(2)]
key: "key_large" (id:0x1 type:0xb) [Key plugin]
compress: "lzo1" (id:0x0 type:0xc) [Compression
plugin]
compressMode: "conv" (id:0x4 type:0xd) [Compression Mode
plugin]
cluster: "64K" (id:0x0 type:0x10) [Cluster plugin]
hash: "r5_hash" (id:0x1 type:0x3) [Directory entry
hash plugin]
fibration: "ext_1_fibre" (id:0x2 type:0x4) [Key fibration
plugin]
formatting: "smart" (id:0x2 type:0x5) [File body
formatting plugin]
reiser4progs-1.0.9 # find . |sort |grep -i fsck
./doc/fsck.reiser4.8
./progs/fsck
./progs/fsck/Makefile.am
./progs/fsck/Makefile.in
./progs/fsck/backup.c
./progs/fsck/backup.h
./progs/fsck/fsck.c
./progs/fsck/fsck.h
# which fsck.reiser4
/usr/sbin/fsck.reiser4
# rpm -qlp reiser4progs-1.0.9-1.2.x86_64.rpm
/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
--installation
# rpm -ivhU reiser4progs-1.0.9-1.2.x86_64.rpm
# r4 partition recovery /dev/sdb
http://www.spinics.net/lists/reiserfs-devel/msg04596.html
next prev parent reply other threads:[~2015-02-13 5:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-13 0:48 [PATCHv5 00/10] reiser4: batch discard support (FITRIM ioctl): initial implementation Ivan Shapovalov
2015-02-13 0:48 ` [PATCHv5 01/10] reiser4: block_alloc: add BA_SOME_SPACE flag for grabbing a fixed amount of space Ivan Shapovalov
2015-02-13 0:48 ` [PATCHv5 02/10] reiser4: block_alloc: add a "monotonic_forward" parameter to reiser4_blocknr_hint to allocate blocks only in forward direction Ivan Shapovalov
2015-02-13 0:48 ` [PATCHv5 03/10] reiser4: block_alloc: move block accounting by pre-commit hook into block_alloc.c and document BA_DEFER behavior Ivan Shapovalov
2015-02-13 0:48 ` [PATCHv5 04/10] reiser4: txnmgr: free allocated but unneeded atom in atom_begin_and_assign_to_txnh() Ivan Shapovalov
2015-02-13 0:48 ` [PATCHv5 05/10] reiser4: txnmgr: add reiser4_create_atom() which creates an empty atom without capturing any nodes Ivan Shapovalov
2015-02-13 0:48 ` [PATCHv5 06/10] reiser4: txnmgr: move "empty atom" shortcut slightly below Ivan Shapovalov
2015-02-13 0:48 ` [PATCHv5 07/10] reiser4: batch discard support: add a dummy FITRIM ioctl handler for directories Ivan Shapovalov
2015-02-13 0:48 ` [PATCHv5 08/10] reiser4: batch discard support: actually implement the FITRIM ioctl handler Ivan Shapovalov
2015-02-13 0:48 ` [PATCHv5 09/10] reiser4: block_alloc: add a "min_len" parameter to reiser4_blocknr_hint to limit allocated extent length from below Ivan Shapovalov
2015-02-13 0:48 ` [PATCHv5 10/10] reiser4: batch discard support: honor minimal extent length passed from the userspace Ivan Shapovalov
2015-02-13 2:11 ` When is the patch set included in the reiser4-for-3.x... release ? doiggl
2015-02-13 3:01 ` Ivan Shapovalov
2015-02-13 5:08 ` doiggl [this message]
2015-02-13 9:39 ` [PATCHv5 00/10] reiser4: batch discard support (FITRIM ioctl): initial implementation Ivan Shapovalov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=927eb13cbcde61cf5883293488f76fda@mail.velocitynet.com.au \
--to=doiggl@velocitynet.com.au \
--cc=edward.shishkin@gmail.com \
--cc=intelfx100@gmail.com \
--cc=reiserfs-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).