From: "Michael Styer" <michael@styer.net>
To: Vitaly Fertman <vitaly@namesys.com>
Cc: Vladimir Saveliev <vs@namesys.com>, reiserfs-list@namesys.com
Subject: Re: missing files?
Date: Sat, 05 Feb 2005 11:31:09 -0500 [thread overview]
Message-ID: <1107621069.13887.214400623@webmail.messagingengine.com> (raw)
In-Reply-To: <200502041433.27112.vitaly@namesys.com>
On Fri, 4 Feb 2005, Vitaly Fertman said:
>
> so what I do not understand is why reiserfsck does not report any
> problem to you. Which reiserfsprogs do you have? have you 'umount &
> mount ro' or 'remount,ro', btw? reiser4 does not do 'remount,ro'
> properly yet. have you run fsck.reiser4 on umounted fs?
Hmm. I did 'remount,ro', actually; didn't realize that it wouldn't work
with reiser4. I have version 1.0.3 of the Gentoo reiser4progs package;
fsck.reiser4, mkfs.reiser4 and debugfs.reiser4 all report version 1.0.3.
I concluded that fsck.reiser4 wasn't reporting problems just on the
basis of the lack of problems noted in the /var/log/messages output on
boot, but I hadn't run it manually.
OK. So I killed everything that was keeping /usr busy and unmounted it.
I ran debugfs.reiser4 on /dev/hdb1 unmounted. Then I mounted the
partition ( 'mount -t reiser 4 -o ro,noatime /dev/hdb1 /usr' ). Now
debugfs.reiser4 dies with this output:
Fatal: Can't read master super block. Error: Can't open
reiser4 on /usr
and fsck.reiser4 says this:
Fatal: Can't read master superblock. Fatal: Failed to open the
reiser4 backup. Fatal: Cannot open the FileSysten on (/usr).
1 fatal corruptions were detected in SuperBlock. Run with --build-sb
option to fix them.
I have the output of my first debugfs run if that would be helpful. I'll
put it up for download on the same IP with the filename of
mas.devhdb1_unmounted.bz2. I'm going to reboot so that you can get that
file (this is my webserver as well...).
Regarding the output of fsck.reiser4, it suggests to run fsck.reiser4
--build-sb. What's that going to do to my filesystem? Am I likely to
lose the contents (i.e. is it like reformatting) or will it fix the
structure without causing data loss? At the minute it seems I still have
access to the filesystem, so I could tar everything up now before
rebuilding the superblock if doing so would mean losing that data.
Do you have any suggestions or advice as to what I should do from here?
Thanks very much for your help; I appreciate your taking the time to
help me out with this.
Michael
PS: I've included the list address again in case this discussion might
be helpful to anyone else.
next prev parent reply other threads:[~2005-02-05 16:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-02 4:34 missing files? michael
2005-02-02 5:33 ` Valdis.Kletnieks
2005-02-02 14:18 ` michael
2005-02-02 16:10 ` Vitaly Fertman
2005-02-02 16:25 ` Michael Styer
2005-02-02 17:14 ` Vitaly Fertman
2005-02-02 20:21 ` Michael Styer
[not found] ` <1107376028.24415.214183081@webmail.messagingengine.com>
[not found] ` <200502041433.27112.vitaly@namesys.com>
2005-02-05 16:31 ` Michael Styer [this message]
2005-02-07 15:38 ` Vitaly Fertman
2005-02-07 15:58 ` Michael Styer
2005-02-07 18:24 ` Vitaly Fertman
2005-02-02 11:08 ` Vladimir Saveliev
2005-02-02 15:07 ` Francis Stevens
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=1107621069.13887.214400623@webmail.messagingengine.com \
--to=michael@styer.net \
--cc=reiserfs-list@namesys.com \
--cc=vitaly@namesys.com \
--cc=vs@namesys.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.