From: vincent_kuo@sercomm.com
To: Linux-LVM@sistina.com
Subject: [linux-lvm] Can't create the Logical Volume in my system
Date: Wed Nov 28 03:08:01 2001 [thread overview]
Message-ID: <48256B12.00325F26.00@mail.sercomm.com.tw> (raw)
[-- Attachment #1: Type: text/plain, Size: 3745 bytes --]
Dear sir,
I am trying the current version of LVM on my machine. I download the
lvm-1.0.1-rc4.tar.gz file from the FTP site. But I can't create any Logical
Volume on my machine. So I need your help. Thanks.
My H/W information is:
VIA Socket7 motherboard with VT82C686A, VT8501 chip
CPU Cyrix MII-333
RAM 192MB
HDD x 3 = hda 40GB (hda1=2G, hda5=rest size, hda6=64 swap)
hdc 20GB (hdc1=2G, hdc2=2G, hdc3=2G, hdc5=128 swap, hdc6=5G,
hdc7=5G, hdc8=rest size)
hdd 40GB (hdd1=200MB, hdd5=rest size, hdd6=32 swap)
FileSystem XFS V1.0.1 on HDA, EXT2 on HDC and HDD.
My OS and Software..:
Red Hat Linux 7.1 with Kernel 2.4.10 (with XFS patches)
My testing procedure:
1. ./configure --with-kernel_dir=/usr/src/linux-2.4
2. cd PATCHES, make
3. cd /usr/src/linux-2.4
3. patch -p1 < lvm-1.0.1=rc4-2.4.10-xfs.patch
4. Configure the Kernel with LVM as Module (and RAID + linear, because
I don't want to test the Software RAID now) There ever happen the Makefile
patched during this procedure. (drivers/md/Makefile has already got "lvm-fs.o"
line before the patch)
5. make bzImage, make modules, make modules_install, change lilo...
6. make, make install (LVM tool and library)
7. reboot
8. Change the partition ID by FDISK (83 Linux Native-> 8e Linux LVM)
on /dev/hdc3, /dev/hdc8, /dev/hdd1
9. pvcreate /dev/hdc3, pvcreate /dev/hdc8 --> OK
10. vgcreate MyVG01 /dev/hdc3, vgcreate MyVG02 /dev/hdc8 --> OK
The result of "vgdisplay" is: (See attached file: VolumeGroup)
11. vgchange -ay MyVG01, vgchange -ay MyVG02 --> OK
12. lvcreate -L 2G -n HDD01 MyVG01 --> core dump
13. lvcreate -L 2G -n HDD02 MyVG02 --> core dump
14. What ever I do (changing the LV size or deactive/active the VG,
format the partition....), it always display core dump.
15. The result of "pvdisplay" are: (See attached file:
PhysicalVolume02)(See attached file: PhysicalVolume01)
I don't know what's wrong with my LVM. Did I make any mistake during the
kernel or tool build procedure? Or I can't use XFS or EXT2 filesystem. I ever
combine 2 partitions into one VolumeGroup, it still got "core dump". I plan to
use LVM in a couple of weeks in all of my machine. So this procedure is my first
try. Please tell me how to fix it (or what's wrong)?
By the way, the "lvcreate -d ...." will dump a lots of messages but I can't
pipeline into a text file. The last few line are like below:
............
<7777777> lvm_get_Device_type called
<7777777> lvm_get_Device_Type leaving with 0
<666666> lvm_check_partition_dev -- LEAVING with ret: TRUE
<55555> lvm_check_dev -- LEAVING with ret: 1
<55555> pv_check_new -- CALLED
<55555> pv_check_new -- LEAVING with ret: 0
<4444> pv_check_consistency -- LEAVING with ret: 0
<333> lv_check_on_pv -- LEAVING with ret: 1
<22> pv_reserve_pe -- EAVING with ret: 0
<1> lv_setup_for_create -- pv_reserve_pe returned: 0 pe_last: 13 pe:0
<1> lv_setup_for_create -- pe: 0
<1> lv_setup_for_create 00 LEAVING with ret: 0
<1> lvm_dont_interrupt -- CALLED
<1> lvm_dont_interrupt -- LEAVING
Segmentation fault (core dumped)
I wish they are helpful. (Also, I haven't mount any filesystem that they
are not on hda. So HDC and HDD are definitely un-mounted.)
Regards,
--
Vincent C. Kuo
vincent_kuo@sercomm.com
---- ---- ---- ---- ---- ---- ---- ---- ---- ----
Take a little time, I will be your friend. ^-^
---- ---- ---- ---- ---- ---- ---- ---- ---- ----
[-- Attachment #2: VolumeGroup --]
[-- Type: application/octet-stream, Size: 1085 bytes --]
--- Volume group ---
VG Name MyVG01
VG Access read/write
VG Status available/resizable
VG # 0
MAX LV 255
Cur LV 0
Open LV 0
MAX LV Size 255.99 GB
Max PV 255
Cur PV 1
Act PV 1
VG Size 2.00 GB
PE Size 4.00 MB
Total PE 512
Alloc PE / Size 0 / 0
Free PE / Size 512 / 2.00 GB
VG UUID UUWX05-T9CB-HQG1-erPE-6cog-zOoc-XHZR9p
--- Volume group ---
VG Name MyVG02
VG Access read/write
VG Status available/resizable
VG # 1
MAX LV 255
Cur LV 0
Open LV 0
MAX LV Size 255.99 GB
Max PV 255
Cur PV 1
Act PV 1
VG Size 4.00 GB
PE Size 4.00 MB
Total PE 1024
Alloc PE / Size 0 / 0
Free PE / Size 1024 / 4.00 GB
VG UUID Cl4rXM-GMCW-QAZA-tAWv-xEI1-y9Rb-MOitJ1
[-- Attachment #3: PhysicalVolume02 --]
[-- Type: application/octet-stream, Size: 431 bytes --]
--- Physical volume ---
PV Name /dev/hdc8
VG Name MyVG02
PV Size 4.01 GB / NOT usable 6.51 MB [LVM: 128.00 KB]
PV# 1
PV Status NOT available
Allocatable yes
Cur LV 0
PE Size (KByte) 4096
Total PE 1024
Free PE 1024
Allocated PE 0
PV UUID DG8j3y-e1Nr-UZM9-Aj3n-YRP0-KATF-taTCwA
[-- Attachment #4: PhysicalVolume01 --]
[-- Type: application/octet-stream, Size: 429 bytes --]
--- Physical volume ---
PV Name /dev/hdc3
VG Name MyVG01
PV Size 2.01 GB / NOT usable 7.19 MB [LVM: 126.00 KB]
PV# 1
PV Status NOT available
Allocatable yes
Cur LV 0
PE Size (KByte) 4096
Total PE 512
Free PE 512
Allocated PE 0
PV UUID Mi3X2I-Xrmt-4NLw-zQ0w-XXLW-h8qT-5wWvsG
next reply other threads:[~2001-11-28 3:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-28 3:08 vincent_kuo [this message]
2001-11-28 3:39 ` [linux-lvm] Can't create the Logical Volume in my system Tom Brown
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=48256B12.00325F26.00@mail.sercomm.com.tw \
--to=vincent_kuo@sercomm.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