Sponsored Content
Operating Systems AIX cfgmgr and hdisk number allocation Post 302096560 by fosteria on Thursday 16th of November 2006 09:07:45 AM
Old 11-16-2006
Flashcopy Scripts

Hello again,

Further to my original post; I'm looking at our existing Flashcopy scripts and the related changes prior to adding our new disks. Can anybody ratify the following scripted processes (in principal) ?

Recreate Flashcopies :

(Shutdown database - quiesce i/o)

1. SMcli -n "FAStT700" -c 'recreateFlashcopy logicalDrive ["FC VOL 1-1"];
2. SMcli -n "FAStT700" -c 'create mapping logicalDrive="FC VOL 1-1" logicalUnitNumber=xx host="AIX HOST";
3.hot_add (actually cfmgr -l deviceclass)
4. chdev -l hdiskxx -a pv=clear;
5. recreatevg -y fc_vgname hdiskxx hdiskxx hdiskxx etc
6. mount /fc_filesystem

Disable Flashcopies :

1. umount /fc_filesystem
2. varyoffvg fc_vgname
3. export fc_vgname
4. rmdev -l hdiskxx (omitting -d which we run currently)
5. Smcli -n "FAStT700" -c 'delete mapping logicalDrive="FC VOL 1-1" host ="AIX HOST";
6. SMcli -n "FAStT700" -c 'disableFlashCopy logicalDrive ["FC VOL 1-1"];

Do I need to do 'chdev -l hdiskxx -a pv=yes' after the clear (step 4) in the recreate to switch the pv from defined to available again; or will the 'hot_add' do that anyway?

Also we got an error with a dirty jfs2 superblock the other night when we mounted the FC volumes. I was wondering about (a) adding a 'sync;sync;sync' call before creating the FCs to flush the buffers and (b) adding a full fsck of the FC volumes before they are mounted; I'm not sure what the policy is on this ??

Thanks in advance.
 

10 More Discussions You Might Find Interesting

1. AIX

LPAR and CFGMGR

I have a P570 that for some reason is not allowing the P1-T6 NIC to be recognized. I have confirmed from the HMC that it is set for the LPAR, but when I do a cfgmgr, it won't recognize it. It though is recognizing the slot cards just fine which are P1-C3 for one shelf and P1-C3 of another shelf.... (1 Reply)
Discussion started by: LegendMan
1 Replies

2. AIX

cfgmgr

Hi All, I remember my old senior mentor in AIX that cfgmgr should not be terminated on your console. Because if it's terminated in the middle, the odm might get corrupted. Is that true for AIX 5.x? Regards, itik (1 Reply)
Discussion started by: itik
1 Replies

3. AIX

cfgmgr: Filesets missing

Hi all, I have a System i server with a couple of AIX LPARs. One of the LPARs owns a dual-channel scsi adapter to which I connect a tape library (IBM TS3100) and a DVD Drive. I had some problems to get the Tape Library detected but finally I got it: rmt0 Available 03-08-01-4,0 IBM 3580... (1 Reply)
Discussion started by: wendelalexis
1 Replies

4. AIX

Dual port NIC, cfgmgr

OS: AIX 6.1 The host has a dual port NIC installed and when I went to run `cfgmgr -v` to configure it I got an error showing device packages are missing from the install: `cfgmgr -v` on 10.15.xx.xxx cfgmgr: 0514-621 WARNING: The following device packages are required for device support but... (3 Replies)
Discussion started by: b1f30
3 Replies

5. Programming

dynamic allocation vs static allocation in c

i wrote a tiny version of tail command using a large buffer statically allocated but, in a second time, i found another version in which i use a bidimensional array dynamically allocated. here is the first version /*my tiny tail, it prints the last 5 line of a file */ #include<stdio.h>... (4 Replies)
Discussion started by: lucasclaus
4 Replies

6. AIX

cfgmgr in my aix box

Hi When I run cfgmgr -v in my aix box I get the below error : cfgmgr: 0514-621 WARNING: The following device packages are required for device support but are not currently installed. devices.loopback My oslevel is 6100-06-02-1044 Please assist. Please use and tags when... (3 Replies)
Discussion started by: samsungsamsung
3 Replies

7. AIX

cfgmgr: 0514-621 WARNING

Dear all i have a sun SL500 tape library attached to my AIX box while issue the command cfgmgr i have the below issue test>cfgmgr cfgmgr: 0514-621 WARNING: The following device packages are required for device support but are not currently installed. devices.fcp.changer please... (3 Replies)
Discussion started by: thecobra151
3 Replies

8. Solaris

Block-based allocation and Extent-based allocation in Solaris

Hi guys! Could you tell me what's this figure about? (See the attached figure below.) This is a representation of block allocation filesystem and extent allocation filesystem in Solaris. Does this mean that in a block-based allocation, data are placed in individual blocks while in... (0 Replies)
Discussion started by: arah
0 Replies

9. AIX

Time taking for cfgmgr on dual VIO

Hi, From the man page, cfgmgr configures devices and optionally installs device software by running the programs specified in the Configuration Rules object class and it is not dependent on platform . Are there any fundamental differences impacting the speed of cfgmgr on a stand-alone and... (5 Replies)
Discussion started by: Sachin1987
5 Replies

10. Post Here to Contact Site Administrators and Moderators

Cfgmgr Error

Hi, My AIX server able to detect the LUN's which is mapped from IBM v7k storage, And i allocated one more LUN from HP storage but it's appear two hdisk instead of one and it's showing incorrect LUN ID. SDDPCM driver already installed on this server. During cfgmgr, Im getting this message :... (1 Reply)
Discussion started by: xinuadmin
1 Replies
VOL(1)							      General Commands Manual							    VOL(1)

NAME
vol - split input on or combine output from several volumes SYNOPSIS
vol [-rw1] [-b blocksize] [-m multiple] [size] device DESCRIPTION
Vol either reads a large input stream from standard input and distributes it over several volumes or combines volumes and sends them to standard output. The size of the volumes is determined automatically if the device supports this, but may be specified before the argument naming the device if automated detection is not possible or if only part of the physical volume is used. The direction of the data is automatically determined by checking whether the input or output of vol is a file or pipe. Use the -r or -w flag if you want to specify the direction explicitly, in shell scripts for instance. Vol waits for each new volume to be inserted, typing return makes it continue. If no size is explicitely given then the size of the device is determined each time before it is read or written, so it is possible to mix floppies of different sizes. If the size cannot be deter- mined (probably a tape) then the device is assumed to be infinitely big. Vol can be used both for block or character devices. It will buffer the data and use a block size appropriate for fixed or variable block sized tapes. Vol reads or writes 8192 bytes to block devices, usually floppies. Character devices are read or written using a multiple of 512 bytes. This multiple has an upper limit of 32767 bytes (16-bit machine), 64 kb (32-bit), or even 1 Mb (32-bit VM). The last partial write to a character device is padded with zeros to the block size. If a character device is a tape device that responds to the mtio(4) status call then the reported tape block size will be used as the smallest unit. If the tape is a variable block length device then it is read or written like a block device, 8192 bytes at the time, with a minimum unit of one byte. All sizes may be suffixed by the letters M, k, b or w to multiply the number by mega, kilo, block (512), or word (2). The volume size by default in kilobytes if there is no suffix. OPTIONS
-rw Explicitly specify reading or writing. Almost mandatory in scripts. -1 Just one volume, start immediately. -b blocksize Specify the device block size. -m multiple Specify the maximum read or write size of multiple blocks. The -b and -m options allow one to modify the block size assumptions that are made above. These assumptions are -b 1 -m 8192 for block devices or variable length tapes, and -b 512 -m 65536 for charac- ter devices (32 bit machine.) These options will not override the tape block size found out with an mtio(4) call. The multiple may be larger then the default if vol can allocate the memory required. EXAMPLES
To back up a tree to floppies as a compressed tarfile: tar cf - . | compress | vol /dev/fd0 To restore a tree from 720 kb images from possibly bigger floppies: vol 720 /dev/fd0 | uncompress | tar xfp - Read or write a device with 1024 byte blocks: vol -b 1k /dev/rsd15 Read or write a variable block length tape using blocking factor 20 as used by default by many tar(1) commands: vol -m 20b /dev/rst5 Note that -m was used in the last example. It sets the size to use to read or write, -b sets the basic block size that may be written in multiples. SEE ALSO
dd(1), tar(1), mt(1), mtio(4). VOL(1)
All times are GMT -4. The time now is 12:49 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy