02-22-2010
Raid 5
---------- Post updated at 01:20 PM ---------- Previous update was at 09:45 AM ----------
Turns out I had some dead paths to the SAN. Did an rmdev -dl diskname and ran cfgmgr and all is good now.
Thanx!
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hello all,
Strange problem on p5 520 server. I've created two volume groups, filesystems, etc.. Everything working fine, without any problem. After some tests with a DS4300 unit I wanted to remove the volume groups, change the DS4300 configuration, and re-create a new volumegroup. However, I'm... (0 Replies)
Discussion started by: EricBE
0 Replies
2. AIX
Is it necessary to put system into single user mode for applying aix 5.3 TL8 on a aix 5.3.5.0 system ?
Is the TL8 installation not totally safe ?
thank you. (6 Replies)
Discussion started by: astjen
6 Replies
3. AIX
Good evening,
Thanks a lot for your help, we appreciate it a bunch. Heres basically a summary of what we have (sorry Im adding some extra history as well):
We have 2 Ibm Servers (Hag and Aki) that are running AIX Version 5. Each connect to a SAN device via 2 separate fiber paths. Hag seems to... (9 Replies)
Discussion started by: aix-olympics
9 Replies
4. AIX
Hello,
On Aix 5.3, during importvg, the varyonvg fails:
importvg -y vgtest hdisk20
0516-013 varyonvg: The volume group cannot be varied on because
there are no good copies of the descriptor area.
When i use manually the command varyonvg -u -b -t vgtest to force, the vg can... (3 Replies)
Discussion started by: dantares
3 Replies
5. AIX
Using nimadm:
nimadm -j nimadmvg -c sap024 -s spot_6100 -l lpp_6100 -d "hdisk1" -Y
Initializing the NIM master.
Initializing NIM client sap024.
0505-205 nimadm: The level of bos.alt_disk_install.rte installed in SPOT
spot_6100 (6.1.3.4) does not match the NIM master's level (7.1.1.2).... (2 Replies)
Discussion started by: sciacca75
2 Replies
6. AIX
Hi all,
I am not sure whether anyone of you using XIV to copy vg from one host to another. After I managed to copy all the respective vg over to destination vg, and map all vg to destination and when come to varyonvg, I got the following error
0516-510 varyonvg: Physical volume not found for... (2 Replies)
Discussion started by: ckwan
2 Replies
7. AIX
Hello,
I've set up email alerts on AIX Servers. so that i can get email notifications (via mail relay server) when ever there is abnormal behavior.
for example
1) my script monitors CPU/disk/memory etc... when it reaches high water ark, it will send an email alert.
2) disk usage alerts
3)... (5 Replies)
Discussion started by: System Admin 77
5 Replies
8. AIX
Iam new to AIX
I am unable varyonvg on the vios,some of the disk are reported as harware failure.
I am going to replace the disk,Please tell me how to remove the disk without any corruption in the VG
lspv -l hdiskx also didn't work (0 Replies)
Discussion started by: roayaix
0 Replies
9. AIX
I am running AIX 7.1 and currently we have samba 3.6.25 installed on the server. As it stands some AIX folders are shared that can be accessed by certain Windows users.
The problem is that since Windows 10 the guest feature no longer works so users have to manually type in their Windows login/pwd... (14 Replies)
Discussion started by: linuxsnake
14 Replies
LEARN ABOUT SUSE
captoinfo
captoinfo(1) General Commands Manual captoinfo(1)
NAME
captoinfo - convert a termcap description into a terminfo description
SYNOPSIS
captoinfo [-vn width] [-V] [-1] [-w width] file . . .
DESCRIPTION
captoinfo looks in file for termcap descriptions. For each one found, an equivalent terminfo description is written to standard output.
Termcap tc capabilities are translated directly to terminfo use capabilities.
If no file is given, then the environment variable TERMCAP is used for the filename or entry. If TERMCAP is a full pathname to a file,
only the terminal whose name is specified in the environment variable TERM is extracted from that file. If the environment variable TERM-
CAP is not set, then the file /usr/share/terminfo is read.
-v print out tracing information on standard error as the program runs.
-V print out the version of the program in use on standard error and exit.
-1 cause the fields to print out one to a line. Otherwise, the fields will be printed several to a line to a maximum width of 60 charac-
ters.
-w change the output to width characters.
FILES
/usr/share/terminfo Compiled terminal description database.
TRANSLATIONS FROM NONSTANDARD CAPABILITIES
Some obsolete nonstandard capabilities will automatically be translated into standard (SVr4/XSI Curses) terminfo capabilities by captoinfo.
Whenever one of these automatic translations is done, the program will issue an notification to stderr, inviting the user to check that it
has not mistakenly translated a completely unknown and random capability and/or syntax error.
XENIX termcap also used to have a set of extension capabilities for forms drawing, designed to take advantage of the IBM PC high-half
graphics. They were as follows:
If the single-line capabilities occur in an entry, they will automatically be composed into an acsc string. The double-line capabilities
and GG are discarded with a warning message.
IBM's AIX has a terminfo facility descended from SVr1 terminfo but incompatible with the SVr4 format. The following AIX extensions are
automatically translated:
Additionally, the AIX box1 capability will be automatically translated to an acsc string.
Hewlett-Packard's terminfo library supports two nonstandard terminfo capabilities meml (memory lock) and memu (memory unlock). These will
be discarded with a warning message.
NOTES
This utility is actually a link to tic(1), running in -I mode. You can use other tic options such as -f and -x.
The trace option is not identical to SVr4's. Under SVr4, instead of following the -v with a trace level n, you repeat it n times.
SEE ALSO
infocmp(1), ncurses(3NCURSES), terminfo(5)
This describes ncurses version 5.7 (patch 20100109).
AUTHOR
Eric S. Raymond <esr@snark.thyrsus.com>
captoinfo(1)