Today (Saturday) We will make some minor tuning adjustments to MySQL.

You may experience 2 up to 10 seconds "glitch time" when we restart MySQL. We expect to make these adjustments around 1AM Eastern Daylight Saving Time (EDT) US.

"issue AIX MPIO path closed"

Post #303032247 by Phat on Thursday 14th of March 2019 07:07:01 AM

Full Discussion: issue AIX MPIO path closed

Here are the output
[root@xxx] / > lspath
Enabled hdisk0  fscsi0
Enabled hdisk1  fscsi0
Enabled hdisk0  fscsi1
Enabled hdisk1  fscsi1
Enabled hdisk8  fscsi3
Enabled hdisk8  fscsi0
Enabled hdisk0  fscsi3
Enabled hdisk1  fscsi3
Enabled hdisk2  fscsi0
Enabled hdisk3  fscsi0
Enabled hdisk4  fscsi0
Enabled hdisk5  fscsi0
Enabled hdisk6  fscsi0
Enabled hdisk7  fscsi0
Enabled hdisk9  fscsi0
Enabled hdisk10 fscsi0
Enabled hdisk11 fscsi0
Enabled hdisk12 fscsi0
Enabled hdisk2  fscsi1
Enabled hdisk3  fscsi1
Enabled hdisk4  fscsi1
Enabled hdisk5  fscsi1
Enabled hdisk6  fscsi1
Enabled hdisk7  fscsi1
Enabled hdisk8  fscsi1
Enabled hdisk9  fscsi1
Enabled hdisk10 fscsi1
Enabled hdisk11 fscsi1
Enabled hdisk12 fscsi1
Enabled hdisk2  fscsi3
Enabled hdisk3  fscsi3
Enabled hdisk4  fscsi3
Enabled hdisk5  fscsi3
Enabled hdisk6  fscsi3
Enabled hdisk7  fscsi3
Enabled hdisk9  fscsi3
Enabled hdisk10 fscsi3
Enabled hdisk11 fscsi3
Enabled hdisk12 fscsi3

[root@xxx] / > lsdev -Cc disk
hdisk0  Available 23-T1-01 MPIO DS5100/5300 Disk
hdisk1  Available 23-T1-01 MPIO DS5100/5300 Disk
hdisk2  Available 23-T1-01 MPIO DS5100/5300 Disk
hdisk3  Available 23-T1-01 MPIO DS5100/5300 Disk
hdisk4  Available 23-T1-01 MPIO DS5100/5300 Disk
hdisk5  Available 23-T1-01 MPIO DS5100/5300 Disk
hdisk6  Available 23-T1-01 MPIO DS5100/5300 Disk
hdisk7  Available 23-T1-01 MPIO DS5100/5300 Disk
hdisk8  Available 23-T1-01 MPIO DS5100/5300 Disk
hdisk9  Available 23-T1-01 MPIO DS5100/5300 Disk
hdisk10 Available 23-T1-01 MPIO DS5100/5300 Disk
hdisk11 Available 23-T1-01 MPIO DS5100/5300 Disk
hdisk12 Available 23-T1-01 MPIO DS5100/5300 Disk


10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users


We are looking at running MPIO for it's redundancy and load balancing benefits. Does anyone know what pieces of software or modules are needed on the VIO server to get load balancing to work. Remember we are using EMC's DMX3500 storage system. We no longer want to use Powerpath. :rolleyes: ... (2 Replies)
Discussion started by: vxg0wa3
2 Replies

2. AIX

AIX 5.3 MPIO vs RDAC on DS4000 range

Hi I would like to ask what the benefits are of changing from RDAC to MPIO when connecting to a DS4000 on AIX 5.3? I have heard that IBM MPIO "might" support more than 1 active path to a LUN when connecting to a DS4800 through more than 1 host connection on the same AIX client. I understand that... (8 Replies)
Discussion started by: kimyo
8 Replies

3. AIX

AIX native MPIO

Hi folks, does anybody have a link to a documentation how to implement native MPIO on AIX? We are using EMC PowerPath and Datacore SanSymphony/Cambex for this so far and I wasn't able to find a good description on that topic. All I know so far is that mkpath, chpath and lspath are used to... (3 Replies)
Discussion started by: zaxxon
3 Replies

4. Red Hat

PATH issue on linux

If PATH is set to ../bin:../sbin:/usr/bin:/usr/local/bin (chunk of path string). Sometime when I try to execute ls command it says ../bin/ls not found. According to my understanding "ls" should be searched in all the path varibales that we set in the PATH varaibale. Is there any reason for the... (5 Replies)
Discussion started by: hansini
5 Replies

5. UNIX for Dummies Questions & Answers

issue with PATH

hello On Debian Lenny, I first ran apt-get install git-core and then removed it to install from source. The trouble is that when I typed git --version, I am get: -bash: /usr/bin/git: No such file or directory of course, git is now in /usr/local/bin I don't understand why since... (1 Reply)
Discussion started by: JCR
1 Replies

6. AIX

Uninstall native MPIO driver on AIX

Hi, I was trying to uninstall the native MPIO driver on the AIX 6.1 machine we have in our lab and ran into a whole bunch dependent filesets initially. I deleted the disks, fcsX, fscsiX, fcnetX and tried again, but ran into the same error. Subsequently, I figured out that the OS disks in... (4 Replies)
Discussion started by: ronykris
4 Replies

7. AIX

Upgrading from native MPIO to SDDPCM AIX 6.1

We have AIX 6.1 system attached to SAN disks (DS4700 and DS8100) thru SVC. Initially when the system was I forgot to install sddpcm drivers. and wanted to know how can i go with the installation of the sddpcm drivers. My understandin going thru the manual ... (3 Replies)
Discussion started by: mk8570
3 Replies

8. UNIX for Dummies Questions & Answers

PLease HELP!!! PATH variable issue

Hello, I logged in to the unix solaris with my user name and then I again logged in with the sudo bash -l command now when I do echo $PATH It shows me => /usr/bin:/usr/local/bin:/usr/bin/usr/sbin:/usr/ucb:/usr/local/bin How do i find out where is this file located for setting the... (3 Replies)
Discussion started by: siddhans
3 Replies

9. UNIX for Dummies Questions & Answers

SFTP Issue - Connection closed

Hi All, I have followed the steps to set up the public and private keys for SFTP setup. Somehow the SFTP is not working and I get following errors: ==> sftp -v remote_user@remote_host_name_changed OpenSSH_5.4p1, OpenSSL 0.9.8m 25 Feb 2010 debug1: Reading configuration data... (12 Replies)
Discussion started by: Hangman2
12 Replies

10. AIX

Failed mpio path on AIX5.3

I have found failed mpio path on AIX and enabled that failed path as below failed path on AIX bash-3.2# lspath -l hdisk10 Enabled hdisk10 fscsi0 Enabled hdisk10 fscsi0 Failed hdisk10 fscsi3 Enabled hdisk10 fscsi3 Enabled failed path as below chpath -l hdisk10 -p fscsi3 -s enable... (13 Replies)
Discussion started by: murali969
13 Replies
posix_spawn_file_actions_addclose(3C)			   Standard C Library Functions 		     posix_spawn_file_actions_addclose(3C)

posix_spawn_file_actions_addclose, posix_spawn_file_actions_addopen - add close or open action to spawn file actions object
#include <spawn.h> int posix_spawn_file_actions_addclose(posix_spawn_file_actions_t *file_actions, int fildes, ); int posix_spawn_file_actions_addopen(posix_spawn_file_actions_t *restrict file_actions, int fildes, const char *restrict path, int oflag, mode_t mode);
These functions add or delete a close or open action to a spawn file actions object. A spawn file actions object is of type posix_spawn_file_actions_t (defined in <spawn.h>) and is used to specify a series of actions to be performed by a posix_spawn(3C) or posix_spawn(3C) operation to arrive at the set of open file descriptors for the child process given the set of open file descriptors of the parent. A spawn file actions object, when passed to posix_spawn() or posix_spawnp(), specifies how the set of open file descriptors in the calling process is transformed into a set of potentially open file descriptors for the spawned process. This transformation occurs as though the specified sequence of actions was performed exactly once, in the context of the spawned process (prior to execution of the new process image), in the order in which the actions were added to the object. Additionally, when the new process image is executed, any file descriptor (from this new set) which has its FD_CLOEXEC flag set is closed (see posix_spawn(3C)). The posix_spawn_file_actions_addclose() function adds a close action to the object referenced by file_actions that causes the file descrip- tor fildes to be closed (as if close(fildes) had been called) when a new process is spawned using this file actions object. The posix_spawn_file_actions_addopen() function adds an open action to the object referenced by file_actions that causes the file named by path to be opened (as if open(path, oflag, mode) had been called, and the returned file descriptor, if not fildes, had been changed to fildes) when a new process is spawned using this file actions object. If fildes was already an open file descriptor, it is closed before the new file is opened. The string described by path is copied by the posix_spawn_file_actions_addopen() function.
Upon successful completion, these functions return 0. Otherwise, an error number is returned to indicate the error.
These functions will fail if: EBADF The value specified by fildes is negative or greater than or equal to {OPEN_MAX}. These functions may fail if: EINVAL The value specified by file_actions is invalid. ENOMEM Insufficient memory exists to add to the spawn file actions object. It is not considered an error for the fildes argument passed to these functions to specify a file descriptor for which the specified opera- tion could not be performed at the time of the call. Any such error will be detected when the associated file actions object is later used during a posix_spawn() or posix_spawnp() operation.
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface Stability |Standard | +-----------------------------+-----------------------------+ |MT-Level |MT-Safe | +-----------------------------+-----------------------------+
close(2), dup(2), open(2), posix_spawn(3C), posix_spawn_file_actions_adddup2(3C), posix_spawn_file_actions_destroy(3C), attributes(5), standards(5) SunOS 5.10 30 Jan 2004 posix_spawn_file_actions_addclose(3C)

Featured Tech Videos