All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Otake <totake66@home.com>
To: linux-lvm@sistina.com
Subject: [linux-lvm] lvm deadlock with 2.4.x kernel?
Date: Mon, 14 May 2001 17:11:47 -0500	[thread overview]
Message-ID: <3B005823.33AEE05D@home.com> (raw)

I'm not sure if this has been brought up yet.  Over the weekend, my
Linux hung up on me twice.  Considering that this never happened before
and only two things have recently changed (LVM and ReiserFS) , I did
some reading and came across the bug report for LVM on sistina's website
about LVM deadlocking Linux.

I'm running kernle 2.4.3 with LVM compiled into the kernel.  LVM is
0.9.1_beta7, reiser is 3.x.0j.  All essential fs (/, /usr, /var, /tmp)
are still using ext2 and linux partitions, non essential fs (/home
amongst others) are all on  reiserfs with LVM, excluding /usr/local,
which is still on ext2 and Linux partition.

The first occurance:
Running vmware (not on lvm/reiser) while browsing the web using netscape
and running seti@home.  The system hung on me when I tried to access a
web page that appeared to be task intensive, wether servlets,
javascript, flash, or something else, I don't know.

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.

All hdisks and CD are SCSI, no IDE at all.

As I said, I'm not sure if the system hang was caused by the deadlock,
since the system was dead.  If this is related to the deadlock issue,
are there any possible workarounds, besides being mindful of the system
load?

Thanks

--
_______________
Intolerance is the last defense of the insecure.

-- Tom Otake
-- totake66@home.com
-- #550

             reply	other threads:[~2001-05-14 22:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-14 22:11 Tom Otake [this message]
2001-05-15  8:40 ` [linux-lvm] lvm deadlock with 2.4.x kernel? 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
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=3B005823.33AEE05D@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.