Tim, Based on my experience with LVM, you have to run vgscan _before_ you run pvcreate. Take a look at the Distributions Redbook, section 17.3.1.
I suspect that if you re-do the pvcreate step, and then the vgcreate, you should be OK. Mark Post -----Original Message----- From: Tim-Chr. Hanschen [mailto:[EMAIL PROTECTED]] Sent: Friday, November 22, 2002 7:41 AM To: [EMAIL PROTECTED] Subject: Antwort: AW: problem with mkfs THX.... fdasd worked fine. Now I have a problem with LVM.... I created a physical volume and wanted to create a volume group as well. fine. No errors. When I do a vgscan I get the followuing result: / # vgscan vgscan -- reading all physical volumes (this may take a while...) vgscan -- found active volume group "test" vgscan -- ERROR "lv_read_all_lv(): number of LV" can't get data of volume group "test" from physical volume(s) vgscan -- ERROR "lv_read_all_lv(): number of LV" creating "/etc/lvmtab" and "/etc/lvmtab.d" I am using LVM 0.9.1_beta7 Any ideas? thx, - Tim - Rene Wiedewilt <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 22.11.2002 12:19:17 Bitte antworten an Linux on 390 Port <[EMAIL PROTECTED]> Gesendet von: Linux on 390 Port <[EMAIL PROTECTED]> An: [EMAIL PROTECTED] Kopie: Thema: AW: problem with mkfs before making the fs you have to make a partition with fdasd -a /dev/dasds gru� rene -----Urspr�ngliche Nachricht----- Von: Tim-Chr. Hanschen [mailto:[EMAIL PROTECTED]] Gesendet: Freitag, 22. November 2002 12:01 An: [EMAIL PROTECTED] Betreff: problem with mkfs Hello, I tried to format a DASD (CDL) and run into the following problem. I am using SLES7.2 (kernel 2.4.17), s390-tools-1.1.4 and e2fsprogs-1.23-2. First off all I used dasdfmt: dasdfmt -f /dev/dasds -b 4096 After that I tried to create an ext2 filesystem mke2fs /dev/dasds1 -b 4096 and got the following error: / # mke2fs /dev/dasds1 -b 4096 mke2fs 1.23, 15-Aug-2001 for EXT2 FS 0.5b, 95/08/09 mke2fs: Device size reported to be zero. Invalid partition specified, or partition table wasn't reread after running fdisk, due to a modified partition being busy and in use. You may need to reboot to re-read your partition table. What is the problem? regards, - Tim -
