12-03-2010
I was confused.. excuse me for my unclear post.. I am using MPIO that is why sdd does not see any devices.. thanks a lot
10 More Discussions You Might Find Interesting
1. Solaris
I just installed IBMsddsun64_........... on my sun server. I untarred it (tar xvf) & I tried to install the paxkage. When I did pkgadd -d ./IBMsdd..... I get a message Error, no packages were found.
Any idea
Thanks, (1 Reply)
Discussion started by: Remi
1 Replies
2. AIX
Hi all,
Sorry if this is in the wrong place but needed to make sure lots of people saw this so that hopefully someone will be able to help.
Basically i've upgraded a test server from 4.3 to 5.3 TL04.
The server has hdisk0 and 1 as rootvg locally but then has another vg setup on our ESS... (5 Replies)
Discussion started by: djdavies
5 Replies
3. UNIX for Advanced & Expert Users
Hi all,
Sorry if this is in the wrong place but needed to make sure lots of people saw this so that hopefully someone will be able to help.
Basically i've upgraded a test server from 4.3 to 5.3 TL04.
The server has hdisk0 and 1 as rootvg locally but then has another vg setup on our ESS... (1 Reply)
Discussion started by: djdavies
1 Replies
4. Filesystems, Disks and Memory
Hello Unix Admins:
Has any one in this distribution list implemented SVC (SAN Volume Contoller - A solution from IBM) in your environment? If you have, do you have any do's / don'ts? Anything which you like sharing would be really appreciated.
For example, my inputs:
I tried implementing... (1 Reply)
Discussion started by: kdossjojo
1 Replies
5. AIX
Can anyone recommend me some reading material surrounding how AIX handles LUNs:
- with and without MPIO installed
- with and without SDD or SDDPCM installed
Where does lspath sit in all of this (MPIO layer?). Can a system be built with just MPIO software? Is MPIO software even needed?
I guess... (0 Replies)
Discussion started by: apra143
0 Replies
6. Red Hat
I was wondering if there is a way of auto-detecting a new vpath, using IBM's SDD driver, on a Linux platform.
ON AIX it is a simple as running cfgmgr.
Alan (0 Replies)
Discussion started by: alanp
0 Replies
7. AIX
Hi folks.
We want to move a "physical" AIX box to a VIOed LPAR. The physical box is running SDD with disks from a DS8300. I want to be able to reattach those LUNs from the DS8300 to my VIO server which is running SDDPCM and then assigned them back to my AIX LPAR. Any thoughts about this?
I... (1 Reply)
Discussion started by: Stephan
1 Replies
8. Red Hat
Dear Guru,
IHAC who is using Redhat Linux 5 on DELL M910.
When system bootup, it show "Buffer I/O error on device sdd" error message. Below is the "dmesg" output.
The scenario is:
If more external FC SAN disk LUN add, the device would change other name. So it will impact the raw device... (7 Replies)
Discussion started by: devyfong
7 Replies
9. AIX
hi all
we recently upgraded our san switches. after that, i found i got many hdisks showing in lsdev with status "Defined" and "Available". the number of "Defined" is equal to "Available". the time stamp shows all "Available" disks created at our downtime night.
"datapath query device"... (0 Replies)
Discussion started by: rs6000er
0 Replies
10. AIX
This is getting very confusing for me, and appreciate if someone can help.
Platform: Power VM ( Virtual I/O Server)
ioslevel 2.1.3.10-FP23
# oslevel -s
6100-05-00-0000
Storage: IBM DS4300
Two HBAs - Dual Port Fibre Adapter Channels
Each card has two ports , so a total of 4 ports going... (3 Replies)
Discussion started by: filosophizer
3 Replies
LEARN ABOUT V7
vgimportclone
VGIMPORTCLONE(8) System Manager's Manual VGIMPORTCLONE(8)
NAME
vgimportclone - import and rename duplicated volume group (e.g. a hardware snapshot)
SYNOPSIS
vgimportclone [-n|--basevgname VolumeGroupName] [-i|--import] PhysicalVolume [PhysicalVolume...]
DESCRIPTION
vgimportclone is used to import a duplicated VG (e.g. hardware snapshot). Duplicate VG(s) and PV(s) are not able to be used until they are
made to coexist with the origin VG(s) and PV(s). vgimportclone renames the VG associated with the specified PV(s) and changes the associ-
ated VG and PV UUIDs.
OPTIONS
See lvm for common options.
-n|--basevgname VolumeGroupName
By default the snapshot VG will be renamed to the original name plus a numeric suffix to avoid duplicate naming (e.g. 'test_vg'
would be renamed to 'test_vg1'). This option will override the base VG name that is used for all VG renames. If a VG already
exists with the specified name a numeric suffix will be added (like the previous example) to make it unique.
-i|--import
Import exported Volume Groups. Otherwise VGs that have been exported will not be changed (nor will their associated PVs).
ENVIRONMENT VARIABLES
LVM_BINARY
The LVM2 binary to use. Defaults to "lvm".
EXAMPLES
The origin VG vg00 has origin PVs /dev/sda and /dev/sdb and the respective snapshot PVs are /dev/sdc and /dev/sdd. To rename the VG asso-
ciated with /dev/sdc and /dev/sdd from vg00 to vg00_snap (and to change associated VG and PV UUIDs) do:
vgimportclone --basevgname vg00_snap /dev/sdc /dev/sdd
SEE ALSO
lvm(8)
Red Hat, Inc. LVM TOOLS 2.02.95(2) (2012-03-06) VGIMPORTCLONE(8)