linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] lvm und promise fasttrack
Date: Fri Oct 26 03:20:02 2001	[thread overview]
Message-ID: <20011026101802.B32377@sistina.com> (raw)
In-Reply-To: <20011026081326.A18287@dragon.blacknet.de>; from bock@blacknet.de on Fri, Oct 26, 2001 at 08:13:26AM +0200

On Fri, Oct 26, 2001 at 08:13:26AM +0200, Goetz Bock wrote:
> 
> Hallo Jens,
> > > ich hab schon wieder ein "Problem".
> Well, it might be a good idea to write your requests to an international
> mailing list in english ...

Well, Jens probably wanted to send it to me personally :-)

> so let's translate your questions (not a strict translation)
> 
> > > Auf meinem Mainboard ist ein Promise Fasttrack 100 Controller.
> > > Die Festplatten kann ich ueber /dev/hd[e-h] ansprechen.
> > My mainboard features a Promise Fasttrack 100 Controller, and I can
> > access my harddrives as /dev/hd[e-h]
> > 
> > > Es gibt aber auch die Moeglichkeit das Hardware Raid anzuspechen ueber
> > > /dev/ataraid/d[0-2]px , mit x als Partitionsnummer.
> > But there is also the option to use the hardware raid as
> > /dev/ataraid/d[0-2]px, with x beeing the partition number
> > 
> > > Beim Aufruf von vgcreate passiert folgendes :
> > when calling vgcreate like this:
> > vgcreate gl_lvm /dev/ataraid/d0p1
> > vgcreate -- physical volume name "/dev/ataraid/d0p1" is invalid
> For this to work, you must first use pvcreate to add the LVM's PV
> information to your device:
> pvcreate /dev/ataraid/d0p1
> 
> But this will not help you, as pvcreate checls the device name against a
> list of valid devices, and /dev/ataraid is not port of this (at last not
> in the way outdated 0.9.1beta5 src I've on this system)
> 
> OOTH you should not trust the bios based softraid of any of the consumer
> raid devices, it is no hardware raid (not just MHO). If you want to do raid
> with IDE devices, I'd suggest using the kernel based MD drivers, and putting 
> every IDE disk on it's own channel.   

Yes, but if Jens still wants it, "atatraid" needs to be added to the _devdir
array in lvm_dir_cache.c.
In future LVM you just change/add an entry to a central config file.

> 
> -- 
> Goetz Bock                                              IT Consultant
> Dipl.-Inf. Univ.



-- 

Regards,
Heinz    -- The LVM Guy --

*** Software bugs are stupid.
    Nevertheless it needs not so stupid people to solve them ***

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

      reply	other threads:[~2001-10-26  3:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-25 12:19 [linux-lvm] lvm und promise fasttrack Jens Tkotz
2001-10-26  1:12 ` Goetz Bock
2001-10-26  3:20   ` Heinz J . Mauelshagen [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=20011026101802.B32377@sistina.com \
    --to=mauelshagen@sistina.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).