Hmmm, yes. I think this is a bug in the way the CLI handles cluster
volumes vs. single machine volumes.
On a single machine, if the volume is not in-use (active but not
mounted), an lvremove will deactivate and remove it.
In a cluster, the lvremove seems to skip the deactivate portion of
that, forcing you to do:
$> lvchange -an ...
$> lvremove ...
to get similar effect.
The GUI seems to be hiding this "bug" from the end-user.
brassow
On Jul 30, 2007, at 1:58 PM, jim parsons wrote:
Follow-up:
luci just calls the same command line command on the ricci agent.
ricci does lvchange -an which will error out if the volume is in
use by
other cluster members
We just confirmed this behavior on a test cluster.
-J
On Mon, 2007-07-30 at 14:48 -0400, jim parsons wrote:
Thanks for this notice, Jonathan; I will check if this is in error...
-j
On Mon, 2007-07-30 at 13:16 -0500, Jonathan Brassow wrote:
lvremove doesn't seem like it wants to remove the volume because
it is
in use on another node. Is this true? If so, the GUI shouldn't be
removing it either.
brassow
On Jul 28, 2007, at 3:04 PM, Mahmoud Hanafi wrote:
I am trying to remove a lv via cmd line but I get the following
error.
[root@nfs1 /]# lvremove /dev/gfs_vg/gfs_st2_sz512
Do you really want to remove active logical volume "gfs_st2_sz512"?
[y/n]: y
Error locking on node nfs1.local: Volume is busy on another node
Can't get exclusive access to volume "gfs_st2_sz512"
But I can remove lv via the GUI (luci).
What am I doing wrong on the cmd line.
Thanks,
Mahmoud
-------------------------------------------------------------------
-------------------------------------------------------------------
------------------------------------------
This is a PRIVATE message. If you are not the intended recipient,
please delete without copying and kindly advise us by e-mail of the
mistake in delivery. NOTE: Regardless of content, this e-mail shall
not operate to bind CSC to any order or other contract unless
pursuant to explicit written agreement or government initiative
expressly permitting the use of e-mail for such purpose.
-------------------------------------------------------------------
-------------------------------------------------------------------
------------------------------------------
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
