From: Phillip Susi <psusi@cfl.rr.com>
To: Martin Vogt <vogt@itwm.fraunhofer.de>
Cc: reiserfs-devel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: fs corruption by doing nothing
Date: Thu, 23 Aug 2007 12:34:59 -0400 [thread overview]
Message-ID: <46CDB733.2000506@cfl.rr.com> (raw)
In-Reply-To: <46CD92B6.5090900@itwm.fraunhofer.de>
Martin Vogt wrote:
>
> Hello,
>
> this bug report describes the following scenario:
>
> - Insert a Knoppix 5.1.1 CD
> into a fileserver with a clean reiserfs system and
> Knoppix completely destroys the reiser filesystem on the fileserver,
> just by booting Knoppix.
>
>
> Its unclear if this is a knoppix bug, but reiserfs
> simply tries to "correct something" which is wrong.
>
>> ReiserFS: sda2: found reiserfs format "3.6" with standard journal
>> ReiserFS: sda2: using ordered data mode
>> ReiserFS: sda2: warning: sh-461: journal_init: wrong transaction max size
>> (144767). Changed to 1024
>
> ^^^^^^^^^^here
>
>> ReiserFS: sdb2: found reiserfs format "3.6" with standard journal
>> ReiserFS: sdb2: using ordered data mode
>> ReiserFS: sdb2: warning: sh-461: journal_init: wrong transaction max size
>> (144767). Changed to 1024
>
> ^^^^^^^^^^here
>
> After that the filesystem is completely broken.
Looks to me that there are two bugs here. The first is with knoppix as
it is mounting each individual mirrored disk instead of the raid device.
The second appears to be in the kernel as it is detecting and
correcting what it thinks is an error but isn't.
prev parent reply other threads:[~2007-08-23 16:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-23 13:59 fs corruption by doing nothing Martin Vogt
2007-08-23 14:31 ` Jan Engelhardt
2007-10-04 23:22 ` [patch] reiserfs: do not repair wrong journal params Edward Shishkin
2007-08-23 16:34 ` Phillip Susi [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=46CDB733.2000506@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-devel@vger.kernel.org \
--cc=vogt@itwm.fraunhofer.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).