11-19-2017
coz i want to keep the links, permissions, owners, etc.
old school way. so i was wondering if nowadays there are better ways specially if a SAN storage is involved (as opposed to physical hd to hd).
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello all,
I have looked at the entire posting that have SAN in it and I'm still fuzzy on how SAN works. I understand that every disk array can be access from any server that needs it, but is there software that is install or NFS mount type situation. One post stated that if your format command... (7 Replies)
Discussion started by: larry
7 Replies
2. AIX
hi
We have 2 AIX nodes running with HACMP and all of them connected to SAN,
Our shared storage is shark; I need to create shared volume group and I need the HACMP take a ware of it.
Regards (1 Reply)
Discussion started by: h2aix
1 Replies
3. HP-UX
Hi, I'm going to be involved in a migration of SAN islands to one big SAN. I've not worked with SANs before and I'm not sure how to approach this. I suspect the disk devices on the HP servers are going to change, when the EVA's and servers are plugged into this new Cisco 9509 switch.
Any... (0 Replies)
Discussion started by: Hils
0 Replies
4. Solaris
I am about to attempt to connect my sun 280R boxes to a EMC SAN.
I have Qlogic cards that came from Sun.
I am going to load traffic manager, navisphere client.
what else do i need, sun foundation suite ro somehting?
This is the first time ive ever connected to a SAN.
any help would be... (3 Replies)
Discussion started by: BG_JrAdmin
3 Replies
5. Solaris
Hi everyone,
I wonder if I can canvas any opinions or thoughts (good or bad) on SAN attaching a SUN V880/490 to an EMC Clarion SAN?
At the moment the 880 is using 12 internal FC-AL disks as a db server and seems to be doing a pretty good job. It is not I/O, CPU or Memory constrained and the... (2 Replies)
Discussion started by: si_linux
2 Replies
6. AIX
Dera all
I have error repeating for two day, when I checked the error log by errpt command:
------------------------------------------------------------------------
LABEL: SC_DISK_ERR2
IDENTIFIER: 79B0DF89
Date/Time: Wed Oct 31 02:41:36 SAUS
Sequence Number: 9000... (1 Reply)
Discussion started by: magasem
1 Replies
7. Linux
Hello everyone.
I was wondering if there is a way to increase the size on the LUN on a SAN and make the Linux kernel understand the changes without restarting?
In the past it has always been rebooted to see the new values but im sure that there is a way now for the lvm to see the Free PE in... (8 Replies)
Discussion started by: d_ark
8 Replies
8. UNIX for Dummies Questions & Answers
hi guys
I installed Centos 5.5 (local disk). I am using 2 HBAs
Now I mapped 5 LUNs from a Storage.
I will be using LVM
just to test I assigned a LUN I've read I have to use multipath to avoid my Centos see the LUN twice
I enabled mdmpd and multipathd...
something else I should do?
... (8 Replies)
Discussion started by: kopper
8 Replies
9. AIX
Can anyone recommend a good book on san storage basics and how it communicates with an AIX server? (1 Reply)
Discussion started by: NycUnxer
1 Replies
10. AIX
Has anyone tried SAN to SAN mirroring on IBM DS SAN Storage.
DS5020 mentions Enhanced Remote Mirror to multi-LUN applications
I wonder if Oracle High availibility can be setup using Remote Mirror option of SAN ? (1 Reply)
Discussion started by: filosophizer
1 Replies
LEARN ABOUT HPUX
diskowner
diskowner(1M) diskowner(1M)
NAME
diskowner - retrieve the owner of a storage device
SYNOPSIS
path
DESCRIPTION
The command is used to retrieve the subsystem, if any, which is using the specified path. The command is intended to help prevent users
from overwriting storage that is already in use. The command will print out the owner of the path, or if no owner was found. A storage
device is considered owned by a subsystem if it has been formatted by that subsystem. For example, if a disk contains a VxFS filesystem,
but is not mounted or in use, it is still considered owned by the VxFS subsystem.
If the path specified is invalid or inaccessible, an error message will be printed.
Options and Arguments
The command recognizes the following options and arguments:
path The path name to the storage device. The path may be a symbolic link, as long as it points to a storage device, such as a file,
disk, or logical volume.
List all the owners of the specified path, seperated by commas
Produce a compact output that is easily parsed by other scripts and
programs. When used with option, displays all the owners seperated by dots This format is described in the section below.
Output from diskowner
displays the following possible output:
owner The owner of the given path. owner can be one of the following:
The path is not owned by any known subsystem.
The path is part of an LVM volume group.
The path is part of a VxVM volume group.
The path has a VxFS filesystem on it.
The path has a HFS filesystem on it.
The path is being used as a swap device.
The path is being used as a dump device.
The path is part of an Oracle database.
The path has EFI partitions on it.
message An error message displayed when the given path is invalid or inaccessible.
Compact Listing
The option generates a compact, colon delimited listing that is easy to parse. The output format is:
and so forth.
The option, when used with the option, produces this output format:
and so forth.
The current command prints out the keys and values listed below. In the future, new keys and/or values may be added to the output.
or
or
where
path is the pathname passed as argument
owner is the owner of the given path
message is an error message when given path is invalid or inaccessible.
n is number of owners of the given path
EXTERNAL INFLUENCES
Environment Variables
determines the language in which messages are displayed.
If is not specified or is null, it defaults to "C" (see lang(5)).
If any internationalization variable contains an invalid setting, all internationalization variables default to "C" (see environ(5)).
RETURN VALUE
Upon completion, returns one of the following values:
The path is not owned (the owner is
The path is already owned by a subsystem.
The path does not exist.
Invalid options or library version incompatible.
The path cannot be opened due to an I/O error.
The path cannot be opened due to insufficient permissions.
The path format is invalid.
EXAMPLES
Display the owner of a disk path:
Display the owner of a logical volume in compact output:
Display all the owners of a disk path:
Display all the owners of a logical volume in compact output:
SEE ALSO
crashconf(1M), df(1M), swapinfo(1M), vgdisplay(1M), vxvmboot(1M), vxassist(1M), fstab(4).
diskowner(1M)