From: Tom Otake <totake66@home.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] lvm deadlock with 2.4.x kernel?
Date: Wed, 16 May 2001 21:26:04 -0500 [thread overview]
Message-ID: <3B0336BC.B8BC97D4@home.com> (raw)
In-Reply-To: 3B01AF42.C171FE86@home.com
I've recreated the system hang exactly as I've described below with a pvscan
during a copy. I used a new kernel with hacking enabled, redirected 1 into
/proc/sys/kernel/sysrq. None of the sysrq commands seemed to have worked. The
system hung about 20 to 30 seconds into the copy process.
Tom Otake wrote:
> Yes, I've been able to recreate the second hang scenario, though I have to
> admit it wasn't exactly the same. I started the copy of the data, created a
> new LV, which worked. I ran mkreiserfs on the new LV, it worked. I removed
> the new LV, also worked, then ran pvscan. That's when the system hung. All
> the while, the copy from CD to disk was going on.
>
> Joe Thornber wrote:
>
> >
> > > The second occurance:
> > > I was copying a large amount of data from a CDROM to my home dir (on
> > > lvm). While the copy was in progress, I created a new LV. This
> > > worked. The system hung when I ran mkreiserfs on the new LV.
> >
> > This sounds more serious. Can you reproduce it ? If you can the
> > quickest way for us to find the problem is for you to build the kernel
> > with kdb and get stack traces for the relevent threads.
> >
next prev parent reply other threads:[~2001-05-17 2:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-14 22:11 [linux-lvm] lvm deadlock with 2.4.x kernel? Tom Otake
2001-05-15 8:40 ` Joe Thornber
2001-05-15 22:35 ` Tom Otake
2001-05-15 22:49 ` Andreas Dilger
2001-05-15 23:14 ` Chris Mason
2001-05-16 0:32 ` Andreas Dilger
2001-05-16 1:17 ` Chris Mason
2001-05-16 1:50 ` Jay Weber
2001-05-16 3:35 ` Jay Weber
2001-05-16 8:39 ` Joe Thornber
2001-05-16 10:50 ` Jay Weber
2001-05-16 11:06 ` Joe Thornber
2001-05-16 10:53 ` Heinz J. Mauelshagen
2001-05-16 13:20 ` Chris Mason
2001-05-17 2:26 ` Tom Otake [this message]
2001-05-17 15:31 ` Andreas Dilger
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=3B0336BC.B8BC97D4@home.com \
--to=totake66@home.com \
--cc=linux-lvm@sistina.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.