All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <mason@suse.com>
To: Oleg Drokin <green@namesys.com>
Cc: Oliver Heering <Heering@edo.uni-dortmund.de>, reiserfs-list@namesys.com
Subject: Re: Problem with Kernel 2.4.19, reiser on sw-raid5 and rsync
Date: 05 Mar 2003 09:43:20 -0500	[thread overview]
Message-ID: <1046875400.2163.253.camel@tiny.suse.com> (raw)
In-Reply-To: <20030305172029.A32305@namesys.com>

On Wed, 2003-03-05 at 09:20, Oleg Drokin wrote:
> Hello!
> 
> On Wed, Mar 05, 2003 at 01:23:56PM +0100, Oliver Heering wrote:
> 
> > we've got a big problem with one of our servers using Kernel 2.4.19
> > (SuSE 8.1 standard kernel), rsync and reiserfs on a software-raid5
> > array consisting of 6x75GB (= 375GB usable capacity) harddrives.
> 
> I suppose this is 2.4.19 shipped with SuSE? Is this the last version available from SuSE?
> This is SuSE 8.1, I presume?
> (and rpm -qa | grep k_i386 output please)

> > kernel: Modules: [(reiserfs:<c1dc0060>:<c1def390>)]
> 
> The decoded output is just a mess.
> You seem to need to restart klogd after reiserfs module was loaded, so that it will
> find new module and it's symtab. (or even better: run dmesg | ksymoops immediately
> after oops have happened). That info would be very useful.
> 

See that kernel: Modules line above?  That tells you were the reiserfs
module started and ended at the time of the oops.  We can use it to
decode the thing if Oliver sends us the output from 
nm -n /lib/modules/2.4.19-4GB/kernel/fs/reiserfs.o

Oliver, you might also want to look in the update directory on
ftp.suse.com for an updated kernel, there have been fixes since
September.  

On some machines, ACPI causes bugs and crashes in strange places, so you
could also trying booting with acpi=off or acpi=oldboot

-chris



  reply	other threads:[~2003-03-05 14:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-05 12:23 Problem with Kernel 2.4.19, reiser on sw-raid5 and rsync Oliver Heering
2003-03-05 14:20 ` Oleg Drokin
2003-03-05 14:43   ` Chris Mason [this message]
2003-03-05 14:51     ` 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=1046875400.2163.253.camel@tiny.suse.com \
    --to=mason@suse.com \
    --cc=Heering@edo.uni-dortmund.de \
    --cc=green@namesys.com \
    --cc=reiserfs-list@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.