mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Oleg Drokin <green@namesys.com>
To: peter <peter.zijlstra@chello.nl>
Cc: reiserfs-dev@namesys.com, linux-kernel@vger.kernel.org
Subject: Re: [reiserfs-dev] Kernel(>2.4.16) BUG with reiserfs.
Date: Thu, 7 Feb 2002 12:32:17 +0300	[thread overview]
Message-ID: <20020207123217.B18107@namesys.com> (raw)
In-Reply-To: <1013071308.474.39.camel@twins.localnet> <20020207120002.A18107@namesys.com> <1013073645.3013.10.camel@twins.localnet>
In-Reply-To: <1013073645.3013.10.camel@twins.localnet>

Hello!

On Thu, Feb 07, 2002 at 10:20:45AM +0100, peter wrote:
> > > With all kernels newer than 2.4.16 (eg. that's that last that works for
> > > me), I get a kernel BUG when remounting my rootfs (which is a reiserfs)
> > > for rw access. After the init scripts complete I can log into my machine
> > > but anything calling sync will freeze it hard.
> > Thanks a lot for your report. We were waiting for somebody to get fs in this
> > state (because we cannot reproduce problem locally).
> > How big your root partition is?
> 35 GB ;-)
Yes, that's somewhat big for the mail.

> > > anybody any ideas?
> > Can you please send us image of your root partition, if it is not big,
> > or at least the metadata snapshot.
> > (you can get metadata snapshot by running 
> > debugreiserfs  -p  /dev/xxx  |gzip -c >metadata.gz)
> > You need to make this with filesystem unmounted.
> I'll go hunting for a bootable cd that contains debugreiserfs.
> Where would you like me to send that metadata dump to?
Send it to me.

Bye,
    Oleg

      parent reply	other threads:[~2002-02-07  9:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1013071308.474.39.camel@twins.localnet>
2002-02-07  9:00 ` Oleg Drokin
     [not found]   ` <1013073645.3013.10.camel@twins.localnet>
2002-02-07  9:32     ` Oleg Drokin [this message]

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=20020207123217.B18107@namesys.com \
    --to=green@namesys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter.zijlstra@chello.nl \
    --cc=reiserfs-dev@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®