From: Andreas Dilger <adilger@turbolinux.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] alpha 2.4.2 + 0.9.1_beta6
Date: Wed, 4 Apr 2001 18:18:56 -0600 (MDT) [thread overview]
Message-ID: <200104050018.f350Iu910698@webber.adilger.int> (raw)
In-Reply-To: <3ACB0FED.C7F0668F@lmt.lv> from Andrejs Dubovskis at "Apr 4, 2001 03:13:33 pm"
Andrejs Dubovskis writes:
> unfortunately, for my environment LVM subsystem does not look stable.
> AlphaServer AS400
> Redhat 7.0
> 2.4.2 + LVM 0.9.1_beta6
> 2 SCSI disk
>
> pvcreate /dev/sda1
> pvcreate /dev/sdb2
> vgcreate vg01 /dev/sda1 /dev/sdb2
> lvcreate -i 2 -I 8 -l 2040 -n sms vg01
> mke2fs -m 0 /dev/vg01/sms
>
> All test was done in single mode (no network, users, daemons, etc).
>
> boot system in single mode
>
> vgchange -a y
> mount /dev/vg01/sms /opt
> dd if=/dev/zero of=/opt/1 count=10000
> dd if=/dev/zero of=/opt/2 count=100000
> dd if=/dev/zero of=/opt/3 count=1000000
> (dd commands' count every next boot may be different)
> Got kernel panic in interrupt handle.
Sorry, can't help you if you don't include ksymoops output (or at least
some more specific problem description).
> vgchange -a y
> Got kernel panic in interrupt handle (not reproducible at next boot).
Need ksymoops info as well. I don't have any non-ix86 systems to test on,
but at least we should be able to narrow down the problem a bit. Note
that Andrea Arcangeli does test LVM on Alpha, so I'm surprised there are
major problems. However, it may be that he has Alpha-specific patches
in his LVM code that are not in the standard LVM sources.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
prev parent reply other threads:[~2001-04-05 0:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-04 12:13 [linux-lvm] alpha 2.4.2 + 0.9.1_beta6 Andrejs Dubovskis
2001-04-05 0:18 ` Andreas Dilger [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=200104050018.f350Iu910698@webber.adilger.int \
--to=adilger@turbolinux.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 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).