Suse Linux LVM Issue

SUSE Linux Enterprise Server SLES Configure-Administer
1

Disk /dev/sdb: 11.8 GB, 11811160064 bytes
245 heads, 25 sectors/track, 3766 cylinders, total 23068672 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x13cce3b6
Device Boot Start End Blocks Id System
/dev/sdb1 2048 23068671 11533312 8e Linux LVM

linux-wmdh:/dev # vgcreate VGncs /dev/sdb1
Volume group “VGncs” successfully created
linux-wmdh:/dev # lvcreate -L+5GB -n LVdata1 VGncs

linux-wmdh:/dev # lvdisplay

— Logical volume —
LV Name /dev/VGncs/LVdata1
VG Name VGncs
LV UUID 8xnsdD-b9Iv-uff0-eOf6-D0BK-loT6-Qe56iT
LV Write Access read/write
LV Creation host, time linux-wmdh, 2014-05-11 10:48:14 -0400
LV Status available

open 0

LV Size 5.00 GiB
Current LE 1280
Segments 1
Allocation inherit
Read ahead sectors auto

  • currently set to 1024
    Block device 253:0
    linux-wmdh:/dev # mke2fs -j /dev/VGncs/LVdata1
    mke2fs 1.41.9 (22-Aug-2009)
    Filesystem label=
    OS type: Linux
    Block size=4096 (log=2)
    Fragment size=4096 (log=2)
    327680 inodes, 1310720 blocks
    65536 blocks (5.00%) reserved for the super user
    First data block=0
    Maximum filesystem blocks=1342177280
    40 block groups
    32768 blocks per group, 32768 fragments per group
    8192 inodes per group
    Superblock backups stored on blocks:
    32768, 98304, 163840, 229376, 294912, 819200, 884736
    Writing inode tables: done
    Creating journal (32768 blocks): done
    Writing superblocks and filesystem accounting information: done
    This filesystem will be automatically checked every 35 mounts or
    180 days, whichever comes first. Use tune2fs -c or -i to override.
    linux-wmdh:/dev # mount /dev/VGncs/LVdata1 /data1
    linux-wmdh:/dev #
    linux-wmdh:/dev # df -h
    Filesystem Size Used Avail Use% Mounted on
    /dev/sda2 48G 3.8G 42G 9% /
    udev 1001M 160K 1001M 1% /dev
    tmpfs 1001M 76K 1001M 1% /dev/shm
    /dev/mapper/VGncs-LVdata1 5.0G 139M 4.6G 3% /data1
    linux-wmdh:/dev # partprobe
    linux-wmdh:/dev # ls -l /dev/VGncs/LVdata1
    lrwxrwxrwx 1 root root 7 May 11 11:04 /dev/VGncs/LVdata1 → …/dm-0
    linux-wmdh:/dev #

Now everything looks good. but when i reboot, block deivice is missing.
could someone help me, if i am doing something wrong or missing some steps to create linux LVM
Running Suse 11 SP3 in vmware workstation

[COLOR="#0000CD"] linux-wmdh:~/Desktop # ls -l /dev/VGncs/LVdata1
ls: cannot access /dev/VGncs/LVdata1: No such file or directory
linux-wmdh:~/Desktop #
linux-wmdh:~/Desktop # ls -l /dev/dm-0
ls: cannot access /dev/dm-0: No such file or directory
linux-wmdh:~/Desktop # [/COLOR]
could someone help me on this. Thanks in Advance

2

Hi ,
please have a look at /etc/sysconfig/lvm: LVM_ACTIVATED_ON_DISCOVERED is probably still at the default value of “disabled” and you PV is not available at boot time.

Does running “vgchange -ay VGncs” activate the VG, once the system has booted? What type of device is /dev/sdb - some SAN resource or DRBD device, activated after boot?

Regards,
Jens