LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Server
User Name
Password
Linux - Server This forum is for the discussion of Linux Software used in a server related context.

Notices


Closed Thread
  Search this Thread
Old 07-05-2012, 07:57 AM   #1
golden_boy615
Member
 
Registered: Dec 2008
Distribution: Ubuntu Fedora
Posts: 445

Rep: Reputation: 18
Recovery of RAID 1 and LVM2 Volume Problem


I have an HDD from a degraded RAID 1 and LVM2 that I want to recover its data but my procedure does not goes as others said:
I have to say that I connect this HDD to another PC with UBUNTU Desktop 10.04.
this is what I did:

Quote:
root@ehsan-laptop:~# fdisk -l /dev/sdb

Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 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: 0x00083088

Device Boot Start End Blocks Id System
/dev/sdb1 1 120378 966929408 83 Linux
/dev/sdb2 120378 121601 9828353 5 Extended
/dev/sdb5 120378 121601 9828352 82 Linux swap / Solaris
root@ehsan-laptop:~# sfdisk -l /dev/sdb

Disk /dev/sdb: 121601 cylinders, 255 heads, 63 sectors/track
Warning: extended partition does not start at a cylinder boundary.
DOS and Linux will interpret the contents differently.
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0

Device Boot Start End #cyls #blocks Id System
/dev/sdb1 0+ 120377- 120378- 966929408 83 Linux
/dev/sdb2 120377+ 121600- 1224- 9828353 5 Extended
/dev/sdb3 0 - 0 0 0 Empty
/dev/sdb4 0 - 0 0 0 Empty
/dev/sdb5 120377+ 121600- 1224- 9828352 82 Linux swap / Solaris
root@ehsan-laptop:~# pvscan
PV /dev/sdb1 lvm2 [922.14 GiB]
Total: 1 [922.14 GiB] / in use: 0 [0 ] / in no VG: 1 [922.14 GiB]
root@ehsan-laptop:~# lvscan
root@ehsan-laptop:~# cat /proc/mdstat
Personalities :
unused devices: <none>
as you see lvscan and cat /proc/mdstat does not show anything so I can not follow the procedure that other says like here
what can I do?

Last edited by golden_boy615; 07-05-2012 at 08:01 AM.
 
Old 07-05-2012, 04:49 PM   #2
unSpawn
Moderator
 
Registered: May 2001
Posts: 29,415
Blog Entries: 55

Rep: Reputation: 3590Reputation: 3590Reputation: 3590Reputation: 3590Reputation: 3590Reputation: 3590Reputation: 3590Reputation: 3590Reputation: 3590Reputation: 3590Reputation: 3590
Aren't you missing the "vgchange -ay" between pvscan and lvscan?
 
Old 07-05-2012, 06:02 PM   #3
golden_boy615
Member
 
Registered: Dec 2008
Distribution: Ubuntu Fedora
Posts: 445

Original Poster
Rep: Reputation: 18
I have to say I did something terrible; I made a new LVM on my previous LVM to access my data . This is my commands chain:

Quote:
2059 pvcreate -ff --uuid fEo2Hs-ntqs-nxPu-Xkbx-HYDp-dduQ-Bc146X /dev/sdc1
2060 pvcreate -ff --uuid fEo2Hs-ntqs-nxPu-Xkbx-HYDp-dduQ-Bc146X1 /dev/sdc1
2061* pvcreate -ff --uuid fEo2Hs-ntqs-nxPu-Xkbx-HYDp-dduQ-Bc1461 /dev/sd1
2062 pvcreate -ff --uuid fEo2Hs-ntqs-nxPu-Xkbx-HYDp-dduQ-Bc146X /dev/sdb1
2063 pvcreate --uuid fEo2Hs-ntqs-nxPu-Xkbx-HYDp-dduQ-Bc146X /dev/sdb1
2064 lvdisplay
2065 pvscan
2066 pvdisplay
2067 vgcreate vol_grp1 /dev/sdb1
2068 vgdisplay
2069 lvcreate -l 20 -n logical_vol1 vol_grp1
2070 lvdisplay
2071 mount -t auto /dev/vol_grp1/logical_vol1 hdd/
2072 mount /dev/vol_grp1/logical_vol1 hdd/
2073 mount -t ext4 /dev/vol_grp1/logical_vol1 hdd/
2074 dmesg | tail
2075 apt-get install mount.ext4
2076 cat /etc/*release
2077 lvscan
2078 lvchange -a y /dev/vol_grp1/logical_vol1
2079 mount -t ext4 /dev/vol_grp1/logical_vol1 hdd/
2080 mount -t ext3 /dev/vol_grp1/logical_vol1 hdd/
2081 mount -t auto /dev/vol_grp1/logical_vol1 hdd/
2082 lvmdiskscan
2083 lvcreate -l 200 -n logical_vol1 vol_grp1
2084 lvremove -h
2085 lvremove /dev/vol_grp1/logical_vol1
2086 man lvcreate
2087 lvmdiskscan
2088 man lvcreate
2089 lvcreate -l 100% -n logical_vol1 vol_grp1
2090 lvcreate -L 922.14G -n logical_vol1 vol_grp1
2091 lvcreate -L 922G -n logical_vol1 vol_grp1
2092 mount -t auto /dev/vol_grp1/logical_vol1 hdd/
2093* lvmdisksc
2094 lvdisplay /dev/vol_grp1/logical_vol1
2095 mount -t auto /dev/vol_grp1/logical_vol1 hdd/
2096 system-config-lvm
2097 apt-get install system-config-lvm
2098 system-config-lvm
2099 mount -t auto /dev/vol_grp1/logical_vol1 hdd/
2100 fdisk -l /dev/sdb1
2101 testdisk
and this is sum of my commands and its output :
Quote:
root@ehsan-laptop:~# cat /etc/*release

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=10.04
DISTRIB_CODENAME=lucid
DISTRIB_DESCRIPTION="Ubuntu 10.04.1 LTS"
root@ehsan-laptop:~# lvscan
ACTIVE '/dev/vol_grp1/logical_vol1' [80.00 MiB] inherit
root@ehsan-laptop:~# lvchange -a y /dev/vol_grp1/logical_vol1
root@ehsan-laptop:~# mount -t ext4 /dev/vol_grp1/logical_vol1 hdd/
mount: wrong fs type, bad option, bad superblock on /dev/mapper/vol_grp1-logical_vol1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

root@ehsan-laptop:~# mount -t ext3 /dev/vol_grp1/logical_vol1 hdd/
mount: wrong fs type, bad option, bad superblock on /dev/mapper/vol_grp1-logical_vol1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

root@ehsan-laptop:~# mount -t auto /dev/vol_grp1/logical_vol1 hdd/
mount: you must specify the filesystem type
root@ehsan-laptop:~# lvmdiskscan
/dev/ram0 [ 64.00 MiB]
/dev/vol_grp1/logical_vol1 [ 80.00 MiB]
/dev/ram1 [ 64.00 MiB]
/dev/sda1 [ 13.67 GiB]
/dev/ram2 [ 64.00 MiB]
/dev/ram3 [ 64.00 MiB]
/dev/ram4 [ 64.00 MiB]
/dev/ram5 [ 64.00 MiB]
/dev/root [ 94.08 GiB]
/dev/ram6 [ 64.00 MiB]
/dev/sda6 [ 4.03 GiB]
/dev/ram7 [ 64.00 MiB]
/dev/ram8 [ 64.00 MiB]
/dev/ram9 [ 64.00 MiB]
/dev/ram10 [ 64.00 MiB]
/dev/ram11 [ 64.00 MiB]
/dev/ram12 [ 64.00 MiB]
/dev/ram13 [ 64.00 MiB]
/dev/ram14 [ 64.00 MiB]
/dev/ram15 [ 64.00 MiB]
/dev/sdb1 [ 922.14 GiB] LVM physical volume
/dev/sdb5 [ 9.37 GiB]
1 disk
20 partitions
0 LVM physical volume whole disks
1 LVM physical volume
root@ehsan-laptop:~# lvcreate -l 200 -n logical_vol1 vol_grp1
Logical volume "logical_vol1" already exists in volume group "vol_grp1"
root@ehsan-laptop:~# lv
lvchange lvcreate lvextend lvmchange lvmdump lvmsar lvremove lvresize lvscan
lvconvert lvdisplay lvm lvmdiskscan lvmsadc lvreduce lvrename lvs
root@ehsan-laptop:~# lvre
lvreduce lvremove lvrename lvresize
root@ehsan-laptop:~# lvremove -h
lvremove: Remove logical volume(s) from the system

lvremove
[-A|--autobackup y|n]
[-d|--debug]
[-f|--force]
[-h|--help]
[--noudevsync]
[-t|--test]
[-v|--verbose]
[--version]
LogicalVolume[Path] [LogicalVolume[Path]...]

root@ehsan-laptop:~# lvremove /dev/vol_grp1/logical_vol1
Do you really want to remove active logical volume logical_vol1? [y/n]: y
Logical volume "logical_vol1" successfully removed
root@ehsan-laptop:~# man lvcreate
root@ehsan-laptop:~# lvmdiskscan
/dev/ram0 [ 64.00 MiB]
/dev/ram1 [ 64.00 MiB]
/dev/sda1 [ 13.67 GiB]
/dev/ram2 [ 64.00 MiB]
/dev/ram3 [ 64.00 MiB]
/dev/ram4 [ 64.00 MiB]
/dev/ram5 [ 64.00 MiB]
/dev/root [ 94.08 GiB]
/dev/ram6 [ 64.00 MiB]
/dev/sda6 [ 4.03 GiB]
/dev/ram7 [ 64.00 MiB]
/dev/ram8 [ 64.00 MiB]
/dev/ram9 [ 64.00 MiB]
/dev/ram10 [ 64.00 MiB]
/dev/ram11 [ 64.00 MiB]
/dev/ram12 [ 64.00 MiB]
/dev/ram13 [ 64.00 MiB]
/dev/ram14 [ 64.00 MiB]
/dev/ram15 [ 64.00 MiB]
/dev/sdb1 [ 922.14 GiB] LVM physical volume
/dev/sdb5 [ 9.37 GiB]
1 disk
19 partitions
0 LVM physical volume whole disks
1 LVM physical volume
root@ehsan-laptop:~# man lvcreate
root@ehsan-laptop:~# lvcreate -l 100% -n logical_vol1 vol_grp1
Invalid argument 100%
Error during parsing of command line.
root@ehsan-laptop:~# lvcreate -L 922.14G -n logical_vol1 vol_grp1
Rounding up size to full physical extent 922.14 GiB
Insufficient free extents (236066) in volume group vol_grp1: 236068 required
root@ehsan-laptop:~# lvcreate -L 922G -n logical_vol1 vol_grp1
Logical volume "logical_vol1" created
root@ehsan-laptop:~# mount -t auto /dev/vol_grp1/logical_vol1 hdd/
mount: you must specify the filesystem type
root@ehsan-laptop:~# lvmdiskscan
/dev/ram0 [ 64.00 MiB]
/dev/vol_grp1/logical_vol1 [ 922.00 GiB]
/dev/ram1 [ 64.00 MiB]
/dev/sda1 [ 13.67 GiB]
/dev/ram2 [ 64.00 MiB]
/dev/ram3 [ 64.00 MiB]
/dev/ram4 [ 64.00 MiB]
/dev/ram5 [ 64.00 MiB]
/dev/root [ 94.08 GiB]
/dev/ram6 [ 64.00 MiB]
/dev/sda6 [ 4.03 GiB]
/dev/ram7 [ 64.00 MiB]
/dev/ram8 [ 64.00 MiB]
/dev/ram9 [ 64.00 MiB]
/dev/ram10 [ 64.00 MiB]
/dev/ram11 [ 64.00 MiB]
/dev/ram12 [ 64.00 MiB]
/dev/ram13 [ 64.00 MiB]
/dev/ram14 [ 64.00 MiB]
/dev/ram15 [ 64.00 MiB]
/dev/sdb1 [ 922.14 GiB] LVM physical volume
/dev/sdb5 [ 9.37 GiB]
1 disk
20 partitions
0 LVM physical volume whole disks
1 LVM physical volume
root@ehsan-laptop:~# ls /dev/d
dahdi/ disk/ dri/ dsp dvd dvdrw
root@ehsan-laptop:~# lvdisplay /dev/vol_grp1/logical_vol1
--- Logical volume ---
LV Name /dev/vol_grp1/logical_vol1
VG Name vol_grp1
LV UUID vqiwcH-tO2Y-ASnY-5Cji-TS66-ebRm-4buDH0
LV Write Access read/write
LV Status available
# open 0
LV Size 922.00 GiB
Current LE 236032
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 252:0

root@ehsan-laptop:~# mount -t auto /dev/vol_grp1/logical_vol1 hdd/
mount: you must specify the filesystem type


root@ehsan-laptop:~# mount -t auto /dev/vol_grp1/logical_vol1 hdd/
mount: you must specify the filesystem type
root@ehsan-laptop:~# fdisk -l /dev/sdb1

Disk /dev/sdb1: 990.1 GB, 990135713792 bytes
255 heads, 63 sectors/track, 120377 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/sdb1 doesn't contain a valid partition table
root@ehsan-laptop:~# testdisk
TestDisk 6.11, Data Recovery Utility, April 2009
Christophe GRENIER <grenier@cgsecurity.org>
http://www.cgsecurity.org
TestDisk exited normally.
root@ehsan-laptop:~#


root@ehsan-laptop:/home/ehan# kpartx -av /dev/vol_grp1/logical_vol1
root@ehsan-laptop:/home/ehan# vgscan
Reading all physical volumes. This may take a while...
Found volume group "vol_grp1" using metadata type lvm2
root@ehsan-laptop:/home/ehan# mount -t auto /dev/vol_grp1/logical_vol1 /root/hdd/
mount: /dev/mapper/vol_grp1-logical_vol1 already mounted or /root/hdd/ busy
root@ehsan-laptop:/home/ehan# ls /root/hdd/
root@ehsan-laptop:/home/ehan# lvdisplay
--- Logical volume ---
LV Name /dev/vol_grp1/logical_vol1
VG Name vol_grp1
LV UUID vqiwcH-tO2Y-ASnY-5Cji-TS66-ebRm-4buDH0
LV Write Access read/write
LV Status available
# open 1
LV Size 922.13 GiB
Current LE 236065
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 252:0

root@ehsan-laptop:/home/ehan# mkfs
mkfs mkfs.cramfs mkfs.ext3 mkfs.ext4dev mkfs.msdos mkfs.reiserfs
mkfs.bfs mkfs.ext2 mkfs.ext4 mkfs.minix mkfs.ntfs mkfs.vfat
root@ehsan-laptop:/home/ehan# mkfs.ext4
mkfs.ext4 mkfs.ext4dev
root@ehsan-laptop:/home/ehan# sfdisk -l /dev/sdb1
Warning: start=2048 - this looks like a partition rather than
the entire disk. Using fdisk on it is probably meaningless.
[Use the --force option if you really want this]
root@ehsan-laptop:/home/ehan# sfdisk -l /dev/sdb

Disk /dev/sdb: 121601 cylinders, 255 heads, 63 sectors/track
Warning: extended partition does not start at a cylinder boundary.
DOS and Linux will interpret the contents differently.
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0

Device Boot Start End #cyls #blocks Id System
/dev/sdb1 0+ 120377- 120378- 966929408 83 Linux
/dev/sdb2 120377+ 121600- 1224- 9828353 5 Extended
/dev/sdb3 0 - 0 0 0 Empty
/dev/sdb4 0 - 0 0 0 Empty
/dev/sdb5 120377+ 121600- 1224- 9828352 82 Linux swap / Solaris
root@ehsan-laptop:/home/ehan# fdisk /dev/sdb

WARNING: DOS-compatible mode is deprecated. It's strongly recommended to
switch off the mode (command 'c') and change display units to
sectors (command 'u').

Command (m for help): ^C
root@ehsan-laptop:/home/ehan# lvs
LV VG Attr LSize Origin Snap% Move Log Copy% Convert
logical_vol1 vol_grp1 -wi-ao 922.13g
root@ehsan-laptop:/home/ehan# vgs
VG #PV #LV #SN Attr VSize VFree
vol_grp1 1 1 0 wz--n- 922.13g 4.00m
root@ehsan-laptop:/home/ehan# mkfs.ext4
mkfs.ext4 mkfs.ext4dev
root@ehsan-laptop:/home/ehan# mkfs.ext4 /dev/vol_grp1/logical_vol1
mke2fs 1.41.11 (14-Mar-2010)
/dev/vol_grp1/logical_vol1 is apparently in use by the system; will not make a filesystem here!
root@ehsan-laptop:/home/ehan# mkfs.ext4 /dev/vol_grp1/logical_vol1
mke2fs 1.41.11 (14-Mar-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
60440576 inodes, 241730560 blocks
12086528 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=0
7378 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, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000, 214990848

Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 28 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
root@ehsan-laptop:/home/ehan# mount -t auto /dev/vol_grp1/logical_vol1 /root/hdd/
root@ehsan-laptop:/home/ehan# ls /root/hdd/
lost+found
Did I completely erase my data ?????????
please help........
 
Old 07-06-2012, 11:39 AM   #4
unSpawn
Moderator
 
Registered: May 2001
Posts: 29,415
Blog Entries: 55

Rep: Reputation: 3590Reputation: 3590Reputation: 3590Reputation: 3590Reputation: 3590Reputation: 3590Reputation: 3590Reputation: 3590Reputation: 3590Reputation: 3590Reputation: 3590
Quote:
Originally Posted by golden_boy615 View Post
I have to say I did something terrible; I made a new LVM on my previous LVM to access my data .
Why the fsck did you do that? If you are unsure why didn't you ask before performing those commands FCOL? And where did you get these commands from? I only told you you were missing a "vgchange -ay" between doing a pvscan and lvscan. (And if you want to access the recovery LV and you already have a standard VG then AFAIK what you should have done is create a separate VG.)


Quote:
Originally Posted by golden_boy615 View Post
Did I completely erase my data ?
Dunno. Can you still access the data? Did you make a backup before you decided to fsck with things?
 
Old 07-07-2012, 12:26 AM   #5
golden_boy615
Member
 
Registered: Dec 2008
Distribution: Ubuntu Fedora
Posts: 445

Original Poster
Rep: Reputation: 18
nooooooooooo there is no back up. How could get backup from a HDD that I could not access it ??? I don't know what to do. I've read that mkfs.ext4 does not erase data it just affect inodes and data should be some where on the HDD but how can I access them.
 
Old 07-07-2012, 04:55 AM   #6
unSpawn
Moderator
 
Registered: May 2001
Posts: 29,415
Blog Entries: 55

Rep: Reputation: 3590Reputation: 3590Reputation: 3590Reputation: 3590Reputation: 3590Reputation: 3590Reputation: 3590Reputation: 3590Reputation: 3590Reputation: 3590Reputation: 3590
Quote:
Originally Posted by golden_boy615 View Post
How could get backup from a HDD that I could not access it ???
As long as the disk (I mean HW) is readable you would with 'dd' or an equivalent.


Quote:
Originally Posted by golden_boy615 View Post
I don't know what to do.
I don't know what you're doing either. And since me posting 'vgchange -ay' makes you go off running all sorts of potentially destructive commands w/o prior consultation this to me means that whatever suggestions are posted either don't register or are ignored anyway.
There's an acronym for that: PEBCAK.
It's not the type of problem I deal with.
 
Old 07-07-2012, 06:46 AM   #7
golden_boy615
Member
 
Registered: Dec 2008
Distribution: Ubuntu Fedora
Posts: 445

Original Poster
Rep: Reputation: 18
I have another HDD of RAID 1 that I've said, But this one does not show anything:
Quote:
root@ubuntu:~# lvdisplay
No volume groups found
root@ubuntu:~# pvdisplay
root@ubuntu:~# vgdisplay
No volume groups found
root@ubuntu:~# parted -l
Error: /dev/sda: unrecognised disk label

Model: hp v225w (scsi)
Disk /dev/sdb: 4041MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number Start End Size Type File system Flags
1 31.7kB 4039MB 4039MB primary fat32 boot, lba


root@ubuntu:~# parted -l /dev/sda
Error: /dev/sda: unrecognised disk label

Model: hp v225w (scsi)
Disk /dev/sdb: 4041MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number Start End Size Type File system Flags
1 31.7kB 4039MB 4039MB primary fat32 boot, lba


root@ubuntu:~#
gparted recognize it as unallocated. test disk does ot show anything . mount says
Quote:
root@ubuntu:~# mount -t auto /dev/sda /mnt/
mount: unknown filesystem type 'isw_raid_member'
I have to say that this HDD is the healthy one in raid perspective and raid controller wanted to rebuild raid from this one , but it is not bootable any more(I dont no why) and does not show any partition on it.
what can I do with this one???

Last edited by golden_boy615; 07-07-2012 at 06:47 AM.
 
Old 07-07-2012, 08:11 AM   #8
unSpawn
Moderator
 
Registered: May 2001
Posts: 29,415
Blog Entries: 55

Rep: Reputation: 3590Reputation: 3590Reputation: 3590Reputation: 3590Reputation: 3590Reputation: 3590Reputation: 3590Reputation: 3590Reputation: 3590Reputation: 3590Reputation: 3590
You have posted a similar thread here and your current threads on the topic have considerable overlap with your thread here. Posting duplicate threads is against the LQ Rules and to compound things you seem to deliberately ignore previous warnings (here, here and here), making you a persistent repeat offender.

This is your final warning to stop posting duplicate threads.
 
Old 07-08-2012, 12:46 AM   #9
golden_boy615
Member
 
Registered: Dec 2008
Distribution: Ubuntu Fedora
Posts: 445

Original Poster
Rep: Reputation: 18
I started to solve my problem from different solutions as you can see none of the topics and solution are the same except that part that I ran mkfs.ext4 /dev/vol_grp1/logical_vol1 and everything went wrong but the other part of my threads are not the same ether. Also about other thread as you can see
here I post the thread some where else because I thought I had posted it in a wrong place.
here I posted it twice by mistake and before anybody told me I said sorry .
and again about my new topic would you please tell me which one has same question same topic and same solution that you counted it as duplicate thread? Except all of them are about RAID, like other people's topics for example lots of users have topic about mysql , ssh or anything else, does this mean that those are duplicated threads!!!!!!!!!!!!!!! but I have to say sorry due to posting the same thing in more than one thread but it was completely relevant to all of them .
 
  


Closed Thread


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
e2fsck froze at 4.8% on large LVM2 volume forbin Linux - Server 1 02-16-2011 07:09 PM
Mount a LVM2 volume in a foreign machine apueyo Linux - Server 1 09-28-2009 10:44 AM
How to move an lvm2 volume group from one physical to another? shwouchk Linux - Software 2 10-29-2008 08:16 PM
resizing lvm2 physical volume fakie_flip Linux - Software 3 08-07-2006 01:18 PM
LVM2 volume group not seen after FC4 install digithead1011 Fedora - Installation 6 10-09-2005 10:25 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Server

All times are GMT -5. The time now is 04:57 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration