From: <doiggl@velocitynet.com.au>
To: Vladimir Shebordaev <vladimir.shebordaev@gmail.com>
Cc: reiserfs-devel@vger.kernel.org
Subject: Re: using debugfs.reiser4 options to access R4 on /dev/sdb
Date: Thu, 26 Feb 2015 14:13:42 +1100 [thread overview]
Message-ID: <d6d728414febcac908cc6aaaf8aebfb6@mail.velocitynet.com.au> (raw)
In-Reply-To: <1424878538.16839.6.camel@home.ted.local>
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
------------------------------------------------------------------
#
next prev parent reply other threads:[~2015-02-26 3:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
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=d6d728414febcac908cc6aaaf8aebfb6@mail.velocitynet.com.au \
--to=doiggl@velocitynet.com.au \
--cc=reiserfs-devel@vger.kernel.org \
--cc=vladimir.shebordaev@gmail.com \
/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).