From: Joe Thornber <thornber@btconnect.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] lvm-1.0.1 not working with DAC960/2.2.20
Date: Wed Nov 28 03:06:03 2001 [thread overview]
Message-ID: <20011128080052.B434@btconnect.com> (raw)
In-Reply-To: <20011127102808.A730@lynx.no>; from adilger@turbolabs.com on Tue, Nov 27, 2001 at 10:28:08AM -0700
On Tue, Nov 27, 2001 at 10:28:08AM -0700, Andreas Dilger wrote:
> On Nov 27, 2001 11:14 +0100, Heinz J . Mauelshagen wrote:
> >
> > Checked it in.
>
> But now it is broken.
>
> > On Tue, Nov 27, 2001 at 09:44:47AM +0100, Adrian Phillips wrote:
> > > --- tools/lib/lvm_check_partitioned_dev.c.orig Tue Nov 27 09:16:03 2001
> > > +++ tools/lib/lvm_check_partitioned_dev.c Tue Nov 27 09:42:38 2001
> > > @@ -140,7 +140,8 @@
> > > "md", /* Multiple Disk driver (SoftRAID) */
> > > "loop", /* Loop device */
> > > "dasd", /* DASD disk (IBM S/390, zSeries) */
> > > - "dac960", /* DAC960 */
> > > + "rd", /* DAC960 2.2 */
> > > + "dac960", /* DAC960 2.4 */
> > > "nbd", /* Network Block Device */
> > > "ida", /* Compaq SMART2 */
> > > "cciss", /* Compaq CCISS array */
>
> Note that this will break other things, because you also need to update
> the LVM_DEVICE_TYPE_<foo> defines when you change this array (it was
> Joe or Alistair that wrote it this way, not me).
No, Stefan Bader wrote it that way.
- Joe
next prev parent reply other threads:[~2001-11-28 3:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-27 2:43 [linux-lvm] lvm-1.0.1 not working with DAC960/2.2.20 Adrian Phillips
2001-11-27 4:13 ` Heinz J . Mauelshagen
2001-11-27 11:26 ` Andreas Dilger
2001-11-28 0:37 ` Adrian Phillips
2001-11-28 1:18 ` Adrian Phillips
2001-11-29 8:17 ` Heinz J . Mauelshagen
2001-11-29 8:42 ` Adrian Phillips
2001-11-28 3:06 ` Joe Thornber [this message]
2001-11-28 10:15 ` Andreas Dilger
2001-11-28 10:55 ` Joe Thornber
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=20011128080052.B434@btconnect.com \
--to=thornber@btconnect.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.