On Friday 20 March 2009 18:52:59 Aldo Foot wrote:
On Fri, Mar 20, 2009 at 11:29 AM, Frank Cox thea...@sasktel.net wrote:
On Fri, 20 Mar 2009 11:24:14 +
Bill Crawford wrote:
You should probably be able to get some sense out of this by doing:
# vgrename
Frank Cox wrote:
One of my computers died and, of course, there is un-backed-up data on there
that I want to recover if I can. The hard drive seems to be in good shape so I
took it out of the dead box and installed it on this computer (my main desktop
machine.)
I have been doing a bunch of
On Monday 23 March 2009 15:53:01 Robin Laing wrote:
There needs to be a firm way of changing and editing LVM characteristics
in these situations.
Yeah, boot from rescue disk and rename the first one it sees, should then let
the other be visible. You could, at a pinch, change the partition
On Mon, Mar 23, 2009 at 8:53 AM, Robin Laing
robin.la...@drdc-rddc.gc.ca wrote:
There needs to be a firm way of changing and editing LVM characteristics in
these situations.
--
Robin Laing
Hopefully the LVM toolset will be refined overtime. Rick said he'd
look into the bugzilla
reports;
Aldo Foot wrote:
On Mon, Mar 23, 2009 at 8:53 AM, Robin Laing
robin.la...@drdc-rddc.gc.ca wrote:
There needs to be a firm way of changing and editing LVM characteristics in
these situations.
--
Robin Laing
Hopefully the LVM toolset will be refined overtime. Rick said he'd
look into the
On Thursday 19 March 2009 18:02:26 Frank Cox wrote:
...
LV Name/dev/VolGroup00/LogVol00
VG NameVolGroup00
LV UUIDyFemKc-s2bo-zZC0-cc7q-50By-4jQM-G1MsQr
...
Block device 253:0
--- Segments ---
Logical extent 0 to 8872:
On Thursday 19 March 2009 18:02:26 Frank Cox wrote:
...
LV Name/dev/VolGroup00/LogVol00
VG NameVolGroup00
LV UUIDyFemKc-s2bo-zZC0-cc7q-50By-4jQM-G1MsQr
...
Block device 253:0
--- Segments ---
Logical extent 0 to 8872:
On Fri, 20 Mar 2009 11:24:14 +
Bill Crawford wrote:
You should probably be able to get some sense out of this by doing:
# vgrename 1dl8EY-s2Qe-W50Y-wU8V-nCRJ-5Upz-SEkJgp vg_sda2
[frank...@mutt temp]$ su -c vgrename 1dl8EY-s2Qe-W50Y-wU8V-nCRJ-5Upz-SEkJgp
vg_sda2 Password:
Volume
On Friday 20 March 2009 18:29:33 Frank Cox wrote:
On Fri, 20 Mar 2009 11:24:14 +
Bill Crawford wrote:
You should probably be able to get some sense out of this by doing:
# vgrename 1dl8EY-s2Qe-W50Y-wU8V-nCRJ-5Upz-SEkJgp vg_sda2
[frank...@mutt temp]$ su -c vgrename
On Fri, Mar 20, 2009 at 11:29 AM, Frank Cox thea...@sasktel.net wrote:
On Fri, 20 Mar 2009 11:24:14 +
Bill Crawford wrote:
You should probably be able to get some sense out of this by doing:
# vgrename 1dl8EY-s2Qe-W50Y-wU8V-nCRJ-5Upz-SEkJgp vg_sda2
[frank...@mutt temp]$ su -c
On Fri, 20 Mar 2009 18:50:31 +
Bill Crawford wrote:
You need to either temporarily pull sda2 out, and boot off a rescue disk to
rename it, or vice versa. Or find out the UUID of the volume ... if you're
lucky, vgdisplay --verbose *might* pick up the duplicate and show you the
UUID for
Frank Cox wrote:
On Fri, 20 Mar 2009 18:50:31 +
Bill Crawford wrote:
You need to either temporarily pull sda2 out, and boot off a rescue disk to
rename it, or vice versa. Or find out the UUID of the volume ... if you're
lucky, vgdisplay --verbose *might* pick up the duplicate and show you
From: Dr. Michael J. Chudobiak m...@avtechpulse.com
Sent: Thursday, 2009, March 19 05:10
Frank Cox wrote:
It looks like the machine can see the second drive and the lvm that's on
it
/dev/sdb2, but it has the same VolGroup name as /dev/sda2.
Yes, this is common and annoying. Here is the
On Fri, Mar 20, 2009 at 1:39 PM, jdow j...@earthlink.net wrote:
From: Dr. Michael J. Chudobiak m...@avtechpulse.com
Sent: Thursday, 2009, March 19 05:10
Frank Cox wrote:
It looks like the machine can see the second drive and the lvm that's on
it
/dev/sdb2, but it has the same VolGroup
Frank Cox wrote:
It looks like the machine can see the second drive and the lvm that's on it
/dev/sdb2, but it has the same VolGroup name as /dev/sda2.
Yes, this is common and annoying. Here is the guide that I followed when
it happened to me:
On Thursday 19 March 2009 12:10:25 Dr. Michael J. Chudobiak wrote:
...
I filed bug 461682 (https://bugzilla.redhat.com/show_bug.cgi?id=461682),
requesting that the default volume names not be so generic - they now
incorporate the hostname, so this problem should be much less common in
F11+.
On Thu, Mar 19, 2009 at 5:10 AM, Dr. Michael J. Chudobiak
m...@avtechpulse.com wrote:
Frank Cox wrote:
It looks like the machine can see the second drive and the lvm that's on
it
/dev/sdb2, but it has the same VolGroup name as /dev/sda2.
Yes, this is common and annoying. Here is the guide
Frank Cox wrote:
On Wed, 18 Mar 2009 17:07:28 -0700
Rick Stevens wrote:
We have a serious conflict here. The df command shows you as on sda,
but LVM is reporting sdb. My gut reaction is to have you do a:
vgreduce --test VolGroup00 /dev/sdb2
and see if it would be successful. If
On Thursday 19 March 2009 17:17:43 Rick Stevens wrote:
This is truly screwey. The pvscan shows sdb2 as part of VolGroup00,
lvdisplay shows the partition as in use, but vgreduce says sdb2 isn't
part of the VG. Hoo, boy.
Could someone post the output of lvdisplay --maps and of pvdisplay
On Thu, Mar 19, 2009 at 10:17 AM, Rick Stevens ri...@nerd.com wrote:
This is truly screwey. The pvscan shows sdb2 as part of VolGroup00,
lvdisplay shows the partition as in use, but vgreduce says sdb2 isn't
part of the VG. Hoo, boy.
Frank, this is potentially dangerous, but you can try
On Thu, 19 Mar 2009 17:47:53 +
Bill Crawford wrote:
Could someone post the output of lvdisplay --maps and of pvdisplay --maps ?
[r...@mutt ~]# lvdisplay --maps
--- Logical volume ---
LV Name/dev/VolGroup00/LogVol00
VG NameVolGroup00
LV UUID
On Thu, Mar 19, 2009 at 10:17 AM, Rick Stevens ri...@nerd.com wrote:
Frank Cox wrote:
On Wed, 18 Mar 2009 17:07:28 -0700
Rick Stevens wrote:
We have a serious conflict here. The df command shows you as on sda,
but LVM is reporting sdb. My gut reaction is to have you do a:
Aldo Foot wrote:
On Thu, Mar 19, 2009 at 10:17 AM, Rick Stevens ri...@nerd.com wrote:
Frank Cox wrote:
On Wed, 18 Mar 2009 17:07:28 -0700
Rick Stevens wrote:
We have a serious conflict here. The df command shows you as on sda,
but LVM is reporting sdb. My gut reaction is to have you do a:
On Thu, Mar 19, 2009 at 11:39 AM, Rick Stevens ri...@nerd.com wrote:
Aldo Foot wrote:
On Thu, Mar 19, 2009 at 10:17 AM, Rick Stevens ri...@nerd.com wrote:
Frank Cox wrote:
On Wed, 18 Mar 2009 17:07:28 -0700
Rick Stevens wrote:
We have a serious conflict here. The df command shows you as
Aldo Foot venit, vidit, dixit 17.03.2009 18:45:
On Mon, Mar 16, 2009 at 8:28 PM, Frank Cox thea...@sasktel.net wrote:
One of my computers died and, of course, there is un-backed-up data on there
that I want to recover if I can. The hard drive seems to be in good shape
so I
took it out of
On Wed, 2009-03-18 at 12:26 -0600, Frank Cox wrote:
At this point, since the second hard drive seems to be in good condition, I
think I would like to re-format it and either add it to the existing volume on
sda2 to make one big logical drive, or just reformat it and make a second lvm
on it
On Wed, 18 Mar 2009 12:17:13 -0700
Rick Stevens wrote:
Now, back to your question. If you REALLY want to put /dev/sdb2 into a
new volume group, first make sure none of its space is being used in
existing LVs (check the output of lvdisplay -vm). If it's being used,
you'll have to first
Frank Cox wrote:
On Wed, 18 Mar 2009 12:17:13 -0700
Rick Stevens wrote:
Now, back to your question. If you REALLY want to put /dev/sdb2 into a
new volume group, first make sure none of its space is being used in
existing LVs (check the output of lvdisplay -vm). If it's being used,
you'll
Rick Stevens wrote:
Big Snipolla
Perhaps we should take this off-list--I don't know that we want to
occupy the list's bandwidth with the back-and-forth of geting this
sorted. When it's fixed, we could post a summary on what we did for
those who are interested.
I, for one, would like you to
On Wed, Mar 18, 2009 at 11:26 AM, Frank Cox thea...@sasktel.net wrote:
snip
At this point, since the second hard drive seems to be in good condition, I
think I would like to re-format it and either add it to the existing volume on
sda2 to make one big logical drive, or just reformat it and make
On Wed, Mar 18, 2009 at 2:24 PM, Dean S. Messing de...@sharplabs.com wrote:
Rick Stevens wrote:
Big Snipolla
Perhaps we should take this off-list--I don't know that we want to
occupy the list's bandwidth with the back-and-forth of geting this
sorted. When it's fixed, we could post a summary
On Wed, 18 Mar 2009 13:43:26 -0700
Rick Stevens wrote:
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 25 200781 83 Linux
/dev/sdb2 26 36481 292832820 8e Linux LVM
Ah, HAH! Ok, do you want to run off the
On Wed, 18 Mar 2009 14:24:12 -0700 (PDT)
Dean S. Messing wrote:
Regarding the actual problem the OP seems to have, it seems to me (not
being an LVM expert) from his output that he has a Volume Group (00)
that spans sda2 and sdb2, two LVs that are defined in the VG, both of
which sit on sdb2,
Frank Cox wrote:
On Wed, 18 Mar 2009 14:24:12 -0700 (PDT)
Dean S. Messing wrote:
Regarding the actual problem the OP seems to have, it seems to me (not
being an LVM expert) from his output that he has a Volume Group (00)
that spans sda2 and sdb2, two LVs that are defined in the VG, both
Slip of the brain:
Well, being a researcher, I'd not do this, but rather figure out
exactly what's causing the funning remapping. But you may not be the
^^^ funny
curious type. :-)
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe:
Frank Cox wrote:
On Wed, 18 Mar 2009 14:24:12 -0700 (PDT)
Dean S. Messing wrote:
Regarding the actual problem the OP seems to have, it seems to me (not
being an LVM expert) from his output that he has a Volume Group (00)
that spans sda2 and sdb2, two LVs that are defined in the VG, both of
On Wed, 18 Mar 2009 17:07:28 -0700
Rick Stevens wrote:
We have a serious conflict here. The df command shows you as on sda,
but LVM is reporting sdb. My gut reaction is to have you do a:
vgreduce --test VolGroup00 /dev/sdb2
and see if it would be successful. If so, then remove
On Wed, Mar 18, 2009 at 5:14 PM, Frank Cox thea...@sasktel.net wrote:
On Wed, 18 Mar 2009 17:07:28 -0700
Rick Stevens wrote:
We have a serious conflict here. The df command shows you as on sda,
but LVM is reporting sdb. My gut reaction is to have you do a:
vgreduce --test VolGroup00
On Wed, 18 Mar 2009 17:43:44 -0700
Aldo Foot wrote:
Rename the VG on the sdb2 to something else other than VolGroup00.
vgrename VolGroup00 some_VG_name
Both of the VG's are named VolGroup00. There doesn't appear to be a way to
tell it to rename the VG on sdb2 and I don't know what
Frank Cox wrote:
On Wed, 18 Mar 2009 17:43:44 -0700
Aldo Foot wrote:
Rename the VG on the sdb2 to something else other than VolGroup00.
vgrename VolGroup00 some_VG_name
Both of the VG's are named VolGroup00. There doesn't appear to be a way to
tell it to rename the VG on sdb2
On Mon, 2009-03-16 at 21:28 -0600, Frank Cox wrote:
One of my computers died and, of course, there is un-backed-up data on there
that I want to recover if I can. The hard drive seems to be in good shape so
I
took it out of the dead box and installed it on this computer (my main desktop
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
On Mon, Mar 16, 2009 at 8:28 PM, Frank Cox thea...@sasktel.net wrote:
One of my computers died and, of course, there is un-backed-up data on there
that I want to recover if I can. The hard drive seems to be in good shape so
I
took it out of the dead box and installed it on this computer (my
One of my computers died and, of course, there is un-backed-up data on there
that I want to recover if I can. The hard drive seems to be in good shape so I
took it out of the dead box and installed it on this computer (my main desktop
machine.)
I have been doing a bunch of reading about logical
44 matches
Mail list logo
