* What can I do next to use R4 partition sdb
@ 2014-08-26 6:52 doiggl
2014-08-26 7:03 ` Ivan Shapovalov
0 siblings, 1 reply; 16+ messages in thread
From: doiggl @ 2014-08-26 6:52 UTC (permalink / raw)
To: reiserfs-devel
Hello.
What can I do next to use R4 partition sdb
Thanks Glenn
- What I have done so far:
# md /media/disk
# ls -la /media/disk
total 0
drwxr-xr-x 2 root users 48 Aug 18 16:05 .
drwxr-xr-x 4 root root 96 Aug 19 18:21 ..
mount command used.
# strace mount /dev/sdb /media/disk
# strace shows {last few lines}
stat("/sbin/mount.reiser4", 0x7fff82b08700) = -1 ENOENT (No such file or
directory)
stat("/sbin/fs.d/mount.reiser4", 0x7fff82b08700) = -1 ENOENT (No such file
or directory)
stat("/sbin/fs/mount.reiser4", 0x7fff82b08700) = -1 ENOENT (No such file
or directory)
mount("/dev/sdb", "/media/disk", "reiser4", MS_MGC_VAL, NULL) = -1 ENOENT
(No such file or directory)
lstat("/media/disk", {st_mode=S_IFDIR|0755, st_size=48, ...}) = 0
stat("/media/disk", {st_mode=S_IFDIR|0755, st_size=48, ...}) = 0
stat("/dev/sdb", {st_mode=S_IFBLK|0660, st_rdev=makedev(8, 16), ...}) = 0
write(2, "mount: ", 7mount: ) = 7
write(2, "mount(2) failed", 15mount(2) failed) = 15
write(2, ": ", 2: ) = 2
write(2, "No such file or directory\n", 26No such file or directory
) = 26
close(1) = 0
close(2) = 0
exit_group(32) = ?
+++ exited with 32 +++
# cat /proc/filesystems
nodev sysfs
nodev rootfs
nodev ramfs
nodev bdev
nodev proc
nodev cgroup
nodev cpuset
nodev tmpfs
nodev devtmpfs
nodev debugfs
nodev securityfs
nodev sockfs
nodev pipefs
nodev devpts
ext3
ext2
ext4
nodev hugetlbfs
nodev autofs
nodev pstore
nodev mqueue
btrfs
reiserfs
reiser4
#dmesg shows atrer I plug in disk and run command #mount /dev/sdb
/media/disk
13927.148926] usb 1-1: new high-speed USB device number 3 using ehci-pci
[13927.285272] usb 1-1: New USB device found, idVendor=04fc,
idProduct=0c25
[13927.285284] usb 1-1: New USB device strings: Mfr=2, Product=3,
SerialNumber=1
[13927.285291] usb 1-1: Product: USB to Serial-ATA bridge
[13927.285297] usb 1-1: Manufacturer: Sunplus Technology Inc.
[13927.285302] usb 1-1: SerialNumber: ST32000542 5XW1ZMG4
[13927.306242] usb-storage 1-1:1.0: USB Mass Storage device detected
[13927.306757] scsi4 : usb-storage 1-1:1.0
[13927.307043] usbcore: registered new interface driver usb-storage
[13928.310186] scsi 4:0:0:0: Direct-Access ST320005 42AS
PQ: 0 ANSI: 2
[13928.310793] sd 4:0:0:0: Attached scsi generic sg2 type 0
[13928.313184] sd 4:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00
TB/1.81 TiB)
[13928.317396] sd 4:0:0:0: [sdb] Write Protect is off
[13928.317410] sd 4:0:0:0: [sdb] Mode Sense: 38 00 00 00
[13928.320044] sd 4:0:0:0: [sdb] No Caching mode page found
[13928.320056] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[13928.386115] sdb: unknown partition table
[13928.405823] sd 4:0:0:0: [sdb] Attached SCSI disk
[14041.917702] Loading Reiser4. See www.namesys.com for a description of
Reiser4.
[14041.921930] reiser4: sdb: found disk format 4.0.0.
[14152.798878] reiser4[mount(7623)]: traverse_tree
(/home/abuild/rpmbuild/BUILD/kernel-reiser4-3.15.0/linux-3.15/fs/reiser4/search.c:725)[nikita-373]:
WARNING: not found on internal node: level: 6, lock_level: 1, stop_level:
1 lock_mode: read, bias: exact
[14152.798896] reiser4[mount(7623)]: key_warning
(/home/abuild/rpmbuild/BUILD/kernel-reiser4-3.15.0/linux-3.15/fs/reiser4/plugin/file_plugin_common.c:512)[nikita-717]:
WARNING: Error for inode 42 (-2)
# uname -a
Linux test.site 3.15.8-1-vanilla #1 SMP Tue Aug 5 04:15:41 UTC 2014
(258e3b0) x86_64 x86_64 x86_64 GNU/Linux
^ permalink raw reply [flat|nested] 16+ messages in thread* Re: What can I do next to use R4 partition sdb
2014-08-26 6:52 What can I do next to use R4 partition sdb doiggl
@ 2014-08-26 7:03 ` Ivan Shapovalov
2014-08-27 7:33 ` doiggl
2015-02-23 13:41 ` doiggl
0 siblings, 2 replies; 16+ messages in thread
From: Ivan Shapovalov @ 2014-08-26 7:03 UTC (permalink / raw)
To: reiserfs-devel; +Cc: doiggl
[-- Attachment #1: Type: text/plain, Size: 1105 bytes --]
On Tuesday 26 August 2014 at 16:52:13, doiggl@velocitynet.com.au wrote:
> Hello.
> What can I do next to use R4 partition sdb
> Thanks Glenn
>
> - What I have done so far:
>
> [...]
>
> [14041.917702] Loading Reiser4. See www.namesys.com for a description of
> Reiser4.
> [14041.921930] reiser4: sdb: found disk format 4.0.0.
> [14152.798878] reiser4[mount(7623)]: traverse_tree
> (/home/abuild/rpmbuild/BUILD/kernel-reiser4-3.15.0/linux-3.15/fs/reiser4/search.c:725)[nikita-373]:
> WARNING: not found on internal node: level: 6, lock_level: 1, stop_level:
> 1 lock_mode: read, bias: exact
> [14152.798896] reiser4[mount(7623)]: key_warning
> (/home/abuild/rpmbuild/BUILD/kernel-reiser4-3.15.0/linux-3.15/fs/reiser4/plugin/file_plugin_common.c:512)[nikita-717]:
> WARNING: Error for inode 42 (-2)
Looks like the filesystem is damaged. Make sure that reiser4progs are installed
and run
# fsck.reiser4 --build-fs /dev/sdb
(You may need to use --force because apparently you have R4 on a whole disk,
not on a partition.)
Hope that helps,
--
Ivan Shapovalov / intelfx /
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 213 bytes --]
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: What can I do next to use R4 partition sdb
2014-08-26 7:03 ` Ivan Shapovalov
@ 2014-08-27 7:33 ` doiggl
2014-08-27 12:56 ` Edward Shishkin
2015-02-23 13:41 ` doiggl
1 sibling, 1 reply; 16+ messages in thread
From: doiggl @ 2014-08-27 7:33 UTC (permalink / raw)
To: Ivan Shapovalov; +Cc: reiserfs-devel
> Looks like the filesystem is damaged. Make sure that reiser4progs are
> installed
> and run
>
> # fsck.reiser4 --build-fs /dev/sdb
>
> (You may need to use --force because apparently you have R4 on a whole
> disk,
> not on a partition.)
>
> Hope that helps,
#
Hello,
Thanks for the details.
I did the fpllowing steps:
# fsck.reiser4 --build-fs --force /dev/sdb
*******************************************************************
This is an EXPERIMENTAL version of fsck.reiser4. Read README first.
*******************************************************************
Fscking the /dev/sdb block device.
Will check the consistency of the Reiser4 SuperBlock.
Will build the Reiser4 FileSystem.
***** fsck.reiser4 started at Tue Aug 26 17:22:24 2014
Reiser4 fs was detected on /dev/sdb.
Master super block (16):
magic: ReIsEr4
blksize: 4096
format: 0x0 (format40)
uuid: 3006ced1-7490-4ea8-a9b8-d82143c6bede
label: <none>
Format super block (17):
plugin: format40
description: Disk-format plugin.
version: 0
magic: ReIsEr40FoRmAt
mkfs id: 0x1ddaf754
flushes: 0
blocks: 488378640
free blocks: 217146980
root block: 37017218
tail policy: 0x2 (smart)
next oid: 0xedade
file count: 188313
tree height: 6
key policy: LARGE
CHECKING THE STORAGE TREE
Read nodes 197008413
Nodes left in the tree 197008413
Leaves of them 194764277, Twigs of them 2217790
Time interval: Tue Aug 26 17:24:21 2014 - Wed Aug 27 01:25:31 2014
CHECKING EXTENT REGIONS.
Read twigs 2217790
Time interval: Wed Aug 27 01:25:31 2014 - Wed Aug 27 03:35:39 2014
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.
#
# mount /dev/sdb /media/disk
mount: mount(2) failed: No such file or directory
# dmesg - {last few lines}
[ 2058.194138] sdb: unknown partition table
[ 2058.206276] sd 4:0:0:0: [sdb] Attached SCSI disk
[ 2109.541114] SFW2-INext-DROP-DEFLT IN=enp3s0f5 OUT= MAC=
SRC=fe80:0000:0000:0000:22cf:30ff:fe28:fda2
DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=84 TC=0 HOPLIMIT=255
FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=44
[ 2208.241136] Loading Reiser4. See www.namesys.com for a description of
Reiser4.
[ 2208.246484] reiser4: sdb: found disk format 4.0.0.
[ 2319.185875] reiser4[mount(2113)]: traverse_tree
(/home/abuild/rpmbuild/BUILD/kernel-reiser4-3.15.0/linux-3.15/fs/reiser4/search.c:725)[nikita-373]:
WARNING: not found on internal node: level: 6, lock_level: 1, stop_level:
1 lock_mode: read, bias: exact
[ 2319.185893] reiser4[mount(2113)]: key_warning
(/home/abuild/rpmbuild/BUILD/kernel-reiser4-3.15.0/linux-3.15/fs/reiser4/plugin/file_plugin_common.c:512)[nikita-717]:
WARNING: Error for inode 42 (-2)
Question Do I run following command again ?.
# fsck.reiser4 --build-fs --force /dev/sdb
Thanks Glenn
^ permalink raw reply [flat|nested] 16+ messages in thread* Re: What can I do next to use R4 partition sdb
2014-08-27 7:33 ` doiggl
@ 2014-08-27 12:56 ` Edward Shishkin
2014-08-28 2:34 ` reiser4progs revision doiggl
` (3 more replies)
0 siblings, 4 replies; 16+ messages in thread
From: Edward Shishkin @ 2014-08-27 12:56 UTC (permalink / raw)
To: doiggl; +Cc: Ivan Shapovalov, reiserfs-devel
On 08/27/2014 09:33 AM, doiggl@velocitynet.com.au wrote:
>> Looks like the filesystem is damaged. Make sure that reiser4progs are
>> installed
>> and run
>>
>> # fsck.reiser4 --build-fs /dev/sdb
>>
>> (You may need to use --force because apparently you have R4 on a whole
>> disk,
>> not on a partition.)
>>
>> Hope that helps,
> #
>
> Hello,
> Thanks for the details.
>
> I did the fpllowing steps:
> # fsck.reiser4 --build-fs --force /dev/sdb
> *******************************************************************
> This is an EXPERIMENTAL version of fsck.reiser4. Read README first.
> *******************************************************************
>
> Fscking the /dev/sdb block device.
>
>
>
> Will check the consistency of the Reiser4 SuperBlock.
>
> Will build the Reiser4 FileSystem.
>
> ***** fsck.reiser4 started at Tue Aug 26 17:22:24 2014
> Reiser4 fs was detected on /dev/sdb.
>
> Master super block (16):
> magic: ReIsEr4
> blksize: 4096
> format: 0x0 (format40)
> uuid: 3006ced1-7490-4ea8-a9b8-d82143c6bede
> label: <none>
>
> Format super block (17):
> plugin: format40
> description: Disk-format plugin.
> version: 0
> magic: ReIsEr40FoRmAt
> mkfs id: 0x1ddaf754
> flushes: 0
> blocks: 488378640
> free blocks: 217146980
> root block: 37017218
> tail policy: 0x2 (smart)
> next oid: 0xedade
> file count: 188313
> tree height: 6
> key policy: LARGE
>
>
> CHECKING THE STORAGE TREE
>
> Read nodes 197008413
>
> Nodes left in the tree 197008413
>
> Leaves of them 194764277, Twigs of them 2217790
>
> Time interval: Tue Aug 26 17:24:21 2014 - Wed Aug 27 01:25:31 2014
>
> CHECKING EXTENT REGIONS.
>
> Read twigs 2217790
>
> Time interval: Wed Aug 27 01:25:31 2014 - Wed Aug 27 03:35:39 2014
>
> 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.
^ permalink raw reply [flat|nested] 16+ messages in thread* reiser4progs revision.
2014-08-27 12:56 ` Edward Shishkin
@ 2014-08-28 2:34 ` doiggl
2014-08-28 12:54 ` Edward Shishkin
2015-02-11 8:26 ` What can I do next to use R4 partition sdb doiggl
` (2 subsequent siblings)
3 siblings, 1 reply; 16+ messages in thread
From: doiggl @ 2014-08-28 2:34 UTC (permalink / raw)
To: Edward Shishkin; +Cc: Ivan Shapovalov, reiserfs-devel
On Wed, 27 Aug 2014 14:56:05 +0200, Edward Shishkin
<edward.shishkin@gmail.com> wrote:
> On 08/27/2014 09:33 AM, doiggl@velocitynet.com.au wrote:
>>> Looks like the filesystem is damaged. Make sure that reiser4progs are
>>> installed
>>> and run
>>>
>>> # fsck.reiser4 --build-fs /dev/sdb
>>>
>>> (You may need to use --force because apparently you have R4 on a whole
>>> disk,
>>> not on a partition.)
>>>
>>> Hope that helps,
>> #
>>
>> Hello,
>> Thanks for the details.
>>
>> I did the fpllowing steps:
>> # fsck.reiser4 --build-fs --force /dev/sdb
>> *******************************************************************
>> This is an EXPERIMENTAL version of fsck.reiser4. Read README first.
>> *******************************************************************
>>
>> Fscking the /dev/sdb block device.
>>
>>
>>
>> Will check the consistency of the Reiser4 SuperBlock.
>>
>> Will build the Reiser4 FileSystem.
>>
>> ***** fsck.reiser4 started at Tue Aug 26 17:22:24 2014
>> Reiser4 fs was detected on /dev/sdb.
>>
>> Master super block (16):
>> magic: ReIsEr4
>> blksize: 4096
>> format: 0x0 (format40)
>> uuid: 3006ced1-7490-4ea8-a9b8-d82143c6bede
>> label: <none>
>>
>> Format super block (17):
>> plugin: format40
>> description: Disk-format plugin.
>> version: 0
>> magic: ReIsEr40FoRmAt
>> mkfs id: 0x1ddaf754
>> flushes: 0
>> blocks: 488378640
>> free blocks: 217146980
>> root block: 37017218
>> tail policy: 0x2 (smart)
>> next oid: 0xedade
>> file count: 188313
>> tree height: 6
>> key policy: LARGE
>>
>>
>> CHECKING THE STORAGE TREE
>>
>> Read nodes 197008413
>>
>> Nodes left in the tree 197008413
>>
>> Leaves of them 194764277, Twigs of them 2217790
>>
>> Time interval: Tue Aug 26 17:24:21 2014 - Wed Aug 27 01:25:31
>> 2014
>>
>> CHECKING EXTENT REGIONS.
>>
>> Read twigs 2217790
>>
>> Time interval: Wed Aug 27 01:25:31 2014 - Wed Aug 27 03:35:39
>> 2014
>>
>> 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.
Hello,
Some questions:
- Can fsck be fixed so it jumps to "correct" branch branch. ?
- It would be useful to display a message when a Node or key is fixed.
- I can test and report back on the results on a newer reiser4progs
- I can get it build at following location:
Rpms will be produced.
https://build.opensuse.org/package/show/home:doiggl/reiser4progs
reiser4progs.changes 5.73 KB
reiser4progs.spec 3.73 KB
reiser4progs-1.0.9.tar.gz 892 KB
Thanks Glenn
# fsck.reiser4 --h
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
-L, --logfile file complains into the file
-n, --no-log makes fsck to not complain
-a, --auto automatically checks the consistency
without any questions.
-q, --quiet supresses gauges
-r ignored
Plugins options:
--print-profile prints the plugin profile.
-l, --print-plugins prints all known plugins.
-o, --override TYPE=PLUGIN overrides the default plugin of the type
"TYPE" by the plugin "PLUGIN" in the
profile.
Common options:
-?, -h, --help prints program usage.
-V, --version prints current version.
-y, --yes assumes an answer 'yes' to all questions.
-f, --force makes fsck to use whole disk, not block
device or mounted partition.
-p, --preen automatically repair the filesysem.
-c, --cache N number of nodes in tree buffer cache
^ permalink raw reply [flat|nested] 16+ messages in thread* Re: reiser4progs revision.
2014-08-28 2:34 ` reiser4progs revision doiggl
@ 2014-08-28 12:54 ` Edward Shishkin
2014-08-28 14:46 ` dimas
2014-08-29 2:16 ` doiggl
0 siblings, 2 replies; 16+ messages in thread
From: Edward Shishkin @ 2014-08-28 12:54 UTC (permalink / raw)
To: doiggl; +Cc: Ivan Shapovalov, reiserfs-devel
On 08/28/2014 04:34 AM, doiggl@velocitynet.com.au wrote:
> On Wed, 27 Aug 2014 14:56:05 +0200, Edward Shishkin
> <edward.shishkin@gmail.com> wrote:
>> On 08/27/2014 09:33 AM, doiggl@velocitynet.com.au wrote:
>>>> Looks like the filesystem is damaged. Make sure that reiser4progs are
>>>> installed
>>>> and run
>>>>
>>>> # fsck.reiser4 --build-fs /dev/sdb
>>>>
>>>> (You may need to use --force because apparently you have R4 on a whole
>>>> disk,
>>>> not on a partition.)
>>>>
>>>> Hope that helps,
>>> #
>>>
>>> Hello,
>>> Thanks for the details.
>>>
>>> I did the fpllowing steps:
>>> # fsck.reiser4 --build-fs --force /dev/sdb
>>> *******************************************************************
>>> This is an EXPERIMENTAL version of fsck.reiser4. Read README first.
>>> *******************************************************************
>>>
>>> Fscking the /dev/sdb block device.
>>>
>>>
>>>
>>> Will check the consistency of the Reiser4 SuperBlock.
>>>
>>> Will build the Reiser4 FileSystem.
>>>
>>> ***** fsck.reiser4 started at Tue Aug 26 17:22:24 2014
>>> Reiser4 fs was detected on /dev/sdb.
>>>
>>> Master super block (16):
>>> magic: ReIsEr4
>>> blksize: 4096
>>> format: 0x0 (format40)
>>> uuid: 3006ced1-7490-4ea8-a9b8-d82143c6bede
>>> label: <none>
>>>
>>> Format super block (17):
>>> plugin: format40
>>> description: Disk-format plugin.
>>> version: 0
>>> magic: ReIsEr40FoRmAt
>>> mkfs id: 0x1ddaf754
>>> flushes: 0
>>> blocks: 488378640
>>> free blocks: 217146980
>>> root block: 37017218
>>> tail policy: 0x2 (smart)
>>> next oid: 0xedade
>>> file count: 188313
>>> tree height: 6
>>> key policy: LARGE
>>>
>>>
>>> CHECKING THE STORAGE TREE
>>>
>>> Read nodes 197008413
>>>
>>> Nodes left in the tree 197008413
>>>
>>> Leaves of them 194764277, Twigs of them 2217790
>>>
>>> Time interval: Tue Aug 26 17:24:21 2014 - Wed Aug 27 01:25:31
>>> 2014
>>>
>>> CHECKING EXTENT REGIONS.
>>>
>>> Read twigs 2217790
>>>
>>> Time interval: Wed Aug 27 01:25:31 2014 - Wed Aug 27 03:35:39
>>> 2014
>>>
>>> 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.
> Hello,
Hello.
> Some questions:
>
> - Can fsck be fixed so it jumps to "correct" branch branch. ?
Yes, it can.
> - It would be useful to display a message when a Node or key is fixed.
Why?
Thanks,
Edward.
> - I can test and report back on the results on a newer reiser4progs
>
> - I can get it build at following location:
> Rpms will be produced.
> https://build.opensuse.org/package/show/home:doiggl/reiser4progs
>
> reiser4progs.changes 5.73 KB
> reiser4progs.spec 3.73 KB
> reiser4progs-1.0.9.tar.gz 892 KB
>
> Thanks Glenn
>
> # fsck.reiser4 --h
> 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
>
> -L, --logfile file complains into the file
> -n, --no-log makes fsck to not complain
> -a, --auto automatically checks the consistency
> without any questions.
> -q, --quiet supresses gauges
> -r ignored
> Plugins options:
> --print-profile prints the plugin profile.
> -l, --print-plugins prints all known plugins.
> -o, --override TYPE=PLUGIN overrides the default plugin of the type
> "TYPE" by the plugin "PLUGIN" in the
> profile.
> Common options:
> -?, -h, --help prints program usage.
> -V, --version prints current version.
> -y, --yes assumes an answer 'yes' to all questions.
> -f, --force makes fsck to use whole disk, not block
> device or mounted partition.
> -p, --preen automatically repair the filesysem.
> -c, --cache N number of nodes in tree buffer cache
>
>
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: reiser4progs revision.
2014-08-28 12:54 ` Edward Shishkin
@ 2014-08-28 14:46 ` dimas
2014-08-29 2:16 ` doiggl
1 sibling, 0 replies; 16+ messages in thread
From: dimas @ 2014-08-28 14:46 UTC (permalink / raw)
To: reiserfs-devel
people, please stop overquoting))
thanks
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: reiser4progs revision.
2014-08-28 12:54 ` Edward Shishkin
2014-08-28 14:46 ` dimas
@ 2014-08-29 2:16 ` doiggl
2014-08-29 13:27 ` Edward Shishkin
1 sibling, 1 reply; 16+ messages in thread
From: doiggl @ 2014-08-29 2:16 UTC (permalink / raw)
To: Edward Shishkin; +Cc: Ivan Shapovalov, reiserfs-devel
>>> This is a bug in fsck: it jumps to wrong branch for some reasons.
>>> Not yet fixed.
>>>
>>> Edward.
>> Hello,
>
> Hello.
>
>> Some questions:
>>
>> - Can fsck be fixed so it jumps to "correct" branch branch. ?
>
> Yes, it can.
>
>> - It would be useful to display a message when a Node or key is
fixed.
>
> Why?
>
>
> Thanks,
Hello,
Can you send me the .patch file so it jumps to "correct" branch branch. ?
I can apply patch to the spec file and retest using # fsck.reiser4
--build-fs /dev/sdb
[1] spec file locations
I can do a test with:
https://build.opensuse.org/package/view_file/home:doiggl:branches:filesystems/reiser4progs/reiser4progs.spec?expand=1
https://build.opensuse.org/package/show/home:doiggl:branches:filesystems/reiser4progs
##
RE:
- It would be useful to display a message when a Node or key is fixed.
Why?
Thanks,
Edward.
Reason for asking:
Would be nice to know if a Node or key is fixed.
Thanks for the time and effort.
Cheers Glenn
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: reiser4progs revision.
2014-08-29 2:16 ` doiggl
@ 2014-08-29 13:27 ` Edward Shishkin
2014-08-29 14:00 ` doiggl
2015-01-30 8:03 ` doiggl
0 siblings, 2 replies; 16+ messages in thread
From: Edward Shishkin @ 2014-08-29 13:27 UTC (permalink / raw)
To: doiggl; +Cc: Ivan Shapovalov, reiserfs-devel
On 08/29/2014 04:16 AM, doiggl@velocitynet.com.au wrote:
>>>> This is a bug in fsck: it jumps to wrong branch for some reasons.
>>>> Not yet fixed.
>>>>
>>>> Edward.
>>> Hello,
>> Hello.
>>
>>> Some questions:
>>>
>>> - Can fsck be fixed so it jumps to "correct" branch branch. ?
>> Yes, it can.
>>
>>> - It would be useful to display a message when a Node or key is
> fixed.
>> Why?
>>
>>
>> Thanks,
> Hello,
>
> Can you send me the .patch file so it jumps to "correct" branch branch. ?
Wait for the reiser4progs release with the announce of fixed diagnostics
in fsck.
>
> I can apply patch to the spec file and retest using # fsck.reiser4
> --build-fs /dev/sdb
>
> [1] spec file locations
> I can do a test with:
> https://build.opensuse.org/package/view_file/home:doiggl:branches:filesystems/reiser4progs/reiser4progs.spec?expand=1
> https://build.opensuse.org/package/show/home:doiggl:branches:filesystems/reiser4progs
>
> ##
>
> RE:
> - It would be useful to display a message when a Node or key is fixed.
> Why?
>
> Thanks,
> Edward.
>
> Reason for asking:
> Would be nice to know if a Node or key is fixed.
fsck perfectly reports about performed fixups.
Edward.
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: reiser4progs revision.
2014-08-29 13:27 ` Edward Shishkin
@ 2014-08-29 14:00 ` doiggl
2015-01-30 8:03 ` doiggl
1 sibling, 0 replies; 16+ messages in thread
From: doiggl @ 2014-08-29 14:00 UTC (permalink / raw)
To: Edward Shishkin; +Cc: Ivan Shapovalov, reiserfs-devel
Hello,
I will wait for the reiser4progs release with the announce of fixed
diagnostics in fsck and retest with
# fsck.reiser4 --build-fs --force /dev/sdb
and report back the results.
--Glenn
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: reiser4progs revision.
2014-08-29 13:27 ` Edward Shishkin
2014-08-29 14:00 ` doiggl
@ 2015-01-30 8:03 ` doiggl
1 sibling, 0 replies; 16+ messages in thread
From: doiggl @ 2015-01-30 8:03 UTC (permalink / raw)
To: Edward Shishkin; +Cc: Ivan Shapovalov, reiserfs-devel
On Fri, 29 Aug 2014 15:27:43 +0200, Edward Shishkin
<edward.shishkin@gmail.com> wrote:
> On 08/29/2014 04:16 AM, doiggl@velocitynet.com.au wrote:
>>>>> This is a bug in fsck: it jumps to wrong branch for some reasons.
>>>>> Not yet fixed.
>>>>>
>>>>> Edward.
Hello,
Is there any news on the fix to correct [1]
--Glenn
see:
http://www.spinics.net/lists/reiserfs-devel/msg04206.html
[1]
message:
Looks like the filesystem is damaged. Make sure that reiser4progs
are
installed
and run
# fsck.reiser4 --build-fs /dev/sdb
(You may need to use --force because apparently you have R4 on a
whole
disk,
not on a partition.)
Hope that helps,
#
Hello,
Thanks for the details.
I did the fpllowing steps:
# fsck.reiser4 --build-fs --force /dev/sdb
*******************************************************************
This is an EXPERIMENTAL version of fsck.reiser4. Read README first.
*******************************************************************
Fscking the /dev/sdb block device.
Will check the consistency of the Reiser4 SuperBlock. Will build the
Reiser4 FileSystem. ***** fsck.reiser4 started at Tue Aug 26 17:22:24 2014
Reiser4 fs was detected on /dev/sdb.
Master super block (16):
magic: ReIsEr4
blksize: 4096
format: 0x0 (format40)
uuid: 3006ced1-7490-4ea8-a9b8-d82143c6bede
label: <none>
Format super block (17):
plugin: format40
description: Disk-format plugin.
version: 0
magic: ReIsEr40FoRmAt
mkfs id: 0x1ddaf754
flushes: 0
blocks: 488378640
free blocks: 217146980
root block: 37017218
tail policy: 0x2 (smart)
next oid: 0xedade
file count: 188313
tree height: 6
key policy: LARGE
CHECKING THE STORAGE TREE Read nodes 197008413 Nodes left in the tree
197008413 Leaves of them 194764277, Twigs of them 2217790 Time interval:
Tue Aug 26 17:24:21 2014 - Wed Aug 27 01:25:31 2014 CHECKING EXTENT
REGIONS. Read twigs 2217790 Time interval: Wed Aug 27 01:25:31 2014 - Wed
Aug 27 03:35:39 2014 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.
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: What can I do next to use R4 partition sdb
2014-08-27 12:56 ` Edward Shishkin
2014-08-28 2:34 ` reiser4progs revision doiggl
@ 2015-02-11 8:26 ` doiggl
2015-04-13 3:55 ` Can the fix for 'bug in fsck: it jumps to wrong branch for some reason' be included in next reiser4progs please doiggl
2015-12-12 8:45 ` What can I do next to use R4 partition sdb doiggl
3 siblings, 0 replies; 16+ messages in thread
From: doiggl @ 2015-02-11 8:26 UTC (permalink / raw)
To: Edward Shishkin; +Cc: Ivan Shapovalov, reiserfs-devel
Regarding:
it jumps to wrong branch for some reasons.
Not yet fixed.
Edward.
Hello,
------
Question: Is there a .patch file to fix this condition ?
can it be supplied ?
--Thanks Glenn
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
[1]
# 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
################################################
On Wed, 27 Aug 2014 14:56:05 +0200, Edward Shishkin
<edward.shishkin@gmail.com> wrote:
> On 08/27/2014 09:33 AM, doiggl@velocitynet.com.au wrote:
>>> Looks like the filesystem is damaged. Make sure that reiser4progs are
>>> installed
>>> and run
>>>
>>> # fsck.reiser4 --build-fs /dev/sdb
>>>
>>> (You may need to use --force because apparently you have R4 on a whole
>>> disk,
>>> not on a partition.)
>>>
>>> Hope that helps,
>> #
>>
>> Hello,
>> Thanks for the details.
>>
>> I did the fpllowing steps:
>> # fsck.reiser4 --build-fs --force /dev/sdb
>> *******************************************************************
>> This is an EXPERIMENTAL version of fsck.reiser4. Read README first.
>> *******************************************************************
>>
>> Fscking the /dev/sdb block device.
>>
>>
>>
>> Will check the consistency of the Reiser4 SuperBlock.
>>
>> Will build the Reiser4 FileSystem.
>>
>> ***** fsck.reiser4 started at Tue Aug 26 17:22:24 2014
>> Reiser4 fs was detected on /dev/sdb.
>>
>> Master super block (16):
>> magic: ReIsEr4
>> blksize: 4096
>> format: 0x0 (format40)
>> uuid: 3006ced1-7490-4ea8-a9b8-d82143c6bede
>> label: <none>
>>
>> Format super block (17):
>> plugin: format40
>> description: Disk-format plugin.
>> version: 0
>> magic: ReIsEr40FoRmAt
>> mkfs id: 0x1ddaf754
>> flushes: 0
>> blocks: 488378640
>> free blocks: 217146980
>> root block: 37017218
>> tail policy: 0x2 (smart)
>> next oid: 0xedade
>> file count: 188313
>> tree height: 6
>> key policy: LARGE
>>
>>
>> CHECKING THE STORAGE TREE
>>
>> Read nodes 197008413
>>
>> Nodes left in the tree 197008413
>>
>> Leaves of them 194764277, Twigs of them 2217790
>>
>> Time interval: Tue Aug 26 17:24:21 2014 - Wed Aug 27 01:25:31
>> 2014
>>
>> CHECKING EXTENT REGIONS.
>>
>> Read twigs 2217790
>>
>> Time interval: Wed Aug 27 01:25:31 2014 - Wed Aug 27 03:35:39
>> 2014
>>
>> 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.
> --
> 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] 16+ messages in thread
* Can the fix for 'bug in fsck: it jumps to wrong branch for some reason' be included in next reiser4progs please.
2014-08-27 12:56 ` Edward Shishkin
2014-08-28 2:34 ` reiser4progs revision doiggl
2015-02-11 8:26 ` What can I do next to use R4 partition sdb doiggl
@ 2015-04-13 3:55 ` doiggl
2015-12-12 8:45 ` What can I do next to use R4 partition sdb doiggl
3 siblings, 0 replies; 16+ messages in thread
From: doiggl @ 2015-04-13 3:55 UTC (permalink / raw)
To: Edward Shishkin; +Cc: Ivan Shapovalov, reiserfs-devel
Hello,
Can the fix for 'bug in fsck: it jumps to wrong branch for some reason' be
included in next reiser4progs please.
Thank you.
--Glenn
references and history:
http://www.spinics.net/lists/reiserfs-devel/msg04206.html
http://sourceforge.net/projects/reiser4/files/reiser4-utils/reiser4progs/
reiser4progs-1.0.9.tar.gz 2014-06-29 913.5 kB
http://sourceforge.net/projects/reiser4/files/reiser4-utils/reiser4progs/reiser4progs-1.0.9.tar.gz
# cat ./ChangeLog
This file is part of reiser4progs package
Copyright (C) 2001, 2002, 2003, 2004 by Hans Reiser, licensing governed by
reiser4progs/COPYING.
This file may be modified and/or distributed without restriction. This is
not an invitation to misrepresent the history of reiser4progs.
2014-06-28
1.0.9 version
2014-06-28
discard option to mkfs -- discard device at filesystem creation
time (for SSD drives)
Fixup in librepair/twig_scan.c: cb_item_region_check().
2013-05-03
1.0.8 version
.
.
.
#http://www.spinics.net/lists/reiserfs-devel/msg04206.html
>> # fsck.reiser4 --build-fs --force /dev/sdb
.
.
>> (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.
^ permalink raw reply [flat|nested] 16+ messages in thread* Re: What can I do next to use R4 partition sdb
2014-08-27 12:56 ` Edward Shishkin
` (2 preceding siblings ...)
2015-04-13 3:55 ` Can the fix for 'bug in fsck: it jumps to wrong branch for some reason' be included in next reiser4progs please doiggl
@ 2015-12-12 8:45 ` doiggl
3 siblings, 0 replies; 16+ messages in thread
From: doiggl @ 2015-12-12 8:45 UTC (permalink / raw)
To: Edward Shishkin; +Cc: Ivan Shapovalov, reiserfs-devel
>> ***** 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.
#
Hello,
- What line/module changes would allow this to happen [allow fsck to jump
to correct branch]?
I can use 'dd' to make a disk image to another disk and use that.
Thanks Glenn
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: What can I do next to use R4 partition sdb
2014-08-26 7:03 ` Ivan Shapovalov
2014-08-27 7:33 ` doiggl
@ 2015-02-23 13:41 ` doiggl
2015-02-24 0:00 ` doiggl
1 sibling, 1 reply; 16+ messages in thread
From: doiggl @ 2015-02-23 13:41 UTC (permalink / raw)
To: reiserfs-devel; +Cc: Edward Shishkin, Ivan Shapovalov, Vladimir Shebordaev
Hello.
Regarding:
Are you sure /media/disk mountpoint exists? If it does, what shows up
from /proc/partitions? Is sdb a removable disk? Do you have udev
running?..
- Are you sure /media/disk mount point exists ? yes
# ll /media/disk
total 0
- what shows up from /proc/partitions ?
# ll /proc/partitions
-r--r--r-- 1 root root 0 Feb 23 07:40 /proc/partitions
# cat /proc/partitions
major minor #blocks name
8 0 62522712 sda
8 1 18217678 sda1
8 2 12546765 sda2
8 3 29295173 sda3
8 4 2462720 sda4
11 0 1048575 sr0
8 16 1953514584 sdb
- Do you have udev running ?
# ps -ef | grep -i udev
root 281 1 0 Feb22 ? 00:00:00
/usr/lib/systemd/systemd-udevd
- By the way, did you try to run fsck on this disk ever since 08/26 last
year?
yes with --check option then used # fsck.reiser4 --build-fs --force
/dev/sdb
# fsck.reiser4 --check /dev/sdb
*******************************************************************
This is an EXPERIMENTAL version of fsck.reiser4. Read README first.
*******************************************************************
Fscking the /dev/sdb block device.
Will check the consistency of the Reiser4 SuperBlock.
Will check the consistency of the Reiser4 FileSystem.
Continue?
(Yes/No): yes
***** fsck.reiser4 started at Mon Feb 23 01:34:22 2015
Reiser4 fs was detected on /dev/sdb.
Master super block (16):
magic: ReIsEr4
blksize: 4096
format: 0x0 (format40)
uuid: 3006ced1-7490-4ea8-a9b8-d82143c6bede
label: <none>
Format super block (17):
plugin: format40
description: Disk-format plugin.
version: 0
magic: ReIsEr40FoRmAt
mkfs id: 0x1ddaf754
flushes: 0
blocks: 488378640
free blocks: 217146980
root block: 37017218
tail policy: 0x2 (smart)
next oid: 0xedade
file count: 188313
tree height: 6
key policy: LARGE
CHECKING THE STORAGE TREE
Read nodes 197008413
Nodes left in the tree 197008413
Leaves of them 194764277, Twigs of them 2217790
Time interval: Mon Feb 23 01:36:17 2015 - Mon Feb 23 09:24:11 2015
CHECKING EXTENT REGIONS.
] 5%CHECKING THE STORAGE
TREE
Read nodes 197008413
Nodes left in the tree 197008413
Leaves of them 194764277, Twigs of them 2217790
Time interval: Mon Feb 23 01:36:17 2015 - Mon Feb 23 09:24:11 2015
Read twigs 2217790
Time interval: Mon Feb 23 09:24:11 2015 - Mon Feb 23 11:34:13 2015
CHECKING THE SEMANTIC TREE
FSCK: semantic.c: 573: repair_semantic_dir_open: Failed to recognize the
plugin for the directory [29:0:2a].
FSCK: semantic.c: 651: repair_semantic_root_prepare: No root directory
opened.
Time interval: Mon Feb 23 11:34:13 2015 - Mon Feb 23 11:34:13 2015
FSCK: repair.c: 550: repair_sem_fini: On-disk used block bitmap and really
used block bitmap differ.
***** fsck.reiser4 finished at Mon Feb 23 11:34:13 2015
Closing fs...done
2 fatal corruptions were detected in FileSystem. Run with --build-fs
option to fix them.
#
Next:
=====
run the following command and result is:
# fsck.reiser4 --build-fs --force /dev/sdb
*******************************************************************
This is an EXPERIMENTAL version of fsck.reiser4. Read README first.
*******************************************************************
Fscking the /dev/sdb block device.
Will check the consistency of the Reiser4 SuperBlock.
Will build the Reiser4 FileSystem.
***** fsck.reiser4 started at Mon Feb 23 13:09:25 2015
Reiser4 fs was detected on /dev/sdb.
Master super block (16):
magic: ReIsEr4
blksize: 4096
format: 0x0 (format40)
uuid: 3006ced1-7490-4ea8-a9b8-d82143c6bede
label: <none>
Format super block (17):
plugin: format40
description: Disk-format plugin.
version: 0
magic: ReIsEr40FoRmAt
mkfs id: 0x1ddaf754
flushes: 0
blocks: 488378640
free blocks: 217146980
root block: 37017218
tail policy: 0x2 (smart)
next oid: 0xedade
file count: 188313
tree height: 6
key policy: LARGE
CHECKING THE STORAGE TREE
Read nodes 197008413
Nodes left in the tree 197008413
Leaves of them 194764277, Twigs of them 2217790
Time interval: Mon Feb 23 13:11:21 2015 - Mon Feb 23 21:10:47 2015
CHECKING EXTENT REGIONS.
Read twigs 2217790
Time interval: Mon Feb 23 21:10:47 2015 - Mon Feb 23 23:20:58 2015
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 Feb 23 23:21:14 2015 - Mon Feb 23 23:24:57 2015
***** fsck.reiser4 finished at Mon Feb 23 23:24:57 2015
Closing fs...done
FS is consistent.
# mount /dev/sdb /media/disk
mount: mount(2) failed: No such file or directory
Some questions:
===============
- What is the next step so I can access this disk/volume ?
- Is this related to a bug in fsck: it jumps to wrong branch ?
- Is there any patches so it jumps to correct branch I could use ?
Thanks four help and assistance.
--Glenn
References:
http://www.spinics.net/lists/reiserfs-devel/msg04662.html
http://www.spinics.net/lists/reiserfs-devel/msg04206.html
^ permalink raw reply [flat|nested] 16+ messages in thread
end of thread, other threads:[~2015-12-12 8:45 UTC | newest]
Thread overview: 16+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-08-26 6:52 What can I do next to use R4 partition sdb doiggl
2014-08-26 7:03 ` Ivan Shapovalov
2014-08-27 7:33 ` doiggl
2014-08-27 12:56 ` Edward Shishkin
2014-08-28 2:34 ` reiser4progs revision doiggl
2014-08-28 12:54 ` Edward Shishkin
2014-08-28 14:46 ` dimas
2014-08-29 2:16 ` doiggl
2014-08-29 13:27 ` Edward Shishkin
2014-08-29 14:00 ` doiggl
2015-01-30 8:03 ` doiggl
2015-02-11 8:26 ` What can I do next to use R4 partition sdb doiggl
2015-04-13 3:55 ` Can the fix for 'bug in fsck: it jumps to wrong branch for some reason' be included in next reiser4progs please doiggl
2015-12-12 8:45 ` What can I do next to use R4 partition sdb doiggl
2015-02-23 13:41 ` doiggl
2015-02-24 0:00 ` doiggl
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.