From: Marcelo Tosatti <marcelo@conectiva.com.br>
To: Stephan von Krawczynski <skraw@ithnet.com>
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 08:54:02 -0300 (BRT) [thread overview]
Message-ID: <Pine.LNX.4.55L.0307100852230.7857@freak.distro.conectiva> (raw)
In-Reply-To: <20030710132141.65a8f770.skraw@ithnet.com>
On Thu, 10 Jul 2003, Stephan von Krawczynski wrote:
> 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.
Stephan,
First of all, thanks a lot for your help. Not everyone is willing to
debug/test problems like you do. This is very important for us.
Well, we now know reiserfs patches in 2.4.22-pre are not the problem.
2.4.21 is OK (does not crash when mounting) correct?
next prev parent reply other threads:[~2003-07-10 12:03 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-06 16:34 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
2003-07-10 11:54 ` Marcelo Tosatti [this message]
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=Pine.LNX.4.55L.0307100852230.7857@freak.distro.conectiva \
--to=marcelo@conectiva.com.br \
--cc=green@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@suse.com \
--cc=skraw@ithnet.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
all inboxes | Powered by JetHome®