Are Logical Volumes In LVM Separte From Each Other, Like A Partition?

Even though they are on the same Volume Group?

I'm still having a hard time understanding this.

Let's say for example, that I have the following:

Code:
# df -ha

VolGroup00/LogVol2     /tmp

VolGroup00/LogVol5     /opt

VolGroup00/LogVol3     /var

I have three different Logical Volumes where /tmp, /opt and /var live. Are these separate like a partition that one would place on a physical disk?

Keep in mind that they all are on the same Volume Group as well?

Similar Content

How To Convert Logical Partition To Primary?
Vgchange -an Command Fail To Work To Inactive VG || Umount Logical Volume Succesfull
New To LVM, How To Bridge Between /dev/sd* And /dev/mapper/vol Group/log Vol?
Duplicate VG Names And Missing Devices
LVM / Device Mapper
?? How To Auto Mount Logical Volume Before Transmission-daemon Starts At Start Up
Virtual CentOS 6.4 Server Expand Disk For Splunk Instance
Resize LVM Partitions
Xubuntu MBR Partioning Question
Doesn't Contain A Valid Partition Table? Working For Months...

How To Convert Logical Partition To Primary?

hello,

i am using slackware 14.1 and my partition table is given below
Code:
 sda1                    Primary   ext4                             60003.42 
    sda2                    Primary   swap                              8998.46
    sda3                    Primary   ext4                            119998.61
                            Logical   Free Space                           0.10*
    sda5        NC          Logical   Linux                           120739.34*
    sda6        NC          Logical   ntfs                            190356.39*
                            Logical   Free Space                          11.56

and i want to change Code:
sda5        NC          Logical   Linux                           120739.34*

Logical to primary partition.i don't know how to do it.i searched over internet but i can't understand could u any body please guide me how to do it.Thanks in advance.

Vgchange -an Command Fail To Work To Inactive VG || Umount Logical Volume Succesfull

Hi All,

umounted all logical volume of tomcatvg successfully.But when tried to deactive Volume group using vgchange command show logical volume are in active state .Need help how to force de-active Volume group .


Actioned perfomed
================
vgchange -an tomcatvg


[root@porsche ~]# vgs
VG #PV #LV #SN Attr VSize VFree
tomcatvg 1 10 0 wz--n- 95.38g 8.88g


[root@porsche ~]# cat /etc/fstab | grep -i fs_opt_tomcat
/dev/tomcatvg/fs_opt_tomcat /opt/tomcat ext4 defaults 1 2
[root@porsche ~]#

fuser -km /opt/tomcat
umount /opt/tomcat

Still I could find logical volume in active state

[root@porsche ~]# lvs | grep -i appvg
fs_opt_tomcat tomcatvg -wi-ao---- 5.00g

Regards
Arun

New To LVM, How To Bridge Between /dev/sd* And /dev/mapper/vol Group/log Vol?

So LVM has taken me by surprise, especially working with all of these virtual servers.

I have Linux servers in VMWare, and I know how to grow hard disks there and how they are tied back to /dev/sd*, however what I'm not sure about is how do I know what Volume Group and Logical Volume they are tied too?

If I isssue df -ha I can see where the various partitions are tied to /dev/mapper/Vol Group/Logical Vol

and I issue fdisk -l and I can see the space and what is tied to /dev/sd*, however how do I tie to two together so I know who has what space and how to grow or shrink that space?

I found an older thread he

http://www.linuxquestions.org/questi...ds-for-699073/

However I still don't understand how to bridge between the two.

thanks

Duplicate VG Names And Missing Devices

This has to deal with ubuntu server, but I'm a Linux newbie. Basically talk to me like I'm an 8 year old.

I have a home linux server running Ubuntu server 14.04.2. A few months ago I ran into some trouble with it and long story short only one of the original drives remains and there are two new ones. I'm having a hard time accessing and mounting the logical volumes on the original drive. I'm having issues with the fact that have have volume groups with the same name, as well as missing devices.

Code:
mike@server:~$ lsblk
NAME                             MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda                                8:0    0   1.8T  0 disk
└─sda3                             8:3    0   1.8T  0 part
sdb                                8:16   0 111.8G  0 disk
├─sdb1                             8:17   0   243M  0 part /boot
├─sdb2                             8:18   0     1K  0 part
└─sdb5                             8:21   0 111.6G  0 part
  ├─server--vg-root (dm-2)       252:2    0  43.4G  0 lvm  /
  └─server--vg-swap_1 (dm-3)     252:3    0   3.2G  0 lvm  [SWAP]
sdc                                8:32   0   1.8T  0 disk
├─server--vg-PrivateMedia (dm-0) 252:0    0  1000G  0 lvm
└─server--vg-PublicMedia (dm-1)  252:1    0   750G  0 lvm

The current boot drive is a 120gb ssd, sdb. sda is a blank 2TB drive that I plan on allocating as necessary to logical volumes. sdc is the has the logical volumes I would like to access.

Code:
mike@server:~$ sudo pvdisplay
  WARNING: Duplicate VG name server-vg: Existing 7MjKjV-5R7c-Qnj1-f3Wh-FR3h-lbom-H4ZEMt (created here) takes precedence over pyCHBp-1KjX-FdhK-hT1V-15uP-7GDn-A1hSRj
  Couldn't find device with uuid QJxFW4-777H-shDs-C2QH-1gWo-Pb0d-56BLPs.
  Couldn't find device with uuid LxIoum-Zjvg-WZ4i-vO8c-ib4O-ldwI-G82TsZ.
  WARNING: Duplicate VG name server-vg: Existing 7MjKjV-5R7c-Qnj1-f3Wh-FR3h-lbom-H4ZEMt (created here) takes precedence over pyCHBp-1KjX-FdhK-hT1V-15uP-7GDn-A1hSRj
  --- Physical volume ---
  PV Name               unknown device
  VG Name               server-vg
  PV Size               465.02 GiB / not usable 2.00 MiB
  Allocatable           yes
  PE Size               4.00 MiB
  Total PE              119045
  Free PE               119045
  Allocated PE          0
  PV UUID               QJxFW4-777H-shDs-C2QH-1gWo-Pb0d-56BLPs

  --- Physical volume ---
  PV Name               /dev/sdc
  VG Name               server-vg
  PV Size               1.82 TiB / not usable 1.09 MiB
  Allocatable           yes
  PE Size               4.00 MiB
  Total PE              476932
  Free PE               28932
  Allocated PE          448000
  PV UUID               t1291H-bZqa-8ksX-qYDg-Jix6-CmC3-tVR0qX

  --- Physical volume ---
  PV Name               unknown device
  VG Name               server-vg
  PV Size               465.02 GiB / not usable 2.00 MiB
  Allocatable           yes
  PE Size               4.00 MiB
  Total PE              119045
  Free PE               119045
  Allocated PE          0
  PV UUID               QJxFW4-777H-shDs-C2QH-1gWo-Pb0d-56BLPs

  --- Physical volume ---
  PV Name               /dev/sdb5
  VG Name               server-vg
  PV Size               111.55 GiB / not usable 4.00 MiB
  Allocatable           yes
  PE Size               4.00 MiB
  Total PE              28556
  Free PE               16636
  Allocated PE          11920
  PV UUID               ad5UcZ-E7s6-SPg5-RUqL-qitV-qJ5t-XHFr0Q

I've tried vgrename and vgreduce to no avail. I'm not really sure what else I can do. Any help would be greatly appreciated.

LVM / Device Mapper

Hello,
We have been having a nightmare of a time with a crash on one of our file shares.

We finally were able to recover the logical volume group and get the path to return. However it appears its mapping is off.

dmsetup status
vg_flood-sff_sha
vg_os-lv_tmp: 0 10485760 linear
vg_os-lv_usr: 0 20971520 linear
vg_os-lv_var: 0 10485760 linear
vg_os-lv_opt: 0 41943040 linear
vg_os-lv_swap: 0 16777216 linear
vg_os-lv_root: 0 10485760 linear


dm6 I would guess is where /dev/mapper/vg_flood-sff_share needs to be mapped to, as it is the only one without mapping. As you can see dmsetup also shows this logical volume as different than the rest.

I am trying to figure out how to fix the mapping for this so that I can activate the logical volume and get our data back.

?? How To Auto Mount Logical Volume Before Transmission-daemon Starts At Start Up

I have been using an old computer to download my torrents and this has been my usual routine:

1. Press the power button.
2. Connect to the computer through Putty
3. Log in
4. Gain su privileges

Startup Commands:
Code:
/etc/init.d/transmission-daemon stop
apt-get update
mount -t ext4 /dev/vgTransmission/lvTransmission /mnt/transmissionVault
/etc/init.d/transmission-daemon start

Shutdown Commands:
Code:
/etc/init.d/transmission-daemon stop
umount /dev/vgTransmission/lvTransmission
shutdown -h now

I was wondering if there is a way to configure a computer to automatically mount a logical volume “before” the transmission-daemon starts at boot up (note my first Startup Command).

I think the instructions here are related to what I want to do, but I want to get some advice before I attempt to do anything dangerous:
http://tille.garrels.be/training/tld...#sect_04_02_04


My perfect scenario would be:

Startup Routine:
1. Send WakeOnLan magic packet to computer to turn it on.
2. Computer boots up, mounts the transmissionVault logical volume
3. Wait 10 seconds to ensure that the logical volume has finished mounting
4. Start transmission-daemon

Shutdown Routine:
Send WakeOnLan magic packet to turn off computer, i.e.: Execute “shutdown -h now”
The shutdown command should include:
1. Stop transmission-daemon
2. Wait 10 seconds to ensure that transmission-daemon has finished shutting down
3. Umount transmissionVault logical volume




Recently the Ethernet port of my transmission box has stopped working, so I went ahead and swapped the motherboard with another old motherboard, added a few hard drives, installed a fresh copy of Debian, and re-created the LVM logical volume for transmissionVault. I pretty much have a fairly stock system running at the moment.

Running a headless 3.2.0-4-amd64

Virtual CentOS 6.4 Server Expand Disk For Splunk Instance

As I'm sure there are other posts for this, I'm terrified to mess with disks in Linux as I'm very green. I've looked at one other post which suggests to run the following so I'm going to do the same. The drive provisioned originally had 400 gb, but currently has 500 gb allocated in vmware. Thanks so much in advance!

Code:
fdisk -l
pvs
vgs
lvs
df -h


Code:
[root@uspk10splunk ~]# fdisk -l

Disk /dev/sda: 8589 MB, 8589934592 bytes
64 heads, 32 sectors/track, 8192 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000c255c

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           2         501      512000   83  Linux
Partition 1 does not end on cylinder boundary.
/dev/sda2             502        8192     7875584   8e  Linux LVM
Partition 2 does not end on cylinder boundary.

Disk /dev/sdb: 536.9 GB, 536870912000 bytes
255 heads, 63 sectors/track, 65270 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x69437664

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1       52216   419424988+  8e  Linux LVM

Disk /dev/mapper/vg_uspk10vsp03-lv_root: 3833 MB, 3833593856 bytes
255 heads, 63 sectors/track, 466 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


Disk /dev/mapper/vg_uspk10vsp03-lv_swap: 4227 MB, 4227858432 bytes
255 heads, 63 sectors/track, 514 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


Disk /dev/mapper/vg_opt-lv_opt: 429.5 GB, 429488340992 bytes
255 heads, 63 sectors/track, 52215 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Code:
[root@uspk10splunk ~]# pvs
  PV         VG             Fmt  Attr PSize   PFree
  /dev/sda2  vg_uspk10vsp03 lvm2 a--    7.51g    0
  /dev/sdb1  vg_opt         lvm2 a--  399.99g    0

Code:
[root@uspk10splunk ~]# vgs
  VG             #PV #LV #SN Attr   VSize   VFree
  vg_opt           1   1   0 wz--n- 399.99g    0
  vg_uspk10vsp03   1   2   0 wz--n-   7.51g    0

Code:
[root@uspk10splunk ~]# lvs
  LV      VG             Attr      LSize   Pool Origin Data%  Move Log Cpy%Sync                     Convert
  lv_opt  vg_opt         -wi-ao--- 399.99g                                                          
  lv_root vg_uspk10vsp03 -wi-ao---   3.57g                                                          
  lv_swap vg_uspk10vsp03 -wi-ao---   3.94g

Code:
[root@uspk10splunk ~]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/vg_uspk10vsp03-lv_root
                      3.6G  1.5G  1.9G  45% /
tmpfs                 1.9G     0  1.9G   0% /dev/shm
/dev/mapper/vg_opt-lv_opt
                      394G  374G  422M 100% /opt
/dev/sda1             485M   32M  428M   7% /boot

Resize LVM Partitions

UPDATED:
I installed a Deb 7 Srv w LVM w following partitions:
The end product should become a mail server (Citadel) and in time also a Web server.
Code:
 df -hT 
Filesystem                Type      Size  Used Avail Use% Mounted on
rootfs                    rootfs    322M  141M  165M  46% /
udev                      devtmpfs   10M     0   10M   0% /dev
tmpfs                     tmpfs     100M  260K  100M   1% /run
/dev/mapper/deb--srv-root ext4      322M  141M  165M  46% /
tmpfs                     tmpfs     5,0M     0  5,0M   0% /run/lock
tmpfs                     tmpfs     200M     0  200M   0% /run/shm
/dev/sda1                 ext2      228M   18M  199M   9% /boot
/dev/mapper/deb--srv-home ext4      233G  188M  221G   1% /home
/dev/mapper/deb--srv-tmp  ext4      368M   11M  339M   3% /tmp
/dev/mapper/deb--srv-usr  ext4      8,3G  481M  7,4G   6% /usr
/dev/mapper/deb--srv-var  ext4      2,8G  236M  2,4G   9% /var

 fdisk -l 
Disk /dev/sda: 268.4 GB, 268435456000 bytes
255 heads, 63 sectors/track, 32635 cylinders, total 524288000 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: 0x00064033

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *        2048      499711      248832   83  Linux
/dev/sda2          501758   524285951   261892097    5  Extended
/dev/sda5          501760   524285951   261892096   8e  Linux LVM

Disk /dev/mapper/deb--srv-root: 348 MB, 348127232 bytes
255 heads, 63 sectors/track, 42 cylinders, total 679936 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: 0x00000000

Disk /dev/mapper/deb--srv-root doesn't contain a valid partition table

Disk /dev/mapper/deb--srv-swap_1: 2143 MB, 2143289344 bytes
255 heads, 63 sectors/track, 260 cylinders, total 4186112 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: 0x00000000

Disk /dev/mapper/deb--srv-swap_1 doesn't contain a valid partition table

Disk /dev/mapper/deb--srv-usr: 8996 MB, 8996782080 bytes
255 heads, 63 sectors/track, 1093 cylinders, total 17571840 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: 0x00000000

Disk /dev/mapper/deb--srv-usr doesn't contain a valid partition table

Disk /dev/mapper/deb--srv-var: 2998 MB, 2998927360 bytes
255 heads, 63 sectors/track, 364 cylinders, total 5857280 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: 0x00000000

Disk /dev/mapper/deb--srv-var doesn't contain a valid partition table

Disk /dev/mapper/deb--srv-tmp: 398 MB, 398458880 bytes
255 heads, 63 sectors/track, 48 cylinders, total 778240 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: 0x00000000

Disk /dev/mapper/deb--srv-tmp doesn't contain a valid partition table

Disk /dev/mapper/deb--srv-home: 253.3 GB, 253289824256 bytes
255 heads, 63 sectors/track, 30794 cylinders, total 494706688 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: 0x00000000

Disk /dev/mapper/deb--srv-home doesn't contain a valid partition table

 pvs 
PV         VG      Fmt  Attr PSize   PFree
/dev/sda5  deb-srv lvm2 a--  249,76g    0

 lvs 
LV     VG      Attr     LSize   Pool Origin Data%  Move Log Copy%  Convert
home   deb-srv -wi-ao-- 235,89g
root   deb-srv -wi-ao-- 332,00m
swap_1 deb-srv -wi-ao--   2,00g
tmp    deb-srv -wi-ao-- 380,00m
usr    deb-srv -wi-ao--   8,38g
var    deb-srv -wi-ao--   2,79g

Now i want to _shrink_ the HOME partition so I can expand my VAR partition. Looked for guides but haven't found any site useful so far

I tried to find a way to do it when I installed it but it didn't seem to offer me this at this time even I looked around for a while.

How do I do this shrinking of HOME and extending of VAR partition??
please be fairly specific as Im not a pro yet

Xubuntu MBR Partioning Question

I was wondering if I can repair my current partitioning setup using gparted, or if I should just reload Xubuntu. Basically I screwed up by making the primary partition only 256M, and made a massive extended logical partition for everything else, and did not leave swap space. I am doing this on an older PC with MBR, dual processor, 2G RAM each processor, 160GB hard drive space. It is single boot, no Windows. I would like the partioning to be as follows, leaving empty disk space for other Linux flavors:

/ 13GB ext4
/home 50GB ext4
swap 8GB swap

sudo parted /dev/sda print all
Code:
Model: ATA ST3160812AS (scsi)
Disk /dev/sda: 160GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start   End    Size   Type      File system  Flags
 1      1049kB  256MB  255MB  primary   ext2         boot
 2      257MB   160GB  160GB  extended
 5      257MB   160GB  160GB  logical
                                                                       
Error: /dev/mapper/xubuntu--vg-swap_1: unrecognised disk label

Model: Linux device-mapper (linear) (dm)
Disk /dev/mapper/xubuntu--vg-root: 158GB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number  Start  End    Size   File system  Flags
 1      0.00B  158GB  158GB  ext4
                                                                          
Error: /dev/mapper/sda5_crypt: unrecognised disk label

df -hT
Code:
Filesystem                   Type      Size  Used Avail Use Mounted on
/dev/mapper/xubuntu--vg-root ext4      145G  6.5G  131G   5% /
none                         tmpfs     4.0K     0  4.0K   0% /sys/fs/cgroup
udev                         devtmpfs  989M  4.0K  989M   1% /dev
tmpfs                        tmpfs     201M  1.1M  200M   1% /run
none                         tmpfs     5.0M     0  5.0M   0% /run/lock
none                         tmpfs    1003M   88K 1003M   1% /run/shm
none                         tmpfs     100M   24K  100M   1% /run/user
/dev/sda1                    ext2      236M  120M  104M  54% /boot
/home/mbrk/.Private          ecryptfs  145G  6.5G  131G   5% /home/mbrk

Doesn't Contain A Valid Partition Table? Working For Months...

Everything is working great on this server, however I am seeing Disk doesn't contain a valid partition table. I have no issue reading and writing, this something that can be ignored?


Disk /dev/xvda: 32.2 GB, 32212254720 bytes
255 heads, 63 sectors/track, 3916 cylinders, total 62914560 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: 0x00000000

Device Boot Start End Blocks Id System
/dev/xvda1 * 16065 62910539 31447237+ 83 Linux

Disk /dev/xvdf: 1099.5 GB, 1099511627776 bytes
255 heads, 63 sectors/track, 133674 cylinders, total 2147483648 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: 0x00000000

Disk /dev/xvdf doesn't contain a valid partition table

Disk /dev/xvdh: 1099.5 GB, 1099511627776 bytes
255 heads, 63 sectors/track, 133674 cylinders, total 2147483648 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: 0x00000000

Disk /dev/xvdh doesn't contain a valid partition table

Disk /dev/xvdg: 1099.5 GB, 1099511627776 bytes
255 heads, 63 sectors/track, 133674 cylinders, total 2147483648 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: 0x00000000

Disk /dev/xvdg doesn't contain a valid partition table

Disk /dev/xvdi: 1099.5 GB, 1099511627776 bytes
255 heads, 63 sectors/track, 133674 cylinders, total 2147483648 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: 0x00000000

Disk /dev/xvdi doesn't contain a valid partition table

Disk /dev/mapper/vgebs-lvebs: 4398.0 GB, 4398029733888 bytes
255 heads, 63 sectors/track, 534696 cylinders, total 8589901824 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 2097152 bytes / 4194304 bytes
Disk identifier: 0x00000000

Disk /dev/mapper/vgebs-lvebs doesn't contain a valid partition table

Disk /dev/xvdj: 32.2 GB, 32212254720 bytes
255 heads, 63 sectors/track, 3916 cylinders, total 62914560 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: 0x00000000

Disk /dev/xvdj doesn't contain a valid partition table