From: Christian <evilninja@gmx.net>
To: sergey ivanov <seriv@parkheights.dyndns.org>
Cc: reiserfs-list@namesys.com
Subject: Re: an incident with reiser4
Date: Tue, 15 Mar 2005 18:50:55 +0100 [thread overview]
Message-ID: <4237207F.8000803@gmx.net> (raw)
In-Reply-To: <42370220.7060103@parkheights.dyndns.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
sergey ivanov wrote:
> # fsck.reiser4 --build-fs /dev/evms/home |tee /root/reiser4.log, and
> after some minutes the filesystem is consystent.
> But alas, all the messages was not directed to stdout, but stderr, so
> the file /root/reiser4.log was empty.
use "fsck.reiser4 --build-fs /dev/evms/home 2>&1 |tee /root/reiser4.log"
to also get stderr messages to the logfile.
> 2) Is it possible to check information at this filesystem, by reiser4
> tools or some another way, - or I should wait if some of mail users
> complain about corrupted or missing information?
as several other readers here pointed out - reiser4 is still beta, don't
use it in production but use it everwhere else to shake out all the
remaining bugs ;)
if you're already using it in production and fsck.reiser4 reports no more
errors, i can't think of any other way than to diff your current reiserfs
with a snapshot made earlier. but since files under /home and especially
mails are always "in flight", this would require a lot of manual "this
file is different, because..." actions.
> 3) Is it possible to identify the problem, or it is gone since I have
> not redirected output of fsck.reiser4 right way?
sorry, can't help you here.
- --
BOFH excuse #309:
firewall needs cooling
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCNyB/C/PVm5+NVoYRAtRoAJ0WYPOBvNsz+LFe0r8xYfF8zEDpEACgpU/C
8NFhJ0YlSom+a9wHf7tStBk=
=hGXK
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2005-03-15 17:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-15 15:41 an incident with reiser4 sergey ivanov
2005-03-15 17:50 ` Christian [this message]
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=4237207F.8000803@gmx.net \
--to=evilninja@gmx.net \
--cc=reiserfs-list@namesys.com \
--cc=seriv@parkheights.dyndns.org \
/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.