From: Stephan von Krawczynski <skraw@ithnet.com>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: green@namesys.com, mason@suse.com, linux-kernel@vger.kernel.org
Subject: Re: 2.4.22-pre3 and reiserfs boot problem
Date: Thu, 10 Jul 2003 13:21:41 +0200 [thread overview]
Message-ID: <20030710132141.65a8f770.skraw@ithnet.com> (raw)
In-Reply-To: <Pine.LNX.4.55L.0307091408340.26373@freak.distro.conectiva>
On Wed, 9 Jul 2003 14:18:37 -0300 (BRT)
Marcelo Tosatti <marcelo@conectiva.com.br> wrote:
> > PS to Marcelo:
> > There is a problem with 2.4.22-pre3. I cannot mount a reiserfs
> > data-partition with 320 GB size located on a 3ware RAID. It just hangs the
> > box, during init or any runlevel I tried. It is completely reproducable,
> > but debugreiserfs on the partition and reiserfsck both show no problems at
> > all ... The things mounts flawlessly under 2.4.22-pre2 and below.
>
> There are no 3ware changes in pre3. So it must be reiserfs or something
> else. Lets try reverting the reiserfs patches to see if they are the
> cause?
>
> Attached are files rei1, rei2, and rei3 (all gzip compressed).
I reverted all three patches and the problem stays just the same. I guess this
makes it a lot likely that the problem lies elsewhere.
If you want me to try others, just send them to me like these three.
Thanks for your support
Stephan
next prev parent reply other threads:[~2003-07-10 11:07 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-06 16:34 2.4.22-pre3 and reiserfs boot problem Stephan von Krawczynski
2003-07-06 18:13 ` Chris Mason
2003-07-06 21:24 ` Stephan von Krawczynski
2003-07-07 10:06 ` Stephan von Krawczynski
2003-07-09 12:01 ` Stephan von Krawczynski
2003-07-09 13:36 ` Chris Mason
2003-07-09 13:48 ` Oleg Drokin
2003-07-09 13:58 ` Stephan von Krawczynski
2003-07-09 14:11 ` Oleg Drokin
2003-07-09 14:25 ` Stephan von Krawczynski
2003-07-09 17:18 ` Marcelo Tosatti
2003-07-10 11:21 ` Stephan von Krawczynski [this message]
2003-07-10 11:54 ` Marcelo Tosatti
2003-07-10 12:20 ` Stephan von Krawczynski
2003-07-10 12:00 ` Stephan von Krawczynski
[not found] ` <20030709154015.GJ150921@niksula.cs.hut.fi>
2003-07-09 16:36 ` Stephan von Krawczynski
2003-07-09 14:01 ` Vincent Touquet
2003-07-09 14:20 ` Stephan von Krawczynski
2003-07-10 14:20 Carl-Daniel Hailfinger
2003-07-10 14:38 ` Stephan von Krawczynski
2003-07-10 14:44 ` Carl-Daniel Hailfinger
2003-07-10 15:12 ` Stephan von Krawczynski
2003-07-10 15:30 ` Anders Karlsson
2003-07-10 15:39 ` Carl-Daniel Hailfinger
2003-07-10 19:06 ` Anders Karlsson
2003-07-10 15:49 "Peter Lojkin"
2003-07-10 16:06 ` Stephan von Krawczynski
2003-07-10 17:55 ` Marcelo Tosatti
2003-07-10 17:57 ` Marcelo Tosatti
[not found] <E19ae9K-000Nas-00.ia6432-inbox-ru@f7.mail.ru>
2003-07-10 17:12 ` Stephan von Krawczynski
2003-07-10 18:01 ` Marcelo Tosatti
2003-07-11 13:15 ` Chris Mason
2003-07-11 13:27 ` Stephan von Krawczynski
2003-07-11 13:48 ` Chris Mason
2003-07-11 13:38 ` Stephan von Krawczynski
2003-07-11 13:51 ` Chris Mason
2003-07-11 15:15 ` Marcelo Tosatti
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=20030710132141.65a8f770.skraw@ithnet.com \
--to=skraw@ithnet.com \
--cc=green@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=mason@suse.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 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).