From: Vladimir Saveliev <vs@namesys.com>
To: Andreas <IOBuf@gmx.de>
Cc: reiserfs-list@namesys.com
Subject: Re: fsck.reiser4 problem (was: reiser4 corruption problem)
Date: Tue, 31 Aug 2004 16:30:15 +0400 [thread overview]
Message-ID: <1093955415.2716.476.camel@tribesman.namesys.com> (raw)
In-Reply-To: <200408311209.43653.IOBuf@gmx.de>
Hello
On Tue, 2004-08-31 at 14:09, Andreas wrote:
> Hello,
>
> > Before doing so, however, try setting
> > the filesystem's default fibration plugin to none or whatever the 'no
> > fibration' option is. This will remove fibration code from the suspect list
> > if the retest is successful.
>
> I can reproduce the reporting of filesystem corruptions with and
> "without" fibration. But fsck.reiser4 crashes on --build-fs on my
> machine. :-(
>
Would you, please, provide exact sequences of operations which confuses
reiser4?
> System:
> linux-2.6.8.1-mm4
> libaal-1.0.0
> reiser4progs-1.0.0
>
> Bye
> Andreas
>
next prev parent reply other threads:[~2004-08-31 12:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-31 1:24 fsck.reiser4 problem (was: reiser4 corruption problem) David Dabbs
2004-08-31 8:52 ` Michael Weissenbacher
[not found] ` <41344719.7040700@free.fr>
2004-08-31 9:43 ` fsck.reiser4 problem Michael Weissenbacher
2004-08-31 10:09 ` fsck.reiser4 problem (was: reiser4 corruption problem) Andreas
2004-08-31 12:30 ` Vladimir Saveliev [this message]
2004-08-31 12:37 ` Michael Weissenbacher
2004-08-31 14:03 ` Andreas
2004-08-31 14:43 ` Vladimir Saveliev
2004-08-31 15:04 ` Michael Weissenbacher
-- strict thread matches above, loose matches on Subject: below --
2004-08-31 16:18 David Dabbs
2004-08-31 16:32 ` Michael Weissenbacher
2004-08-31 1:10 David Dabbs
2004-08-30 21:07 David Dabbs
2004-08-31 0:02 ` Michael Weissenbacher
2004-08-26 23:15 reiser4 corruption problem (maybe related to "Broken reiser4 FS") Michael Weissenbacher
2004-08-28 21:49 ` fsck.reiser4 problem (was: reiser4 corruption problem) Michael Weissenbacher
2004-08-29 6:54 ` Adrian Ulrich
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=1093955415.2716.476.camel@tribesman.namesys.com \
--to=vs@namesys.com \
--cc=IOBuf@gmx.de \
--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.