11-18-2013
Hi,
it looks like that the specific path is not (longer) available.
Maybe your storage admin has removed the mapping for this volume or the zoning for this path has been removed.
An lspath and lscfg -vl hdisk10 would be helpfull.
Regards
Last edited by -=XrAy=-; 11-18-2013 at 11:06 AM..
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. Solaris
Hi All,
The path requires me to go Single User mode. On single user mode, the patch still won't continue:
dhcpagent supports a new keyword in /etc/default/dhcpagent.
Please merge the existing /etc/default/dhcpagent with the
patched version of /etc/default/dhcpagent shipped with this... (2 Replies)
Discussion started by: itik
2 Replies
3. AIX
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. AIX
Hello All,
After creating lpp_source/spot from AIX 5.3TL6-07 DVD on the NIM(AIX6.1), I went online and download the fix pack for reaching TL8-04. (it was less than 200Mgegs total)
then I did define a newer lpp_source530TL8-04 via a copy from the older lpp_source530TL6-07 (I diduse a command... (2 Replies)
Discussion started by: sangers
2 Replies
5. AIX
On a particular LPAR, I was running AIX 5.3 TL 3. On Monday I did an update of the LPAR to 5.3 TL 9 SP2. The install was smooth, but then I ran into a problem.
The MPIO driver does not work with LSI's StoreAge (SVM4). I did some looking, and looks like
5.3 TL3 = IBM.MPIO 5.3.0.30
5.3... (0 Replies)
Discussion started by: clking
0 Replies
6. AIX
Hi,
we have a vew boxes using MPIO and they are connected to some virtualization software managing some disk subsystems, offering volumes to the AIX boxes.
Sometimes when a cable has been plugged out for a test or when a real problem occurs, using lspath to show the state of the paths shows... (8 Replies)
Discussion started by: zaxxon
8 Replies
7. AIX
Hello,
we are planning to deploy some of our databases on AIX/LPAR based servers (we didn't bought it yet ...). IBM's engineers says that if we want to boot them from SAN the hardware array has to be compatible with MPIO but they don't want to deliver any document with list of arrays supported... (5 Replies)
Discussion started by: andy55
5 Replies
8. 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
9. AIX
Hello,
I have some concerns over the disk management of my AIX system.
For example server1
/ > lspv
hdisk0 00fa6d1288c820aa rootvg active
hdisk1 00fa6d1288c8213c vg_2 active
hdisk2 00c1cc14d6de272b ... (6 Replies)
Discussion started by: Phat
6 Replies
10. AIX
Hello,
I have encountered the issue on my AIX 6.1. As you can see below, the hdisk1 & hdisk8 are not recognized by the system
/ > lspv
hdisk0 00fa6d1288c820aa rootvg active
hdisk1 00fa6d1288c8213c None
hdisk2 ... (9 Replies)
Discussion started by: Phat
9 Replies
rmdir(2) System Calls Manual rmdir(2)
Name
rmdir - remove a directory file
Syntax
rmdir(path)
char *path;
Description
The system call removes a directory file whose name is given by path. The directory must not have any entries other than dot (.) and dot-
dot (..).
If one or more processes have the directory open when the last link is removed, the dot and dot-dot entries, if present, are removed before
returns and no new entries may be created in the directory. The directory, however, is not removed until all references to the directory
have been closed.
Return Values
A zero (0) is returned if the remove succeeds; otherwise, a -1 is returned, and an error code is stored in the global location errno.
Diagnostics
The named file is removed unless one or more of the following are true:
[ENOTEMPTY] The named directory contains files other than dot and dot-dot.
[EPERM] The directory containing the directory to be removed is marked sticky, and neither the containing directory nor the direc-
tory to be removed are owned by the effective user ID.
[ENOTDIR] A component of the path is not a directory.
[ENOENT] The named directory does not exist or path points to an empty string and the environment defined is POSIX or SYSTEM_FIVE.
[EACCES] Search permission is denied for a component of the path prefix.
[EACCES] Write permission is denied on the directory containing the link to be removed.
[EBUSY] The directory to be removed is the mount point for a mounted file system.
[EROFS] The directory entry to be removed resides on a read-only file system.
[EFAULT] The path points outside the process's allocated address space.
[ELOOP] Too many symbolic links were encountered in translating the pathname.
[ENAMETOOLONG] A component of a pathname exceeded 255 characters, or an entire pathname exceeded 1023 characters.
[EIO] An I/O error occurred while deleting the directory entry or deallocating the inode.
[ETIMEDOUT] A connect request or remote file operation failed because the connected party did not properly respond after a period of
time that is dependent on the communications protocol.
See Also
mkdir(2), unlink(2)
rmdir(2)