Before you start using your resource group you might want to reimport the VG again using the "-V" flag as funksen said.
It is not a *requirement* to have the same Major Number for the VG on both participating nodes but it makes administrating the cluster a lot easier in the long run.
To get the major number have a look at the node where you created the VG. You will notice an character-device entry /dev/<vgname>, which has a certain major number. Like in this example, the major number is 34:
Code:
root@system# lsvg
rootvg
datavg
imagevg
root@system# ls -l /dev/datavg
crw-rw---- 1 root admin 34, 0 Jan 20 13:46 /dev/datavg
This you can use to import the VG on the other node with the same Major Number.
Hello,
I have logical volume group of 50GB, in which I have 2 logical volumes, LogVol01 and LogVol02, both are of 10GB.
If I extend LogVol01 further by 10GB, then it keeps the extended copy after logical volume 2. I want to know where it keeps this information
Regards
Himanshu (3 Replies)
Does anyone have any simple methods for moving a current logical volume from one volume group to another? I do not wish to move the data from one physical volume to another. Basically, I want to "relink" the logical volume to exist in a different volume group. Any ideas? (2 Replies)
Hello,
I am a french computer technician, and i speak English just a little.
On Aix 5.3, I encounter a name conflict logical volume on two volume group.
The first volume lvnode01 is OK in rootvg and mounted. It is also consistent in the ODM
root # lsvg -l rootvg |grep lvnode01 ... (10 Replies)
Hi,
I have a requirement to monitor the HACMP Resource Groups. At present in my environment, if the Resource Groups fail over from preferred node to Secondary node we dont get notification.
Can some one help me in creating a scrript. I have more than one RG online. (Max 4 Resource Groups in... (2 Replies)
Hi,
Not sure if this is the correct forum to post this on but maybe a mod could move it if not.
When trying to move a HACMP resource group between lpars on AIX I receive the following.
State not STABLE/RP_RUNNING or ibcasts Join for node 2 rejected,
Clearing in join protocol flag... (11 Replies)
Hi,
I'm new to HACMP. Currently I setup a cluster with nfs cross-mount follow this guide:
kristijan.org NFS cross-mounts in PowerHA/HACMPMy cluster has two nodes: erp01 and erp02.
I'm using nfs4 with filesystem for nfs is: /sapnfs
Cluster start without problems. But I cannnot move RG (with... (3 Replies)
Hello. I am Running AIX 6.1 and PowerHA 6.1
I have an active/active cluster (Prod/Dev) cluster. Each side will failover to the other.
I have on my prod side an active volume group with a file system. The VG is imported on both nodes and active (varried on, file system mounted) on the prod... (3 Replies)
Hi Experts
I need an script to add an disk in to the veritas volume manager disk group.
For example:
# cd /tmp
# view disk
c6t5d2
c6t2d1
c6t3d7
c6t11d2
c7t11d2
c6t11d6
Normally we add the disk like this:
# vxdg -g freedg freedisk01=c6t5d2
# vxdg -g freedg freedisk02=c6t2d1
#... (3 Replies)
hi,
I want to create a volume group of 200 GB and then create different file systems on that.
please help me out. Its becomes confusing when the PP calculating PP.
I don't understand this concept. (2 Replies)
Hello Guys,
I want to create a file system dedicated for an application installation. But there is no space in volume group to create a new logical volume. There is enough space in other logical volume which is being mounted on /var.
I know we can use that logical volume and create a virtual... (2 Replies)
Discussion started by: vamshigvk475
2 Replies
LEARN ABOUT FREEBSD
mknod
MKNOD(8) BSD System Manager's Manual MKNOD(8)NAME
mknod -- build special file
SYNOPSIS
mknod name
mknod name [b | c] major minor [owner:group]
DESCRIPTION
The mknod utility is deprecated on modern FreeBSD systems.
The mknod utility creates device special files. To make nodes manually, the arguments are:
name Device name, for example /dev/da0 for a SCSI disk or /dev/pts/0 for pseudo-terminals.
b | c Type of device. If the device is a block type device such as a tape or disk drive which needs both cooked and raw special files, the
type is b. All other devices are character type devices, such as terminal and pseudo devices, and are type c.
major The major device number is an integer number which tells the kernel which device driver entry point to use.
minor The minor device number tells the kernel which subunit the node corresponds to on the device; for example, a subunit may be a file
system partition or a tty line.
owner:group
The owner group operand pair is optional, however, if one is specified, they both must be specified. The owner may be either a
numeric user ID or a user name. If a user name is also a numeric user ID, the operand is used as a user name. The group may be
either a numeric group ID or a group name. Similar to the user name, if a group name is also a numeric group ID, the operand is used
as a group name.
Major and minor device numbers can be given in any format acceptable to strtoul(3), so that a leading '0x' indicates a hexadecimal number,
and a leading '0' will cause the number to be interpreted as octal.
The mknod utility can be used to recreate deleted device nodes under a devfs(5) mount point by invoking it with only a filename as an argu-
ment. Example:
mknod /dev/cd0
where /dev/cd0 is the name of the deleted device node.
COMPATIBILITY
The chown(8)-like functionality is specific to FreeBSD.
As of FreeBSD 4.0, block devices were deprecated in favour of character devices. As of FreeBSD 5.0, device nodes are managed by the device
file system devfs(5), making the mknod utility superfluous. As of FreeBSD 6.0 device nodes may be created in regular file systems but such
nodes cannot be used to access devices.
SEE ALSO mkfifo(1), mknod(2), devfs(5), chown(8)HISTORY
A mknod utility appeared in Version 6 AT&T UNIX.
BSD January 31, 2010 BSD