From: Martin Pitt <martin@piware.de>
To: Oleg Drokin <green@namesys.com>
Cc: linux-kernel@vger.kernel.org, vitaly@namesys.com
Subject: Re: PROBLEM: 2.6.0-test1/2 reiserfsck journal replaying hangs
Date: Mon, 4 Aug 2003 12:13:12 +0200 [thread overview]
Message-ID: <20030804101310.GA1187@donald.balu5> (raw)
In-Reply-To: <20030804091703.GC3911@namesys.com>
Hi!
Am 2003-08-04 13:12 +0400 schrieb Oleg Drokin:
> > 3.6.6, the kernel Changes says that 3.6.3 is required at least, thus
> > it should be okay.
> Hi Martin, would you try 3.6.11 reiserfsprogs and tell us about the result?
I upgraded reiserfsck and tried again. Now a note appears that I
obviously created my partitions with an older version of reiserfsprogs
and that the journal header was fixed.
Otherwise, it behaves similar, the last message is "Replaying journal"
and that hangs forever.
Am 2003-08-04 13:17 +0400 schrieb Oleg Drokin:
> On Mon, Aug 04, 2003 at 10:43:07AM +0200, Martin Pitt wrote:
> > > So you are starrting reiserfsck on rootfs and it starts to
> > > replay a journal? That's really weird (but seems there is nthing to do with
> > > kernel, though).
> > Well, it is started automatically. Actually, the line "replaying
> > journal" appears with every boot and it also lasts a while, so I
> > suppose it is actually done. fsck and replaying works with all other
> > file systems, it only hangs with the root fs.
>
> Hm, have you tried to press any other keys prior to ^C?
Yes, but only very few work: after ^C and PrintScreen a prompt
appears: "press Control-D for normal startup or enter root password"
(something similar; ^D works well) and SysRq-... work normally (magic
key).
> What was screen looking like at the hang time (can you capture it somehow?),
That's very difficult, no consoles are active at that time. There are
no error messages and no messages that don't appear with 2.4.x, apart
from the warnings about missing module stuff. I can photograph it if
you want.
> can you press sysrq-T at the time of a hang and then send us the traces?
That's even more difficult, it produces several screenfulls of text
scrolling away very fast. I'd need a serial console for this purpose
but it will last a while to set this up since I don't have the
necessary hardware here. I could do it tomorrow.
Thanks and have a nice day!
Martin
--
Martin Pitt
home: www.piware.de
eMail: martin@piware.de
Es gibt zwei Regeln für Erfolg im Leben:
1. Erzähle den Leuten nie alles, was Du weißt.
next prev parent reply other threads:[~2003-08-04 10:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-03 10:23 Martin Pitt
2003-08-04 7:54 ` Oleg Drokin
2003-08-04 8:43 ` Martin Pitt
2003-08-04 9:10 ` Vitaly Fertman
2003-08-04 9:17 ` Oleg Drokin
2003-08-04 10:13 ` Martin Pitt [this message]
2003-08-04 10:16 ` Oleg Drokin
2003-08-04 13:22 ` Martin Pitt
2003-08-04 13:48 ` Oleg Drokin
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=20030804101310.GA1187@donald.balu5 \
--to=martin@piware.de \
--cc=green@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vitaly@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 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®