* Is it possible to speed up the command fsck.reiser4
@ 2013-09-18 13:49 doiggl
2013-09-20 8:11 ` Mathieu Belanger
0 siblings, 1 reply; 3+ messages in thread
From: doiggl @ 2013-09-18 13:49 UTC (permalink / raw)
To: reiserfs-devel
Hello,
Questions:
Is it possible to speed up the command
#fsck.reiser4 --build-fs /dev/sdX
These days disk capacity is increasing.
There are more cores per cpu.
According to report it took 658 minutes to do
How come it takes a long time to run?
In the future will it be speeded up ?
Thanks Glenn
report at [1]
# fdisk -l
Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes, 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
***** fsck.reiser4 finished at Sun Jan 29 13:35:04 2012
***** fsck.reiser4 started at Sun Jan 29 02:37:21 2012
[1]
# fsck.reiser4 --build-fs /dev/sdc
*******************************************************************
This is an EXPERIMENTAL version of fsck.reiser4. Read README first.
*******************************************************************
Fscking the /dev/sdc block device.
Will check the consistency of the Reiser4 SuperBlock.
Will build the Reiser4 FileSystem.
Continue?
(Yes/No): yes
***** fsck.reiser4 started at Sun Jan 29 02:37:21 2012
Reiser4 fs was detected on /dev/sdc.
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: Sun Jan 29 02:39:18 2012 - Sun Jan 29 11:20:38 2012
CHECKING EXTENT REGIONS.
Read twigs 2217790
Time interval: Sun Jan 29 11:20:38 2012 - Sun Jan 29 13:30:57 2012
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: Sun Jan 29 13:31:14 2012 - Sun Jan 29 13:35:04 2012
***** fsck.reiser4 finished at Sun Jan 29 13:35:04 2012
Closing fs...done
FS is consistent.
[2]
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: Is it possible to speed up the command fsck.reiser4
2013-09-18 13:49 Is it possible to speed up the command fsck.reiser4 doiggl
@ 2013-09-20 8:11 ` Mathieu Belanger
2013-09-20 21:07 ` Edward Shishkin
0 siblings, 1 reply; 3+ messages in thread
From: Mathieu Belanger @ 2013-09-20 8:11 UTC (permalink / raw)
To: doiggl; +Cc: reiserfs-devel
A build-fs probably read the whole disk to find what it need to
rebuild (I did not check inside but it sound like that). After, if you
add that for reading a fatty 2TB hard drive still go at the speed of a
80GB drive, that will justify the time ;)
So if fsck go read the nodes "one at a time" and that you have
something like a Western digital Grean 2TB, you end up with a nominal
transfer speed of 56.6MiB/s with is about half the max because you
miss one (slow)RPM of read, you end up with 609 minutes and so just to
read the STORAGES TREE nodes...
If fsck read them "one at a time", it could be speed-up by doing a
sequential read of the whole disk and using the ram for buffer to scan
for theses nodes but it's not actually the priority (lot of thing are
more important than the speed of fsck, for exemple FITRIM to keep our
SSD fast).
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Is it possible to speed up the command fsck.reiser4
2013-09-20 8:11 ` Mathieu Belanger
@ 2013-09-20 21:07 ` Edward Shishkin
0 siblings, 0 replies; 3+ messages in thread
From: Edward Shishkin @ 2013-09-20 21:07 UTC (permalink / raw)
To: Mathieu Belanger; +Cc: doiggl, reiserfs-devel
A real possibility to speed up fsck is supporting many storage trees per
volume.
This feature has a special name "subvolumes": you marked some directories as
"subvolumes", so that (meta)data of their children will be stored in the
respective
storage tree.
So, instead of processing one storage tree fsck will process many trees
in parallel.
The old name of this feature is "ChunkFS": there were attempts to
organize something
similar in ext3..
Thanks,
Edward.
On 09/20/2013 10:11 AM, Mathieu Belanger wrote:
>
> A build-fs probably read the whole disk to find what it need to
> rebuild (I did not check inside but it sound like that). After, if you
> add that for reading a fatty 2TB hard drive still go at the speed of a
> 80GB drive, that will justify the time ;)
>
> So if fsck go read the nodes "one at a time" and that you have
> something like a Western digital Grean 2TB, you end up with a nominal
> transfer speed of 56.6MiB/s with is about half the max because you
> miss one (slow)RPM of read, you end up with 609 minutes and so just to
> read the STORAGES TREE nodes...
>
> If fsck read them "one at a time", it could be speed-up by doing a
> sequential read of the whole disk and using the ram for buffer to scan
> for theses nodes but it's not actually the priority (lot of thing are
> more important than the speed of fsck, for exemple FITRIM to keep our
> SSD fast).
> --
> 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] 3+ messages in thread
end of thread, other threads:[~2013-09-20 21:07 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-09-18 13:49 Is it possible to speed up the command fsck.reiser4 doiggl
2013-09-20 8:11 ` Mathieu Belanger
2013-09-20 21:07 ` 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).