* using debugfs.reiser4 options to access R4 on /dev/sdb
@ 2015-02-24 14:24 doiggl
2015-02-24 20:22 ` Vladimir Shebordaev
0 siblings, 1 reply; 8+ messages in thread
From: doiggl @ 2015-02-24 14:24 UTC (permalink / raw)
To: reiserfs-devel
Hello,
Are there any switches with using 'debugfs.reiser4' to help using mount or
print details on R4 disk/partition. Im trying get to access /dev/sdb
Thanks Glenn
/dev/sdb problem encountered:
============================
http://www.spinics.net/lists/reiserfs-devel/msg04665.html
# which debugfs.reiser4
/usr/sbin/debugfs.reiser4
# debugfs.reiser4 -V
debugfs.reiser4 1.0.9
# debugfs.reiser4
Usage: debugfs.reiser4 [ options ] FILE
Browsing options:
-k, --cat FILE browses passed file like standard
cat and ls programs.
Print options:
-s, --print-super prints the both super blocks.
-t, --print-tree prints the whole tree.
-j, --print-journal prints journal.
-d, --print-oid prints oid allocator data.
-a, --print-alloc prints block allocator data.
-b, --print-block N prints block by its number.
-n, --print-nodes FILE prints all nodes file lies in.
-i, --print-file FILE prints all items specified file
consists of.
Metadata options:
-P, --pack-metadata fetches filesystem metadata and writes it
to standard output.
-U, --unpack-metadata uses metadata stream from stdandard input
to construct filesystem by it.
Space options:
-O, --occupied-blocks works with occupied blocks only(default).
-F, --free-blocks works with free blocks only.
-W, --whole-partition works with the whole partition.
-B, --bitmap works with blocks marked in the bitmap
only.
Plugins options:
-p, --print-profile prints the plugin profile.
-l, --print-plugins prints 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.
-f, --force makes debugfs to use whole disk, not
-y, --yes assumes an answer 'yes' to all questions.
block device or mounted partition.
-c, --cache N number of nodes in tree buffer cache
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: using debugfs.reiser4 options to access R4 on /dev/sdb
2015-02-24 14:24 using debugfs.reiser4 options to access R4 on /dev/sdb doiggl
@ 2015-02-24 20:22 ` Vladimir Shebordaev
2015-02-25 2:04 ` doiggl
0 siblings, 1 reply; 8+ messages in thread
From: Vladimir Shebordaev @ 2015-02-24 20:22 UTC (permalink / raw)
To: doiggl; +Cc: reiserfs-devel
On Wed, 2015-02-25 at 01:24 +1100, doiggl@velocitynet.com.au wrote:
> Hello,
> Are there any switches with using 'debugfs.reiser4' to help using mount or
> print details on R4 disk/partition. Im trying get to access /dev/sdb
Well, most of the switches enable some very specific data dumps. You can
use for sure
-l to dump all plugins known to libreiser4
-p to show default profile
-t to dump the tree
-n <file> to dump all nodes where <file> resides
I guess, the tree dump is the most curious data you can get out of that
disk.
But did you use some released reiser4/progs version when you created
filesystem that time? It seems, you've got reiser4 and progs in some
inconsistent state. I guess, it is the reason for unexpected fsck
behavior that Edward was talking about.
By the way, do you have something valuable on that disk? Latest release
from sf.net is expected to work out of the box, you could use it to
format the disk anew.
> Thanks Glenn
>
> /dev/sdb problem encountered:
> ============================
> http://www.spinics.net/lists/reiserfs-devel/msg04665.html
>
> # which debugfs.reiser4
>
> /usr/sbin/debugfs.reiser4
>
> # debugfs.reiser4 -V
> debugfs.reiser4 1.0.9
>
> # debugfs.reiser4
> Usage: debugfs.reiser4 [ options ] FILE
> Browsing options:
> -k, --cat FILE browses passed file like standard
> cat and ls programs.
> Print options:
> -s, --print-super prints the both super blocks.
> -t, --print-tree prints the whole tree.
> -j, --print-journal prints journal.
> -d, --print-oid prints oid allocator data.
> -a, --print-alloc prints block allocator data.
> -b, --print-block N prints block by its number.
> -n, --print-nodes FILE prints all nodes file lies in.
> -i, --print-file FILE prints all items specified file
> consists of.
> Metadata options:
> -P, --pack-metadata fetches filesystem metadata and writes it
> to standard output.
> -U, --unpack-metadata uses metadata stream from stdandard input
> to construct filesystem by it.
> Space options:
> -O, --occupied-blocks works with occupied blocks only(default).
> -F, --free-blocks works with free blocks only.
> -W, --whole-partition works with the whole partition.
> -B, --bitmap works with blocks marked in the bitmap
> only.
> Plugins options:
> -p, --print-profile prints the plugin profile.
> -l, --print-plugins prints 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.
> -f, --force makes debugfs to use whole disk, not
> -y, --yes assumes an answer 'yes' to all questions.
> block device or mounted partition.
>
> -c, --cache N number of nodes in tree buffer cache
> --
> 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] 8+ messages in thread
* Re: using debugfs.reiser4 options to access R4 on /dev/sdb
2015-02-24 20:22 ` Vladimir Shebordaev
@ 2015-02-25 2:04 ` doiggl
2015-02-25 15:35 ` Vladimir Shebordaev
2015-02-27 2:22 ` doiggl
0 siblings, 2 replies; 8+ messages in thread
From: doiggl @ 2015-02-25 2:04 UTC (permalink / raw)
To: Vladimir Shebordaev; +Cc: reiserfs-devel
Hello
I want to access the content on volume.
--Glenn
# debugfs.reiser4
-l to dump all plugins known to libreiser4
-p to show default profile
-t to dump the tree
# debugfs.reiser4 -l /dev/sdb
debugfs.reiser4 1.0.9
Copyright (C) 2001-2005 by Hans Reiser, licensing governed by
reiser4progs/COPYING.
Known plugins:
"reg40" (id:0x0 type:0x0) [Unix-file regular file plugin.]
"dir40" (id:0x1 type:0x0) [Directory file plugin.]
"sym40" (id:0x2 type:0x0) [Symlink file plugin.]
"spl40" (id:0x3 type:0x0) [Special file plugin.]
"ccreg40" (id:0x4 type:0x0) [Cryptcompress regular file plugin.]
"stat40" (id:0x0 type:0x1) [StatData item plugin.]
"cde40" (id:0x2 type:0x1) [Compound directory entry item
plugin.]
"nodeptr40" (id:0x3 type:0x1) [Node pointer item plugin.]
"extent40" (id:0x5 type:0x1) [Extent file body item plugin.]
"plain40" (id:0x6 type:0x1) [Plain file body item plugin.]
"ctail40" (id:0x7 type:0x1) [Compressed file body item plugin.]
"bbox40" (id:0x8 type:0x1) [Safe link item plugin.]
"node40" (id:0x0 type:0x2) [Node plugin.]
"rupasov_hash" (id:0x0 type:0x3) [Rupasov hash plugin.]
"r5_hash" (id:0x1 type:0x3) [R5 hash plugin.]
"tea_hash" (id:0x2 type:0x3) [Tea hash plugin.]
"fnv1_hash" (id:0x3 type:0x3) [Fnv1 hash plugin.]
"deg_hash" (id:0x4 type:0x3) [Degenerate hash plugin.]
"lexic_fibre" (id:0x0 type:0x4) [Lexicographic fibration plugin.]
"dot_o_fibre" (id:0x1 type:0x4) ['.o' fibration plugin.]
"ext_1_fibre" (id:0x2 type:0x4) [1-symbol extention fibration
plugin.]
"ext_3_fibre" (id:0x3 type:0x4) [3-symbol extention fibration
plugin.]
"extents" (id:0x0 type:0x5) ['Extents only' tail policy plugin.]
"tails" (id:0x1 type:0x5) ['Tails only' tail policy plugin.]
"smart" (id:0x2 type:0x5) [Smart tail policy plugin.]
"sdext_lw" (id:0x0 type:0x6) [Light stat data extension plugin.]
"sdext_unix" (id:0x1 type:0x6) [Unix stat data extension plugin.]
"sdext_lt" (id:0x2 type:0x6) [Large times stat data extension
plugin.]
"sdext_symlink" (id:0x3 type:0x6) [Symlink stat data extension
plugin.]
"sdext_plugin_set" (id:0x4 type:0x6) [Plugin Set StatData extension
plugin.]
"sdext_flags" (id:0x5 type:0x6) [Inode flags stat data extension
plugin.]
"sdext_crypto" (id:0x7 type:0x6) [Crypto stat data extension plugin.]
"sdext_heir_set" (id:0x8 type:0x6) [Heir Set StatData extension
plugin.]
"format40" (id:0x0 type:0x7) [Disk-format plugin.]
"oid40" (id:0x0 type:0x8) [Inode number allocator plugin.]
"alloc40" (id:0x0 type:0x9) [Space allocator plugin.]
"journal40" (id:0x0 type:0xa) [Journal plugin.]
"key_short" (id:0x0 type:0xb) [Short key plugin.]
"key_large" (id:0x1 type:0xb) [Large key plugin.]
"lzo1" (id:0x0 type:0xc) [lzo1 compression transform plugin.]
"gzip1" (id:0x1 type:0xc) [gzip1 compression transform
plugin.]
"none" (id:0x0 type:0xd) ['Don't compress' compression mode
plugin.]
"latt" (id:0x1 type:0xd) ['Check on dynamic lattice'
compression mode plugin.]
"ultim" (id:0x2 type:0xd) ['Check ultimately' compression mode
plugin.]
"force" (id:0x3 type:0xd) ['Compress evrything' compression
mode plugin.]
"conv" (id:0x4 type:0xd) ['Convert to extent' compression
mode plugin.]
"64K" (id:0x0 type:0x10) [64K size cluster plugin.]
"32K" (id:0x1 type:0x10) [32K size cluster plugin.]
"16K" (id:0x2 type:0x10) [16K size cluster plugin.]
"8K" (id:0x3 type:0x10) [8K size cluster plugin.]
"4K" (id:0x4 type:0x10) [4K size cluster plugin.]
# debugfs.reiser4 -p /dev/sdb
debugfs.reiser4 1.0.9
Copyright (C) 2001-2005 by Hans Reiser, licensing governed by
reiser4progs/COPYING.
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]
--Glenn
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: using debugfs.reiser4 options to access R4 on /dev/sdb
2015-02-25 2:04 ` doiggl
@ 2015-02-25 15:35 ` Vladimir Shebordaev
2015-02-26 3:13 ` doiggl
2015-02-27 2:22 ` doiggl
1 sibling, 1 reply; 8+ messages in thread
From: Vladimir Shebordaev @ 2015-02-25 15:35 UTC (permalink / raw)
To: doiggl; +Cc: reiserfs-devel
On Wed, 2015-02-25 at 13:04 +1100, doiggl@velocitynet.com.au wrote:
> Hello
> I want to access the content on volume.
> --Glenn
>
> # debugfs.reiser4
> -l to dump all plugins known to libreiser4
> -p to show default profile
> -t to dump the tree
>
> # debugfs.reiser4 -l /dev/sdb
> debugfs.reiser4 1.0.9
> Copyright (C) 2001-2005 by Hans Reiser, licensing governed by
> reiser4progs/COPYING.
>
> Known plugins:
> "reg40" (id:0x0 type:0x0) [Unix-file regular file plugin.]
> "dir40" (id:0x1 type:0x0) [Directory file plugin.]
> "sym40" (id:0x2 type:0x0) [Symlink file plugin.]
> "spl40" (id:0x3 type:0x0) [Special file plugin.]
> "ccreg40" (id:0x4 type:0x0) [Cryptcompress regular file plugin.]
> "stat40" (id:0x0 type:0x1) [StatData item plugin.]
> "cde40" (id:0x2 type:0x1) [Compound directory entry item
> plugin.]
> "nodeptr40" (id:0x3 type:0x1) [Node pointer item plugin.]
> "extent40" (id:0x5 type:0x1) [Extent file body item plugin.]
> "plain40" (id:0x6 type:0x1) [Plain file body item plugin.]
> "ctail40" (id:0x7 type:0x1) [Compressed file body item plugin.]
> "bbox40" (id:0x8 type:0x1) [Safe link item plugin.]
> "node40" (id:0x0 type:0x2) [Node plugin.]
> "rupasov_hash" (id:0x0 type:0x3) [Rupasov hash plugin.]
> "r5_hash" (id:0x1 type:0x3) [R5 hash plugin.]
> "tea_hash" (id:0x2 type:0x3) [Tea hash plugin.]
> "fnv1_hash" (id:0x3 type:0x3) [Fnv1 hash plugin.]
> "deg_hash" (id:0x4 type:0x3) [Degenerate hash plugin.]
> "lexic_fibre" (id:0x0 type:0x4) [Lexicographic fibration plugin.]
> "dot_o_fibre" (id:0x1 type:0x4) ['.o' fibration plugin.]
> "ext_1_fibre" (id:0x2 type:0x4) [1-symbol extention fibration
> plugin.]
> "ext_3_fibre" (id:0x3 type:0x4) [3-symbol extention fibration
> plugin.]
> "extents" (id:0x0 type:0x5) ['Extents only' tail policy plugin.]
> "tails" (id:0x1 type:0x5) ['Tails only' tail policy plugin.]
> "smart" (id:0x2 type:0x5) [Smart tail policy plugin.]
> "sdext_lw" (id:0x0 type:0x6) [Light stat data extension plugin.]
> "sdext_unix" (id:0x1 type:0x6) [Unix stat data extension plugin.]
> "sdext_lt" (id:0x2 type:0x6) [Large times stat data extension
> plugin.]
> "sdext_symlink" (id:0x3 type:0x6) [Symlink stat data extension
> plugin.]
> "sdext_plugin_set" (id:0x4 type:0x6) [Plugin Set StatData extension
> plugin.]
> "sdext_flags" (id:0x5 type:0x6) [Inode flags stat data extension
> plugin.]
> "sdext_crypto" (id:0x7 type:0x6) [Crypto stat data extension plugin.]
> "sdext_heir_set" (id:0x8 type:0x6) [Heir Set StatData extension
> plugin.]
> "format40" (id:0x0 type:0x7) [Disk-format plugin.]
> "oid40" (id:0x0 type:0x8) [Inode number allocator plugin.]
> "alloc40" (id:0x0 type:0x9) [Space allocator plugin.]
> "journal40" (id:0x0 type:0xa) [Journal plugin.]
> "key_short" (id:0x0 type:0xb) [Short key plugin.]
> "key_large" (id:0x1 type:0xb) [Large key plugin.]
> "lzo1" (id:0x0 type:0xc) [lzo1 compression transform plugin.]
> "gzip1" (id:0x1 type:0xc) [gzip1 compression transform
> plugin.]
> "none" (id:0x0 type:0xd) ['Don't compress' compression mode
> plugin.]
> "latt" (id:0x1 type:0xd) ['Check on dynamic lattice'
> compression mode plugin.]
> "ultim" (id:0x2 type:0xd) ['Check ultimately' compression mode
> plugin.]
> "force" (id:0x3 type:0xd) ['Compress evrything' compression
> mode plugin.]
> "conv" (id:0x4 type:0xd) ['Convert to extent' compression
> mode plugin.]
> "64K" (id:0x0 type:0x10) [64K size cluster plugin.]
> "32K" (id:0x1 type:0x10) [32K size cluster plugin.]
> "16K" (id:0x2 type:0x10) [16K size cluster plugin.]
> "8K" (id:0x3 type:0x10) [8K size cluster plugin.]
> "4K" (id:0x4 type:0x10) [4K size cluster plugin.]
>
So, what? fsck complains about unknown plugin for the root directory,
you have to try to dump the tree.
Since you fail to mount the disk, you anyway need debugging output from
running filesystem.
> # debugfs.reiser4 -p /dev/sdb
> debugfs.reiser4 1.0.9
> Copyright (C) 2001-2005 by Hans Reiser, licensing governed by
> reiser4progs/COPYING.
>
> 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]
>
> --Glenn
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: using debugfs.reiser4 options to access R4 on /dev/sdb
2015-02-25 15:35 ` Vladimir Shebordaev
@ 2015-02-26 3:13 ` doiggl
2015-02-26 12:39 ` Vladimir Shebordaev
0 siblings, 1 reply; 8+ messages in thread
From: doiggl @ 2015-02-26 3:13 UTC (permalink / raw)
To: Vladimir Shebordaev; +Cc: reiserfs-devel
On Wed, 25 Feb 2015 18:35:38 +0300, Vladimir Shebordaev
<vladimir.shebordaev@gmail.com> wrote:
>
> So, what? fsck complains about unknown plugin for the root directory,
> you have to try to dump the tree.
>
> Since you fail to mount the disk, you anyway need debugging output from
> running filesystem.
Hello
I tried:
# debugfs.reiser4 -t /dev/sdb |gzip >fsck.reiser4-t.txt.gz
And it produced the following file:
# ll fsck.reiser4-t.txt.gz
-rw-r--r-- 1 root users 44,105,728 Feb 25 22:01 fsck.reiser4-t.txt.gz
# ll fsck.reiser4-t.txt
-rw-r--r-- 1 root users 849764352 Feb 26 14:06 fsck.reiser4-t.txt
849,764,352
start an end shows:[1]
Question:
What process or command to do next ?
Thank you Glenn
[1]
# head fsck.reiser4-t.txt
NODE (37017218) LEVEL=6 ITEMS=27 SPACE=2826 MKFS ID=0x1ddaf754 FLUSH=0x0
#0 NPTR (nodeptr40):
[ffff:0(NAME):16c6f73745f6e61:6d655f3130303335:6847c177b306589b] OFF=28,
LEN=8, flags=0x0 [146395369]
------------------------------------------------------------------------------
#1 NPTR (nodeptr40): [1a897:4(FB):14665646f72612d:234e8:5a3cd448] OFF=36,
LEN=8, flags=0x0 [41273715]
------------------------------------------------------------------------------
#2 NPTR (nodeptr40): [1a897:4(FB):146726565425344:236db:22cf668] OFF=44,
LEN=8, flags=0x0 [233048611]
------------------------------------------------------------------------------
#3 NPTR (nodeptr40): [1a897:4(FB):153696d706c794d:33bfa:63e6c] OFF=52,
LEN=8, flags=0x0 [233054862]
------------------------------------------------------------------------------
#4 NPTR (nodeptr40): [1a897:4(FB):16f70656e535553:423e8:df7db1d] OFF=60,
LEN=8, flags=0x0 [233055996]
.
.
.
# tail fsck.reiser4-t.txt
==============================================================================
NODE (9833881) LEVEL=1 ITEMS=1 SPACE=0 MKFS ID=0x1ddaf754 FLUSH=0x0
#0 CTAIL (ctail40): [19af5:4(FB):636f6d7061712d:19af6:26fe61871] OFF=28,
LEN=4030, flags=0x0 shift=16
==============================================================================
NODE (9833882) LEVEL=1 ITEMS=1 SPACE=0 MKFS ID=0x1ddaf754 FLUSH=0x0
#0 CTAIL (ctail40): [19af5:4(FB):636f6d7061712d:19af6:26fe6282e] OFF=28,
LEN=4030, flags=0x0 shift=16
==============================================================================
NODE (9833883) LEVEL=1 ITEMS=2 SPACE=0 MKFS ID=0x1ddaf754 FLUSH=0x0
#0 CTAIL (ctail40): [19af5:4(FB):636f6d7061712d:19af6:26fe637eb] OFF=28,
LEN=250, flags=0x0 shift=16
------------------------------------------------------------------
#
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: using debugfs.reiser4 options to access R4 on /dev/sdb
2015-02-26 3:13 ` doiggl
@ 2015-02-26 12:39 ` Vladimir Shebordaev
[not found] ` <8285e510086433ffcc25556941f7bbe3@mail.velocitynet.com.au>
0 siblings, 1 reply; 8+ messages in thread
From: Vladimir Shebordaev @ 2015-02-26 12:39 UTC (permalink / raw)
To: doiggl; +Cc: reiserfs-devel
On Thu, 2015-02-26 at 14:13 +1100, doiggl@velocitynet.com.au wrote:
> On Wed, 25 Feb 2015 18:35:38 +0300, Vladimir Shebordaev
> <vladimir.shebordaev@gmail.com> wrote:
>
> >
> > So, what? fsck complains about unknown plugin for the root directory,
> > you have to try to dump the tree.
> >
> > Since you fail to mount the disk, you anyway need debugging output from
> > running filesystem.
>
>
> Hello
>
> I tried:
>
> # debugfs.reiser4 -t /dev/sdb |gzip >fsck.reiser4-t.txt.gz
>
> And it produced the following file:
>
> # ll fsck.reiser4-t.txt.gz
> -rw-r--r-- 1 root users 44,105,728 Feb 25 22:01 fsck.reiser4-t.txt.gz
>
> # ll fsck.reiser4-t.txt
> -rw-r--r-- 1 root users 849764352 Feb 26 14:06 fsck.reiser4-t.txt
>
> 849,764,352
>
> start an end shows:[1]
>
So, you decided you don't need all that gig of text. You are right.
You have to grep the dump file for two strings
"[29:1(SD):0:2a:0]" which names root directory stat data item
"[2a:0(NAME):0:0:0]" which is the root directory item itself
Normally, the output there should look like
NODE (3851068) LEVEL=1 ITEMS=12 SPACE=15 MKFS ID=0x66d6b8ae FLUSH=0x0
#0 SD (stat40): [29:1(SD):0:2a:0] OFF=28, LEN=94, flags=0x0
exts: 3
mask: 0x13
plugin: sdext_lw
offset: 2
len: 14
mode: drwxr-xr-x
nlink: 7
size: 7
plugin: sdext_unix
offset: 16
len: 28
uid: 1000
gid: 0
atime: Wed Feb 25 21:45:42 2015
mtime: Wed Mar 5 00:25:14 2014
ctime: Wed Mar 5 00:25:14 2014
rdev: 350
bytes: 350
plugin: sdext_plugin_set
offset: 44
len: 50
Pset count: 12
permission : id = 0
formatting : id = 2 (smart)
hash : id = 1 (r5_hash)
fibration : id = 2 (ext_1_fibre)
statdata : id = 0 (stat40)
diritem : id = 2 (cde40)
crypto : id = 0
digest : id = 0
compress : id = 1 (gzip1)
compressMode : id = 4 (conv)
cluster : id = 0 (64K)
create : id = 4 (ccreg40)
------------------------------------------------------------------------------
#1 DIRITEM (cde40): [2a:0(NAME):0:0:0] OFF=122, LEN=352, flags=0x0
NR(7) NAME OFFSET HASH
SDKEY
0 . 184
0000000000000000:0000000000000000 0000291:000002a
1 .. 208
0000000000000000:0000000000000000 0000291:000002a
2 data 232
0000000000000000:0000000000000000 00002a1:001cd53
3 etc 256
0000000000000000:0000000000000000 00002a1:0010000
<cropped>
------------------------------------------------------------------------------
Please notice, that actual layout can differ, so ignore any exact
numbers except keys here.
Since fsck complains about unknown item plugin for the root directory,
you've got error message around or instead of the second entry.
> Question:
> What process or command to do next ?
>
> Thank you Glenn
>
> [1]
> # head fsck.reiser4-t.txt
> NODE (37017218) LEVEL=6 ITEMS=27 SPACE=2826 MKFS ID=0x1ddaf754 FLUSH=0x0
>
> #0 NPTR (nodeptr40):
> [ffff:0(NAME):16c6f73745f6e61:6d655f3130303335:6847c177b306589b] OFF=28,
> LEN=8, flags=0x0 [146395369]
> ------------------------------------------------------------------------------
>
> #1 NPTR (nodeptr40): [1a897:4(FB):14665646f72612d:234e8:5a3cd448] OFF=36,
> LEN=8, flags=0x0 [41273715]
> ------------------------------------------------------------------------------
>
> #2 NPTR (nodeptr40): [1a897:4(FB):146726565425344:236db:22cf668] OFF=44,
> LEN=8, flags=0x0 [233048611]
>
> ------------------------------------------------------------------------------
>
>
> #3 NPTR (nodeptr40): [1a897:4(FB):153696d706c794d:33bfa:63e6c] OFF=52,
> LEN=8, flags=0x0 [233054862]
>
> ------------------------------------------------------------------------------
>
>
> #4 NPTR (nodeptr40): [1a897:4(FB):16f70656e535553:423e8:df7db1d] OFF=60,
> LEN=8, flags=0x0 [233055996]
> .
> .
> .
> # tail fsck.reiser4-t.txt
> ==============================================================================
> NODE (9833881) LEVEL=1 ITEMS=1 SPACE=0 MKFS ID=0x1ddaf754 FLUSH=0x0
> #0 CTAIL (ctail40): [19af5:4(FB):636f6d7061712d:19af6:26fe61871] OFF=28,
> LEN=4030, flags=0x0 shift=16
> ==============================================================================
> NODE (9833882) LEVEL=1 ITEMS=1 SPACE=0 MKFS ID=0x1ddaf754 FLUSH=0x0
> #0 CTAIL (ctail40): [19af5:4(FB):636f6d7061712d:19af6:26fe6282e] OFF=28,
> LEN=4030, flags=0x0 shift=16
> ==============================================================================
> NODE (9833883) LEVEL=1 ITEMS=2 SPACE=0 MKFS ID=0x1ddaf754 FLUSH=0x0
> #0 CTAIL (ctail40): [19af5:4(FB):636f6d7061712d:19af6:26fe637eb] OFF=28,
> LEN=250, flags=0x0 shift=16
> ------------------------------------------------------------------
> #
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: using debugfs.reiser4 options to access R4 on /dev/sdb
2015-02-25 2:04 ` doiggl
2015-02-25 15:35 ` Vladimir Shebordaev
@ 2015-02-27 2:22 ` doiggl
1 sibling, 0 replies; 8+ messages in thread
From: doiggl @ 2015-02-27 2:22 UTC (permalink / raw)
To: reiserfs-devel
# 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 Thu Feb 26 15:03:06 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: Thu Feb 26 15:05:01 2015 - Thu Feb 26 23:11:57 2015
CHECKING EXTENT REGIONS.
Read twigs 2217790
Time interval: Thu Feb 26 23:11:57 2015 - Fri Feb 27 01:22:19 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: Fri Feb 27 01:22:38 2015 - Fri Feb 27 01:26:23 2015
***** fsck.reiser4 finished at Fri Feb 27 01:26:23 2015
Closing fs...done
FS is consistent.
# 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 Fri Feb 27 02:58:06 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: Fri Feb 27 03:00:05 2015 - Fri Feb 27 11:07:45 2015
CHECKING EXTENT REGIONS.
Read twigs 2217790
Time interval: Fri Feb 27 11:07:45 2015 - Fri Feb 27 13:18:06 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: Fri Feb 27 13:18:06 2015 - Fri Feb 27 13:18:06 2015
FSCK: repair.c: 550: repair_sem_fini: On-disk used block bitmap and really
used block bitmap differ.
***** fsck.reiser4 finished at Fri Feb 27 13:18:07 2015
Closing fs...done
2 fatal corruptions were detected in FileSystem. Run with --build-fs
option to fix them.
#
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: using debugfs.reiser4 options to access R4 on /dev/sdb
[not found] ` <8285e510086433ffcc25556941f7bbe3@mail.velocitynet.com.au>
@ 2015-02-27 5:35 ` Vladimir Shebordaev
0 siblings, 0 replies; 8+ messages in thread
From: Vladimir Shebordaev @ 2015-02-27 5:35 UTC (permalink / raw)
To: doiggl; +Cc: reiserfs-devel
On Fri, 2015-02-27 at 02:37 +1100, doiggl@velocitynet.com.au wrote:
> >
> >
> > So, you decided you don't need all that gig of text. You are right.
> >
> > You have to grep the dump file for two strings
> >
> > "[29:1(SD):0:2a:0]" which names root directory stat data item
> > "[2a:0(NAME):0:0:0]" which is the root directory item itself
> >
> > Normally, the output there should look like
> >
> > NODE (3851068) LEVEL=1 ITEMS=12 SPACE=15 MKFS ID=0x66d6b8ae FLUSH=0x0
> > #0 SD (stat40): [29:1(SD):0:2a:0] OFF=28, LEN=94, flags=0x0
> > exts: 3
> > mask: 0x13
> > plugin: sdext_lw
> > offset: 2
> > len: 14
> > mode: drwxr-xr-x
> > nlink: 7
> > size: 7
> > plugin: sdext_unix
> > offset: 16
> > len: 28
> > uid: 1000
> > gid: 0
> > atime: Wed Feb 25 21:45:42 2015
> > mtime: Wed Mar 5 00:25:14 2014
> > ctime: Wed Mar 5 00:25:14 2014
> > rdev: 350
> > bytes: 350
> > plugin: sdext_plugin_set
> > offset: 44
> > len: 50
> > Pset count: 12
> > permission : id = 0
> > formatting : id = 2 (smart)
> > hash : id = 1 (r5_hash)
> > fibration : id = 2 (ext_1_fibre)
> > statdata : id = 0 (stat40)
> > diritem : id = 2 (cde40)
> > crypto : id = 0
> > digest : id = 0
> > compress : id = 1 (gzip1)
> > compressMode : id = 4 (conv)
> > cluster : id = 0 (64K)
> > create : id = 4 (ccreg40)
> >
> >
> ------------------------------------------------------------------------------
> > #1 DIRITEM (cde40): [2a:0(NAME):0:0:0] OFF=122, LEN=352, flags=0x0
> > NR(7) NAME OFFSET HASH
> > SDKEY
> > 0 . 184
> > 0000000000000000:0000000000000000 0000291:000002a
> > 1 .. 208
> > 0000000000000000:0000000000000000 0000291:000002a
> > 2 data 232
> > 0000000000000000:0000000000000000 00002a1:001cd53
> > 3 etc 256
> > 0000000000000000:0000000000000000 00002a1:0010000
> >
> > <cropped>
> >
> Hello
> Tried to exclude the unwanted lines. Came up with this grep with
> exclude... :
But can you read English? Can you find root directory entry and its
stat-data?
> # cat fsck.reiser4-t.txt | grep -v "CTAIL" | grep -v "LEVEL=" | grep -v
> "(nodeptr40):" | grep -v "====" | grep -v "\-\-\-\-\-" >result.txt
> Attaching the result output file,a lot smaller.
>
> # ll result.txt
> -rw-r--r-- 1 root users 147419 Feb 27 02:32 result.txt
>
>
> Does that contain the wanted detail.
> --Glenn
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2015-02-27 5:35 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-02-24 14:24 using debugfs.reiser4 options to access R4 on /dev/sdb doiggl
2015-02-24 20:22 ` Vladimir Shebordaev
2015-02-25 2:04 ` doiggl
2015-02-25 15:35 ` Vladimir Shebordaev
2015-02-26 3:13 ` doiggl
2015-02-26 12:39 ` Vladimir Shebordaev
[not found] ` <8285e510086433ffcc25556941f7bbe3@mail.velocitynet.com.au>
2015-02-27 5:35 ` Vladimir Shebordaev
2015-02-27 2:22 ` 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.