linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oleg Drokin <green@namesys.com>
To: Stephan von Krawczynski <skraw@ithnet.com>
Cc: mason@suse.com, linux-kernel@vger.kernel.org
Subject: Re: 2.4.22-pre3 and reiserfs boot problem
Date: Wed, 9 Jul 2003 18:11:11 +0400	[thread overview]
Message-ID: <20030709141111.GK18307@namesys.com> (raw)
In-Reply-To: <20030709155803.2d1569a8.skraw@ithnet.com>

Hello!

On Wed, Jul 09, 2003 at 03:58:03PM +0200, Stephan von Krawczynski wrote:
> > > Step one is to figure out if the problem is reiserfs or 3ware.  Instead
> > > of mounting the filesystem, run debugreiserfs -d /dev/xxxx > /dev/null
> > > and see if you still hang.
> > > This will read the FS metadata and should generate enough io to trigger
> > > the hang if it is a 3ware problem.
> Ok, I tried this. debugreiserfs runs without any problems. Disks show quite an
> activity, the whole thing lasts 1-2 minutes.
> mount afterwards shows the same hang.

Hm.

> > Or if this one suceeds, then may be reiserfsck --check /dev/xxxx to get
> > journal replayed. This is in case access pattern matters.
> I can try that, too. What do you expect to see?

Well, it will either hang or not, I think.
It it won't hang, this will complicate matters.
Then next step would be probably to try and mount the partition from usermodelinux if you are able
to conduct such a test.
I am still pretty skeptical about the possibility that recent reiserfs changes broke stuff.

Bye,
    Oleg

  reply	other threads:[~2003-07-09 13:56 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 [this message]
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
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=20030709141111.GK18307@namesys.com \
    --to=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;
as well as URLs for NNTP newsgroup(s).