From: Vitaly Fertman <vitaly@namesys.com>
To: Domenico Andreoli <cavok@libero.it>, reiserfs-list@namesys.com
Cc: 152548@bugs.debian.org
Subject: Re: Bug #152548: docs about reiserfsprogs is confused
Date: Wed, 7 Jan 2004 15:13:25 +0300 [thread overview]
Message-ID: <200401071507.38208.vitaly@namesys.com> (raw)
In-Reply-To: 3FFBA8ED.8050100@libero.it
> > this is the last of the known ones, i'd like to make the package as clean
> > as possible, next release of debian distribution doesn't look too far
> > (BTW, any chance to have 3.6.12 soon?).
yes, I think in a week or so.
> > thanks for your contribute to the debian project.
> >
> > cheers
> > domenico
>
> Package: reiserfsprogs
> Version: 3.x.1b-1
> Severity: normal
this is very old version, you should try the latest -- 3.6.11.
> Man reiserfsck mentions
>
> 2. Run reiserfsck --check --logfile check.log /dev/hda1. If
> reiserfsck --check exits with status 0 it means
> no errors were discovered.
>
> and then says
>
> TODO
> Faster recovering, signal handling, i/o error handling,
> return reasonable exit codes, etc.
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> With -fy, exit status 0 is reported if filesystem is not found on
> specified disk. That seems like a bug.
As was mentioned in the man page exit codes were not always
correct in that version, but it is already fixed in last versions.
I have also checked the exit code of
reiserfsck --check /dev/hda1
from 3.x.1b where /dev/hda1 was not the reiserfs. SuperBlock was
not found and it was aboted -- 134 was returned.
Would you try it all again with 3.6.11 and email me about the results?
--
Thanks,
Vitaly Fertman
prev parent reply other threads:[~2004-01-07 12:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-07 6:36 Bug #152548: docs about reiserfsprogs is confused Domenico Andreoli
2004-01-07 12:13 ` Vitaly Fertman [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=200401071507.38208.vitaly@namesys.com \
--to=vitaly@namesys.com \
--cc=152548@bugs.debian.org \
--cc=cavok@libero.it \
--cc=reiserfs-list@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.