From: Michael Boman <michael@elinux.com.sg>
To: linux-lvm <linux-lvm@msede.com>,
WebMin List <webmin-l@webmin.com>,
linux-raid <linux-raid@vger.kernel.org>
Cc: Laurence Liew <laurence@elinux.com.sg>
Subject: [linux-lvm] WebMin LVM module development
Date: Wed, 06 Dec 2000 17:43:55 +0800 [thread overview]
Message-ID: <3A2E0A5B.2EB3CCEB@elinux.com.sg> (raw)
[-- Attachment #1: Type: text/plain, Size: 1991 bytes --]
Hi,
for the past week I've been working on a WebMin (http://www.webmin.com)
module for LVM.
I have a few questions I need to get answered as well as I seek people
that is willing to try the LVM module out.
My questions are:
- How can I check what PV's are availble to use with a VG. I know the
pvscan command, but it takes quite a long while to complete and I wonder
if there is any shortcuts to find what PV's that is free to use with a
VG.
- I have problem using MD as a PV of my VG, any hints what it can be?
<output>
mike:/mnt# vgextend vg_test /dev/md0
vgextend -- INFO: maximum logical volume size is 255.99 Gigabyte
vgextend -- ERROR: no physical volumes usable to extend volume group
"vg_test"
</output>
Seeking bug-hunters and feedback:
I'd like to offer the oppertunity for you guy's (and gal's) that are
living on the edge to try out my WebMin LVM module. It's not fully
operational yet (Can only display VG's and assosiated info as well as
create VG's), but I am hoping that a early beta release will provide me
with enuff feedback to make this a good and useful module to WebMin.
The code is under GNU GPL License version 2 or later, and currently
given out on a per-request basis. I nor the company I work for offers no
garranty that it wont eat your data etc.. #include <std/disclaimer.txt>
as per usual.
Jargon file for the uninformed:
MD = Multiple Devices, software raid.
PV = Physical Volume
PE = Physical Extent
LV = Logical Volume
VG = Volume Group
Best regards
Michael Boman
PS
Sorry for cross-posting here, but I wanted to make sure all relivant
parties got informed.
DS
--
"eLINUX --- Enabling the Net Economy on Linux"
----------------------------------------------------------
Michael Boman eLinux Pte Ltd
Technical Consultant http://www.elinux.com.sg
michael@elinux.com.sg Tel: (65) 227 6180
Fax: (65) 227 5808
----------------------------------------------------------
[-- Attachment #2: Card for Michael Boman --]
[-- Type: text/x-vcard, Size: 394 bytes --]
begin:vcard
n:Boman;Michael
tel;cell:+65 9855 1734
tel;fax:+65 227 5808
tel;work:+65 227 6180
x-mozilla-html:FALSE
url:http://www.elinux.com.sg
org:eLinux Pte Ltd;Technical Division
version:2.1
email;internet:michael@elinux.com.sg
title:Technical Consultant
adr;quoted-printable:;;3 Shenton Way=0D=0A#22-09 Shenton House;Singapore;;068805;Singapore
x-mozilla-cpt:;0
fn:Michael Boman
end:vcard
next reply other threads:[~2000-12-06 9:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-06 9:43 Michael Boman [this message]
2000-12-06 14:20 ` [linux-lvm] WebMin LVM module development Heinz J. Mauelshagen
2000-12-06 18:49 ` [linux-lvm] " Luca Berra
2000-12-06 19:02 ` Steven Lembark
2000-12-07 17:21 ` [linux-lvm] lvm 0.9 + raid (Was: WebMin LVM module development) Luca Berra
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=3A2E0A5B.2EB3CCEB@elinux.com.sg \
--to=michael@elinux.com.sg \
--cc=laurence@elinux.com.sg \
--cc=linux-lvm@msede.com \
--cc=linux-lvm@sistina.com \
--cc=linux-raid@vger.kernel.org \
--cc=webmin-l@webmin.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