linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oleg Drokin <green@namesys.com>
To: Tupshin Harper <tupshin@tupshin.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: JDIRTY JWAIT errors in 2.4.19
Date: Mon, 16 Dec 2002 09:46:16 +0300	[thread overview]
Message-ID: <20021216094616.A20997@namesys.com> (raw)
In-Reply-To: <3DFD74B5.5050206@tupshin.com>

Hello!

On Sun, Dec 15, 2002 at 10:37:41PM -0800, Tupshin Harper wrote:
> >Can you please execute SysRq-T, decode it with ksymoops and send us the 
> >result?
> I have succeeded in reproducing this problem at will (and 
> deterministically) with a SysRq enabled kernel.

Ok.

> I can reproduce the problem consistently by doing a cp -av of a 
> directory(haven't tried other cp permutations, guessing it wouldn't make 
> a difference) containing three mp3 files from one location on a 
> partition to another location on the same reiserfs partition. During the 
> third file, cp hangs(continues to use 80%+ of the CPU), and is 
> unkillable. A few minutes later, it starts generating the same JDIRTY 
> error messages that I reported before.

Can you please produce a metadump data for us?
use debugreiserfs -p /dev/yourdevice | gzip -9c >metadata.gz
then tell us where we can get that file.
Also please use recent reiserfsprogs for that operation
(e.g. version 3.6.4 available from us: ftp://ftp.namesys.com/pub/reiserprogs )

> I have not tried to do any kind of reiserfs check or repair on the 
> filesystem, and I can trigger this problem at any point if you would 
> like me to test further.

Let's see if we can reproduce it locally after you give us the metadata.

Thank you.

Bye,
    Oleg

      reply	other threads:[~2002-12-16  6:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-14  9:29 JDIRTY JWAIT errors in 2.4.19 Tupshin Harper
2002-12-14 10:55 ` Oleg Drokin
2002-12-14 18:34   ` Tupshin Harper
2002-12-16  6:37   ` Tupshin Harper
2002-12-16  6:46     ` 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=20021216094616.A20997@namesys.com \
    --to=green@namesys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tupshin@tupshin.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).