e I'm not terribly anxious to just start playing around with
> the lvm configuration without knowing what I'm doing.
>
> Here are my findings so far:
>
> [r...@mutt ~]# pvscan
> PV /dev/sdb2 VG VolGroup00 lvm2 [279.25 GB / 32.00 MB free]
> PV /dev/sda2 VG VolGrou
Craig White wrote:
> I wouldn't mess with pv commands at all but rather simply create a mount
> point and mount the drives. You probably need to figure out what
> partitions are in the two LV Groups and I think you should be able to do
> that with the command 'blkid'
Doesn't he have to rename the
e I'm not terribly anxious to just start playing around with
> the lvm configuration without knowing what I'm doing.
>
> Here are my findings so far:
>
> [r...@mutt ~]# pvscan
> PV /dev/sdb2 VG VolGroup00 lvm2 [279.25 GB / 32.00 MB free]
> PV /dev/sda2 V
volumes and some of what
I've found is self-contradictory, incomplete and stuff that I just don't
really understand (yet.) And, as you can imagine, since this is my main
desktop machine I'm not terribly anxious to just start playing around with
the lvm configuration without knowing
After upgrading my kernel I got read errors on my external USB disk when
doing a pvscan and LVM wouldn't recognize it as a valid volume. My
internal LVM PV worked fine.
Booting back into kernel-2.6.27.15-170.2.24.fc10.i686 made it work
again. Has anyone else seen problems with USB st
On Sat, 2009-02-21 at 18:51 -0500, Chris Tyler wrote:
>
> # lvextend VolGroup00 /dev/xxx
Whoops, I should obviously have written vgextend.
-Chris
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedorapro
On Sat, 2009-02-21 at 23:30 +, iarly selbir wrote:
> - create a lvm partition with fdisk
> fdisk /dev/xxx
> n ( new partition )
> p ( type primary )
> 1 ( first partition )
> t ( select partition type )
> 8e ( lvm )
>
> - create physical volume
> # pvcreate /de
- create a lvm partition with fdisk
fdisk /dev/xxx
n ( new partition )
p ( type primary )
1 ( first partition )
t ( select partition type )
8e ( lvm )
- create physical volume
# pvcreate /dev/xxx1
- create volume group
# vgcreate name_vg /dev/xxx1
- create logical volume
# lvcreate -L SIZE
In an F-10 computer I have a second drive that I would like to designate
lvm VolGroup01 but have not had much success at finding how to proceed.
Need some guidance ... How to do it, where to look?
Thanks.
Bob
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https
On Thu, 2009-02-12 at 23:56 +0300, Andrew Junev wrote:
> P.S. What does the 'OP' mean? Something like 'Original Poster'? :)
Yes, it's accepted usage. Not that common but not extremely rare either.
poc
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mai
Thursday, February 12, 2009, 11:29:07 PM, you wrote:
> In any case, it would be interesting to have the OP reboot, and see
> if the VG is active on reboot.
I did. I even powered the system down. It starts now without that
problem and everything gets mounted automatically during boot.
So the probl
Mikkel L. Ellertson wrote:
Strange - /var/lock/lvm is empty, and its date does not correspond
It's always empty unless an LVM tool is running (or you've disabled
locking or are using some non-local locking mode for all your VGs).
Try running e.g. vgchange in a debugger. Set a bre
gt;>> If I understand the VG commands correctly, you just did.
>>> I think the OP wants his VG to activate without the need for him
>>> to give the root password at each boot and mess around running
>>> commands by hand :)
>>>
>>> Bryn.
>>&
the root password at each boot and mess around running
commands by hand :)
Bryn.
I thought that running "vgchange -ay VolTerabytes00" would have
modified /etc/lvm/cache/.cache so that the VG would stay active. (I
The cache is revalidated each time the tools run. If VGs are only
being
vate without the need for him to
> give the root password at each boot and mess around running commands
> by hand :)
>
> Bryn.
>
I thought that running "vgchange -ay VolTerabytes00" would have
modified /etc/lvm/cache/.cache so that the VG would stay active. (I
think I have
Andrew Junev wrote:
/var/log/messages doesn't contain any information about that problem.
The error happened too early during boot - so that the data didn't get
into the log files (disks were mounted in read-only mode).
You can work around this by commenting out the file systems on the
problem
Hello Bryn,
> You need to understand why it wasn't being activated automatically.
> Boot logs (dmesg and/or /var/log/messages) would help here. Normally,
> devices are scanned for LVM metadata when rc.sysinit runs.
> There were some bugs in older releases (f8 is no longer
>
Mikkel L. Ellertson wrote:
Andrew Junev wrote:
Thursday, February 12, 2009, 9:42:38 PM, you wrote:
Running the command: vgchange -ay VolTerabytes00 Should
activate the VG, assuming that all PVs are present (and any
needed modules have been loaded).
I tried running lvm and it says "Lo
since the vgchange -ay worked after the system had
> booted but there's not really enough information to say for sure.
>
> Try adding a "sleep 5" or "udevsettle --timeout=30" command to
> rc.sysinit above each of the LVM activation commands.
I don't use
Andrew Junev wrote:
> Thursday, February 12, 2009, 9:42:38 PM, you wrote:
>
>
>> Running the command:
>
>> vgchange -ay VolTerabytes00
>
>> Should activate the VG, assuming that all PVs are present (and any
>> needed modules have been loaded).
>
&g
Andrew Junev wrote:
Thursday, February 12, 2009, 9:42:38 PM, you wrote:
Running the command:
vgchange -ay VolTerabytes00
Should activate the VG, assuming that all PVs are present (and
any needed modules have been loaded).
I tried running lvm and it says "Locking type 1 initialis
Thursday, February 12, 2009, 9:42:38 PM, you wrote:
> Running the command:
> vgchange -ay VolTerabytes00
> Should activate the VG, assuming that all PVs are present (and any
> needed modules have been loaded).
>> I tried running lvm and it says "Locking type 1 initi
:
vgchange -ay VolTerabytes00
Should activate the VG, assuming that all PVs are present (and any
needed modules have been loaded).
I tried running lvm and it says "Locking type 1 initialisation failed"
no matter what command I enter...
Check that the file system providing /var has been
I'm prompted to enter a root password to get to system maintenance, or
Ctrl+D to continue.
In the system maintenance I can see there's /dev/VolGroup00 but
there's no /dev/VolTerabytes00, so my newly-created VG seem to be
missing!
I tried running lvm and it says "Locking type 1
Leslie Satenstein wrote:
My question is in the subject line.
Btrfs will take more time to mature (maybe a couple more releases
atleast) but essentially, yes.
Btrfs features are listed in
http://btrfs.wiki.kernel.org/index.php/Main_Page
Rahul
--
fedora-list mailing list
fedora-list@redha
My question is in the subject line.
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
On Dec 11, 2008, at 6:35 PM, Bryn M. Reeves wrote:
Bruce Thompson wrote:
Just got home to try it out, that did the trick nicely.
BTW for those that may have influence, would it be unreasonable to
expect the default initrd to include usb-storage?
The current approach is to build initramfs i
Bruce Thompson wrote:
Just got home to try it out, that did the trick nicely.
BTW for those that may have influence, would it be unreasonable to
expect the default initrd to include usb-storage?
The current approach is to build initramfs images that are tailored to a
specific system - only t
On Dec 11, 2008, at 7:32 AM, Mikkel L. Ellertson wrote:
Bruce Thompson wrote:
Hi all,
I haven't seen this reported anywhere else and it's kind of driving
me
nuts.
I've got an LVM volume group that extends across two internal
drives and
one external USB drive. Prior to
Bruce Thompson wrote:
> Hi all,
>
> I haven't seen this reported anywhere else and it's kind of driving me
> nuts.
>
> I've got an LVM volume group that extends across two internal drives and
> one external USB drive. Prior to Fedora 10, the volume group in
Hi all,
I haven't seen this reported anywhere else and it's kind of driving me
nuts.
I've got an LVM volume group that extends across two internal drives
and one external USB drive. Prior to Fedora 10, the volume group
initializes fine during boot and the filesystems liste
Frode Petersen:
I can't find a way to create new LV's on an existing PV.
(Back from the install session) I accidentally figured this out. You
have to select one of the listed logical volumes and choose 'edit', then
in the next dialog you can select a logical volume and choose edit to
actual
Hi. I'm installing F10 (fresh) from the DVD. I have a tri-boot setup
with Win+CentOS+F10. The CentOS and Fedora installs will share some
physical LVM volumes, having some logical volumes in common and others
for them selves.
When setting up the partitioning of the disks in Anaconda (c
On Wed, Nov 26, 2008 at 07:41:24AM -0500, John Burton wrote:
> I've never used LVM under Fedora. I did use something similar under AIX
> probably 10-15 years ago. I've been using linux for since slackware (on
> floppies) and kernel version 0.99.4, but I've always used
All,
I've never used LVM under Fedora. I did use something similar under AIX
probably 10-15 years ago. I've been using linux for since slackware (on
floppies) and kernel version 0.99.4, but I've always used the old
standard of partitioning hard drives and creating files
B drive and your system have VolGroup00 as
> the volume group name, which is causing confusion.
Guessing that's the problem, or that they have the same name? They do
have the same name,
lvm lvs
LV VG Attr LSize Origin Snap% Move Log Copy% Convert
LogVol00 VolGroup00
els for non-LVM partitions, etc)
to provide unique identifiers, where they're (currently) given generic
non-unique ones.
--
[EMAIL PROTECTED] ~]$ uname -r
2.6.27.5-41.fc9.i686
Don't send private replies to my address, the mailbox is ignored. I
read messages from the public lists.
--
On Tue, 2008-11-25 at 15:27 -1000, Dave Burns wrote:
> On Tue, Nov 25, 2008 at 2:57 PM, Dario Nievas <[EMAIL PROTECTED]> wrote:
> > could you please provide the output of:
> > "pvscan"
> > "lvscan"
> > "vgscan"
> >
>
&g
On Tue, Nov 25, 2008 at 2:59 PM, Chris Tyler <[EMAIL PROTECTED]> wrote:
>
> On Tue, 2008-11-25 at 14:30 -1000, Dave Burns wrote:
>> I have a thumb drive with fedora installed on it. When I plug in the
>> drive, /boot mounts automatically. fdisk -l shows the root partition
&
On Tue, Nov 25, 2008 at 2:57 PM, Dario Nievas <[EMAIL PROTECTED]> wrote:
> could you please provide the output of:
> "pvscan"
> "lvscan"
> "vgscan"
>
lvm pvscan;lvm lvscan;lvm vgscan
PV /dev/sdc2 VG VolGroup00 lvm2 [7.28 GB / 32.00 MB fre
On Tue, 2008-11-25 at 14:30 -1000, Dave Burns wrote:
> I have a thumb drive with fedora installed on it. When I plug in the
> drive, /boot mounts automatically. fdisk -l shows the root partition
> device is LVM. I would like to mount / by hand at another mount point,
> but I can'
gt; I have a thumb drive with fedora installed on it. When I plug in the
> drive, /boot mounts automatically. fdisk -l shows the root partition
> device is LVM. I would like to mount / by hand at another mount point,
> but I can't figure out what parameter to give to -t. man moun
I have a thumb drive with fedora installed on it. When I plug in the
drive, /boot mounts automatically. fdisk -l shows the root partition
device is LVM. I would like to mount / by hand at another mount point,
but I can't figure out what parameter to give to -t. man mount no
help. man lvm do
miss ?
Regards.
You probably need to rebuild the initrd for your kernel to know about the new
logical volume name(s).
Now, I am not that sure because I did read that it is necessary to rebuild
the initrd if the root is on a lvm which is not my case
On Monday 24 November 2008 00:34:25 Patrick Dupre wrote:
> Hello,
>
> I duplicate an hard drive to another one with logical partition.
> I kept the / on a standard partition, put the /usr on /dev/VG1/usr, etc...
> When I mount the logical partitions I do experience any problem but when
> I boot th
Timothy Murphy wrote:
Patrick Dupre wrote:
fsck complains
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you mig
Patrick Dupre wrote:
> fsck complains
> The superblock could not be read or does not describe a correct ext2
> filesystem. If the device is valid and it really contains an ext2
> filesystem (and not swap or ufs or something else), then the superblock
> is corrupt, and you might try running
On Tue, 25 Nov 2008, Bill Crawford wrote:
On Monday 24 November 2008 00:34:25 Patrick Dupre wrote:
Hello,
I duplicate an hard drive to another one with logical partition.
I kept the / on a standard partition, put the /usr on /dev/VG1/usr, etc...
When I mount the logical partitions I do experi
Hello,
I can add that when it scratches, I get the following information:
Setting hostname: OK
locking type 1 initialisation failed
fsck.ext No such file or directory while trying to open /dev/mapper/VG1-usr
then / is only mount in read only.
What is wrong ?
--
---
/floppy msdos,auto noauto,user,umask=0 0 0
I did try /dev/VG1 and /dev/mapper with the same result.
I looks like that the logical partitions are not recognize by fsck, but it
works fine when I do the same from a properly boot disk.
fsck works find with LVM. I suspect that you may may have
On Mon, 24 Nov 2008 15:13:57 +0100, Chris Tyler <[EMAIL PROTECTED]> wrote:
On Mon, 2008-11-24 at 15:04 +0100, roland wrote:
Hello,
I used vmware-vdiskmanager to extend a virtual client
This virtual client runs fedora and has a LVM.
fdisk /dev/sda
results in
/dev/sda1 (id 83) /dev/sda2
basic tasks like this (it's not been updated in a
couple of years, but is still correct for simple things like expanding
VGs/LVs):
http://tldp.org/HOWTO/LVM-HOWTO/
Regards,
Bryn.
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinf
On Mon, 2008-11-24 at 15:04 +0100, roland wrote:
> Hello,
>
> I used vmware-vdiskmanager to extend a virtual client
> This virtual client runs fedora and has a LVM.
>
> fdisk /dev/sda
> results in
> /dev/sda1 (id 83) /dev/sda2 (id=8e) /dev/sda3
>
> How can I con
Hello,
I used vmware-vdiskmanager to extend a virtual client
This virtual client runs fedora and has a LVM.
fdisk /dev/sda
results in
/dev/sda1 (id 83) /dev/sda2 (id=8e) /dev/sda3
How can I connect sda3 to VolGroup00
I read all kind of entrees on google, but they are all complicated.
I have
e that the logical partitions are not recognize by fsck, but it
> works fine when I do the same from a properly boot disk.
>
fsck works find with LVM. I suspect that you may may have the wrong
LV and/or VG name. You may want to run lvscan to display the names.
Mikkel
--
Do not meddle in the
Hello,
I duplicate an hard drive to another one with logical partition.
I kept the / on a standard partition, put the /usr on /dev/VG1/usr, etc...
When I mount the logical partitions I do experience any problem but when
I boot the machine on the logical partition I get an error from the
/etc/fst
ndows , now i have free space on
> >> disk
> >>
> >> There is
> >>
> >> sda1 - now free space
> >> sda2 - /boot
> >> sda3 - LVM
> >>
> >> Now i want to resize sda3 to take free space over sda1. Is this
> >> possib
t;
>> sda1 - now free space
>> sda2 - /boot
>> sda3 - LVM
>>
>> Now i want to resize sda3 to take free space over sda1. Is this
>> possible? as there is sda2 in way before ...
>> Is the best solution to just create sda1 with LVM and then resize my
>>
On Sat, 2008-10-25 at 20:37 +0200, David Hláčik wrote:
> Hello guys,
>
> i have removed sda1 partition with Windows , now i have free space on
> disk
>
> There is
>
> sda1 - now free space
> sda2 - /boot
> sda3 - LVM
>
> Now i want to resize sda3 t
David Hláčik a écrit :
> Hello guys,
>
> i have removed sda1 partition with Windows , now i have free space on disk
>
> There is
>
> sda1 - now free space
> sda2 - /boot
> sda3 - LVM
>
> Now i want to resize sda3 to take free space over sda1. Is this
> poss
Hello guys,
i have removed sda1 partition with Windows , now i have free space on disk
There is
sda1 - now free space
sda2 - /boot
sda3 - LVM
Now i want to resize sda3 to take free space over sda1. Is this possible? as
there is sda2 in way before ...
Is the best solution to just create sda1
nd -L+6G /dev/VolGroup00/LogVol03
> # resize2fs /dev/VolGroup00/LogVol03
> # mount /tmp
>
> Does that ring any alarm bells?
One huge alarm bell.
When you are manually resizing an ext3/LVM combo you risk over reducing
the LVM compared to the ext3 FS due to math/1000vs1024 conversion
erro
Robert Locke wrote:
Unmounting should only be necessary when "shrinking" a filesystem. I
thought you were growing /tmp But, now that you mention it, I
didn't notice that you were unmounting and fscking /var before lvextend
and resize2fs.
Generally growing should work with just lvextend an
On Wed, 2008-10-22 at 14:48 -0400, brian wrote:
> brian wrote:
> > Robert Locke wrote:
> >>
> >> As an alternative, that might be easier, why not install
> >> "system-config-lvm"? It presents a graphical view of shrinking and
> >&
brian wrote:
Robert Locke wrote:
As an alternative, that might be easier, why not install
"system-config-lvm"? It presents a graphical view of shrinking and
enlarging.
Thanks, I'll check that out.
That looks easy to use. However, I can't unmount /tmp so it look
gt; >> # resize2fs /dev/VolGroup00/LogVol03 # mount /tmp
> >>
> >> Does that ring any alarm bells?
> >>
> >> [1] http://www.tldp.org/HOWTO/LVM-HOWTO/
> > I don't know about alarm bells but I would think that you would
> > have to
on where things are
That was supposed to be the point of LVM. No moving necessary. They
are both on the Volume Group, space doesn't have to be contiguous,
etc, etc
That's what I thought.
I would suggest that when reducing you should use the "same numbers"
for both re
00/LogVol04 # mount /var # umount /tmp # e2fsck -f
/dev/VolGroup00/LogVol03 # lvextend -L+6G /dev/VolGroup00/LogVol03
# resize2fs /dev/VolGroup00/LogVol03 # mount /tmp
Does that ring any alarm bells?
[1] http://www.tldp.org/HOWTO/LVM-HOWTO/
I don't know about alarm bells but I woul
On Wed, 2008-10-22 at 09:09 -0700, Craig White wrote:
> On Wed, 2008-10-22 at 11:42 -0400, brian wrote:
> > I have a /tmp volume that I'd like to increase. I've been having a look
> > at the LVM HOWTO [1] and various other pages online and think I've got
> >
On Wed, 2008-10-22 at 11:42 -0400, brian wrote:
> I have a /tmp volume that I'd like to increase. I've been having a look
> at the LVM HOWTO [1] and various other pages online and think I've got
> it figured out. Those being famous last words, I thought I'd check
I have a /tmp volume that I'd like to increase. I've been having a look
at the LVM HOWTO [1] and various other pages online and think I've got
it figured out. Those being famous last words, I thought I'd check here
first.
# parted /dev/sda print
Model: ATA Maxtor 6Y080L0
Thanks Mikkel;
On Sun, 2008-10-12 at 18:36 -0500, Mikkel L. Ellertson wrote:
> William Case wrote:
> >
> > It's OK Mikkel, I gotcha anyways. I have checked rc.sysinit and it does
> > a
> > 'if [ -x /sbin/lvm ]; then
> > action $"Setting up L
William Case wrote:
>
> It's OK Mikkel, I gotcha anyways. I have checked rc.sysinit and it does
> a
> 'if [ -x /sbin/lvm ]; then
> action $"Setting up Logical Volume Management:" /sbin/lvm vgchange -a y
> --ignorelockingfailure
> fi
>
> I
Hi;
On Sun, 2008-10-12 at 17:39 -0500, Mikkel L. Ellertson wrote:
> Mikkel L. Ellertson wrote:
> > William Case wrote:
> >> Hi;
> >>
> >> At boot up, the first thing that init.d seems to look for after udev is
> >> an LVM fs set up. Finding none, bec
Mikkel L. Ellertson wrote:
> William Case wrote:
>> Hi;
>>
>> At boot up, the first thing that init.d seems to look for after udev is
>> an LVM fs set up. Finding none, because I am not using LVM, it
>> continues to boot echoing every service. What is the name of
William Case wrote:
> Hi;
>
> At boot up, the first thing that init.d seems to look for after udev is
> an LVM fs set up. Finding none, because I am not using LVM, it
> continues to boot echoing every service. What is the name of this LVM
> checking service and how do I tur
Hi;
At boot up, the first thing that init.d seems to look for after udev is
an LVM fs set up. Finding none, because I am not using LVM, it
continues to boot echoing every service. What is the name of this LVM
checking service and how do I turn it off? Service xxx stop??
--
Regards Bill
Fedora
side is up and running as it
should. Problem is I don't know how to extend LVM to a larger size,
without doing the whole adding of physical drives, and so forth, and the
pv display doesn't show more than the 1.4TB that I started with. Most
documentation details software RAID procedures
side is up and running as it
> should. Problem is I don't know how to extend LVM to a larger size,
> without doing the whole adding of physical drives, and so forth, and the
> pv display doesn't show more than the 1.4TB that I started with. Most
> documentation details software R
of
> the disks well, and everything on that side is up and running as it
> should. Problem is I don't know how to extend LVM to a larger size,
> without doing the whole adding of physical drives, and so forth, and the
> pv display doesn't show more than the 1.4TB that I start
. Problem is I don't know how to extend LVM to a larger size,
without doing the whole adding of physical drives, and so forth, and the
pv display doesn't show more than the 1.4TB that I started with. Most
documentation details software RAID procedures that don't really work
with t
Luc MAIGNAN <[EMAIL PROTECTED]> writes:
> I've setup a LVM volume on several disks. It appears that one at
> least of the disks has crashed. Is there a way to recover data on
> the good disks or all is lost ?
>From your backups? (Sorry! Been there, felt your pain.)
Luc MAIGNAN a écrit :
> Hi,
>
> I've setup a LVM volume on several disks.
> It appears that one at least of the disks has crashed.
>
> Is there a way to recover data on the good disks or all is lost ?
try in rescue mode :
lvm vgreduce --test --removem
Hi,
I've setup a LVM volume on several disks.
It appears that one at least of the disks has crashed.
Is there a way to recover data on the good disks or all is lost ?
Thanks for any help
BR
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/ma
That's what I forgot! resize2fs!
I greatly appreciate the replies.
Thanks,
Gene Poole
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
On Wed, 2008-09-24 at 19:20 +0530, Kapil Hari Paranjape wrote:
> Hello,
>
> On Wed, 24 Sep 2008, Gene Poole wrote:
> > I performed an extend (lvextend) on a file system that was running out
> > of space. All of the return codes and messages showed a good
> > completion. However, when I did a
Hello,
On Wed, 24 Sep 2008, Gene Poole wrote:
> I performed an extend (lvextend) on a file system that was running out
> of space. All of the return codes and messages showed a good
> completion. However, when I did a display on the file system (df -m
> /work) it didn't show that the file sys
I performed an extend (lvextend) on a file system that was running out
of space. All of the return codes and messages showed a good
completion. However, when I did a display on the file system (df -m
/work) it didn't show that the file system had been extended.
The first display command was:
v/VolGroup-F9 (or something like that - man
> >vgrename).
> >
> >(although in rescue mode, this would be lvm vgrename)
> >
> >if you put the other disk back afterwards, the names will no longer clash
>
> <<<<<
>
> Good afternoon, Stuart.
>
>
in rescue mode, this would be lvm vgrename)
if you put the other disk back afterwards, the names will no longer clash
<<<<<
Good afternoon, Stuart.
I tried that and found that I can't do that with the boot drive, else
it will no longer boot. I assume that I have to edit /et
on a new hard drive,
>> and I need to mount the old FC5 boot disk to copy some stuff off of it.
>>
>> "mount /dev/sdb2 /driveb" doesn't work for the reasons noted
>> (/dev/sdb2 is a container and not a volume).
>>
>> So, I said "lvm vgscan" an
On Tue, Sep 23, 2008 at 12:35:21AM -0400, Eric wrote:
> At 08:40 PM 9/22/2008, Paul W. Frields wrote:
> >>>>>
> >The LVM system uses UUIDs (which are almost guaranteed to be unique) to
> >label each LVM PV, VG, and LV. I believe you can use "vgscan" to
&
> "mount /dev/sdb2 /driveb" doesn't work for the reasons noted
> (/dev/sdb2 is a container and not a volume).
>
> So, I said "lvm vgscan" and got:
>
> File descriptor 20 left open
>Reading all physical volumes. This may take a while...
>Fou
Hello,
On Tue, 23 Sep 2008, Eric wrote:
> If I then go and physically reconnect the second drive (the old FC5
> drive), there is no lvm command that will allow me to see both drives
> AND see their UIDs... the only command that will let me see the UID is
> vgscan, and that one w
At 08:40 PM 9/22/2008, Paul W. Frields wrote:
>>>>>
The LVM system uses UUIDs (which are almost guaranteed to be unique) to
label each LVM PV, VG, and LV. I believe you can use "vgscan" to
display them, and then reference the UUID of the VG in question when you
run &
lGroup on one drive
> is 00 and the one on another drive is 01.
>
> Until I can resolve that one issue, I cannot mount my old FC6 drive, at all.
The LVM system uses UUIDs (which are almost guaranteed to be unique) to
label each LVM PV, VG, and LV. I believe you can use "vgscan&quo
At 07:54 PM 9/22/2008, Antonio Olivares wrote:
>
You can try to use Slax Linux Live CD(get the latest slax608rc6.iso.
http://www.slax.org/forum.php?action=view&parentID=17340
or you can also use:
http://forums.fedoraforum.org/showthread.php?p=707874
to find out answers!
<
Good even
--- On Mon, 9/22/08, Eric <[EMAIL PROTECTED]> wrote:
> From: Eric <[EMAIL PROTECTED]>
> Subject: How to mount an LVM volume? (was lvm2 problem)
> To: fedora-list@redhat.com
> Date: Monday, September 22, 2008, 1:41 PM
> At 12:45 PM 9/22/2008, Chris Tyler wrote:
>
>
doing a fresh install on a new hard drive,
and I need to mount the old FC5 boot disk to copy some stuff off of it.
"mount /dev/sdb2 /driveb" doesn't work for the reasons noted
(/dev/sdb2 is a container and not a volume).
So, I said "lvm vgscan" and got:
File descri
On Sat, 2008-08-23 at 20:09 +0200, Roberto Ragusa wrote:
> Craig White wrote:
> > I was able to reduce the size of the logical volumes, move the logical
> > volumes so they are adjacent and then reduce the size of the physical
> > LVM but I cannot seem to reduce the par
101 - 200 of 249 matches
Mail list logo
