From: Chris Mason <mason@suse.com>
To: Pierre Etchemaite <petchema@concept-micro.com>
Cc: reiserfs-list@namesys.com
Subject: Re: 2.4.22-pre5+dl going into a loop while unlink()ing
Date: 14 Jul 2003 09:27:32 -0400 [thread overview]
Message-ID: <1058189251.13318.162.camel@tiny.suse.com> (raw)
In-Reply-To: <20030714151230.7e79574f.petchema@concept-micro.com>
On Mon, 2003-07-14 at 09:12, Pierre Etchemaite wrote:
> Hi,
>
> I compiled a 2.4.22-pre5 kernel with current data-logging patch (for
> 2.4.22), all went right 'til I removed a second 600mb file from a partition.
> At that point, the kernel started writing to the disk at full speed (as
> reported by gkrellm), and the disk was no longer available for anything
> else.
>
> I hit the red button, booted using a failsafe 2.4.20 kernel with no
> data-logging, and reiserfsck 3.6.8 from the recovery partition found
> nothing wrong.
>
> Rebooted again with the new kernel, and the kernel got stuck again during
> unlink()s replay! I had to boot using 2.4.21 + dl, that could replay unlinks
> without chocking...
>
> Sadly the dumpreiserfs from recovery partition was outdated and didn't even
> recognize the partition as being reiserfs-formated :(
> Hopefully the problem should not be too hard to reproduce (I wasn't even
> trying to trigger it !), tell me if you can't...
Hmmm, unlinking large files works for me here, what does reiserfsck have
to say about your disk?
If you could try to reproduce and get the output from sysrq-t a few
times during the hang, it would help.
-chris
prev parent reply other threads:[~2003-07-14 13:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-14 13:12 2.4.22-pre5+dl going into a loop while unlink()ing Pierre Etchemaite
2003-07-14 13:27 ` Chris Mason [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=1058189251.13318.162.camel@tiny.suse.com \
--to=mason@suse.com \
--cc=petchema@concept-micro.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.