From: "Vladimir V. Saveliev" <vs@namesys.com>
To: michael chang <thenewme91@gmail.com>
Cc: ReiserFS List <reiserfs-list@namesys.com>
Subject: Re: reiser3.6 files inaccessable from rescue CD post reiserfsck --rebuild-tree
Date: Tue, 01 Nov 2005 15:28:52 +0300 [thread overview]
Message-ID: <43675F84.3040902@namesys.com> (raw)
In-Reply-To: <43675BBA.1050202@namesys.com>
Hello
Vladimir V. Saveliev wrote:
>>
>>Unfortuantely, I didn't think to thorughly read your e-mail (misread
>>the first line) before preceeding to run reiserfsck from a different,
>>newer live CD (that I had a friend burn), which ran just fine. While
>>some files have "dissapeared" into lost+found (which means they need
>>to be recatagorized or something, including everything in /boot), the
>>remainder of the files (maybe 94% of them or so) are now readable. I
>>have no idea whether or not this is considered "progress". Probably
>>now have to go sort them by magic or something, with filenames like
>>"25740_124378" on them.
>
> It might also be useful for you if knew that this file was initially created in
I meant:
It might be useful if you knew that this file was initially created in a
directory whose id is 25740. You can try to find that directory with find /mnt
-inum 25740
next prev parent reply other threads:[~2005-11-01 12:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-30 23:55 reiser3.6 files inaccessable from rescue CD post reiserfsck --rebuild-tree michael chang
2005-10-31 8:34 ` Vladimir V. Saveliev
2005-10-31 21:41 ` michael chang
2005-11-01 12:12 ` Vladimir V. Saveliev
2005-11-01 12:28 ` Vladimir V. Saveliev [this message]
2005-11-02 0:03 ` michael chang
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=43675F84.3040902@namesys.com \
--to=vs@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=thenewme91@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 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.