All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rich Turner <rich@storix.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] determing lvm support
Date: Mon Dec 22 10:05:02 2003	[thread overview]
Message-ID: <1072109013.1353.11.camel@rich> (raw)
In-Reply-To: <20031220123023.H21022@uk.sistina.com>

On Sat, 2003-12-20 at 04:30, Alasdair G Kergon wrote:
> On Fri, Dec 19, 2003 at 04:47:18PM -0800, Rich Turner wrote:
> > lvm2:
> > look for "vgcreate" command and
> Better to check for the new 'lvm' base command: other commands are
> links to it: check that running 'lvm version' produces complete output.
> That will also confirm that device-mapper is available in the live
> kernel and that /dev/mapper/control is set up correctly.
> (See device-mapper/scripts/devmap_mknod.sh)
if i have 'device-mapper' and 'lvm version' produces complete output, is
there anything else to check if lvm is supported on the system?

is 'device-mapper' used for anything else besides lvm?

does the kernel need to be built with 'lvm' support (which i believe was
true with lvm1-created 'lvm-mod'), or does building a kernel for 'lvm'
support just create 'dm-mod' loadable module/builtin 'dm-mod' kernel
support?

> > look for "device-mapper" in /proc/devices or
> It's better to check for that in /proc/misc, which will tell you whether
> or not device-mapper support is present in the running kernel.
why is it better to check in /proc/misc? when device-mapper support is
loaded, it shows up in both /proc/misc as well as /proc/devices.

> 
> > look for "dm-mod" in /lib/modules/[release]/kernel/drivers/md/*
> Better to attempt to load the module with modprobe and then do the
> tests above to check it worked.
>  
> Alasdair

  parent reply	other threads:[~2003-12-22 10:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-19 18:49 [linux-lvm] determing lvm support Rich Turner
2003-12-20  6:31 ` Alasdair G Kergon
2003-12-20  7:37   ` Luca Berra
2003-12-20 17:32     ` Alasdair G Kergon
2003-12-21  2:09       ` Luca Berra
2003-12-21 10:02         ` Alasdair G Kergon
2003-12-22 10:05   ` Rich Turner [this message]
2003-12-22 18:08     ` Alasdair G Kergon
2003-12-20 12:55 ` Micah Anderson

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=1072109013.1353.11.camel@rich \
    --to=rich@storix.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.