All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LVM and Network Block Device (problem sollution)
Date: Mon Nov  3 04:15:02 2003	[thread overview]
Message-ID: <20031103111449.G1850@sistina.com> (raw)
In-Reply-To: <212842093.20031101062735@tnonline.net>; from spam@tnonline.net on Sat, Nov 01, 2003 at 06:27:35AM +0100

On Sat, Nov 01, 2003 at 06:27:35AM +0100, Spam wrote:
> 
>   The sollution to the problem was simple. The lvm tools are hardcoded
>   (from  lvm_dir_cache.c)  to  only look for specific directories when
>   scaning  for  lvm disks. For network block devices lvm looks only in
>   /dev/nb/*, while my Gentoo kernel created /dev/nbd/*.
> 
>   A  simple  fix was to make a link /dev/nb->/dev/nbd and it worked. I
>   did not find anything about this in the howto or man-pages.

In LVM2 we don't have hard-coded device namespace like this any more.
You can set up filters in /etc/lvm/lvm.conf, run vgscan and devices
conforming to your filters are used/excluded.

Want to give LVM2 a try ? ;)
(It is LVM1 metadata compatible)

> 
>   //Anders
> 
> >   Hello,
> 
> >   How can I make lvm to recognize my network block devices? They are
> >   listed in /dev/nbd/* and I can access them fine with fdisk or dd.
> 
> >   But when I try pvdisplay /dev/nbd/0 I get the following error:
> 
> >   pvdisplay - ERROR "pv_read(): pv_create_name_from_kdev_t" no VALID
> >               physical volume "/dev/nbd/0"
> 
> >   I get no errors in the logs either so I am not sure where to start.
> 
> >   From what I see lvmdiskscan etc looks in /proc/partitions and never
> >   scans /dev/ for valid blockdevices?
>   
> >   Thanks for any input,
> >   Anders
> 
> 
> 
> 
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

-- 

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:[~2003-11-03  4:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-31 22:39 [linux-lvm] LVM and Network Block Device Spam
2003-10-31 23:28 ` [linux-lvm] LVM and Network Block Device (problem sollution) Spam
2003-11-03  4:15   ` 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=20031103111449.G1850@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 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.