[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

[linux-lvm] Problems with lvm2 / devive mapper



Hello everbody,

i'm having problems setting up lvm2.

creating a a new vg works fine:

	pvcreate /dev/sdb1 /dev/sdc1
	vgcreate -s 64M vgEQ51fs /dev/sdc1 /dev/sdb1

but lvcreate 

	lvcreate -n lvsapdbQ51sapdata -L 100G vgEQ51fs

rises this dmesg output:

	hgesst40:~ # dmesg | tail -n 10
	eth0: no IPv6 routers present
	bond0: no IPv6 routers present
	mtrr: type mismatch for d0000000,1000000 old: uncachable new: write-combining
	device-mapper: : dm-linear: Device lookup failed
	device-mapper: error adding target to table
	device-mapper: : dm-linear: Device lookup failed
	device-mapper: error adding target to table

doing an mkfs.xfs produces this failure:

	hgesst40:~ # mkfs.xfs /dev/vgEQ51fs/lvsapdbQ51sapdata
	can't get size of data subvolume
	Usage: mkfs.xfs
	/* blocksize */         [-b log=n|size=num]
	/* data subvol */       [-d agcount=n,agsize=n,file,name=xxx,size=num,
                            (sunit=value,swidth=value|su=num,sw=num),	
	[...]

but lvscan find's the volume:
	hgesst40:~ # lvscan
  		ACTIVE            '/dev/vgEQ51fs/lvsapdbQ51sapdata' [100.00 GB] next free (default)
  		ACTIVE            '/dev/vgOS/lvusrfs' [3.00 GB] next free (default)
	[...]

Here're some info's on the system:
	
	SuSE Linux Enterprise Server 9 (x86_64)
	Service Pack 1
	device-mapper-1.00.19-2.2
	lvm2-2.00.15-0.8
	kernel-smp-2.6.5-7.139
	kernel-smp-2.6.5-7.147
	Linux hgesst40 2.6.5-7.139-smp #1 SMP Fri Jan 14 15:41:33 UTC 2005 x86_64 x86_64 x86_64 GNU/Linux

The kernel -139 is running because it's the latest sap certified kernel.

However, creating an ext2 fs on /dev/sdb1 works fine.

	hgesst40:~ # mke2fs /dev/sdb1
	mke2fs 1.34 (25-Jul-2003)
	Filesystem label=
	OS type: Linux
	Block size=4096 (log=2)
	Fragment size=4096 (log=2)
	26214400 inodes, 52428119 blocks
	2621405 blocks (5.00%) reserved for the super user
	First data block=0
	1600 block groups
	32768 blocks per group, 32768 fragments per group
	16384 inodes per group
	Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
        4096000, 7962624, 11239424, 20480000, 23887872

	Writing inode tables: done
	Writing superblocks and filesystem accounting information: 
	done

	This filesystem will be automatically checked every 27 mounts or
	180 days, whichever comes first.  Use tune2fs -c or -i to override.

has anyone an idea, how to solve this issue?

Mit freundlichem Gruß,



Dirk Laurenz
Systems Engineer	

Fujitsu Siemens Computers
S CE DE SE PS N/O
Sales Central Europe Deutschland 
Professional Service Nord / Ost

Hildesheimer Strasse 25
30880 Laatzen
Germany

Telephone:	+49 (511) 84 89 - 18 08
Telefax:	+49 (511) 84 89 - 25 18 08
Mobile:	+49 (170) 22 10 781
Email:	mailto:dirk laurenz fujitsu-siemens com
Internet:	http://www.fujitsu-siemens.com
            http://www.fujitsu-siemens.de/services/index.html
*******************************************************************************************************************
 


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]