Sponsored Content
Operating Systems Solaris Solaris 10 booting from EMC SAN DISK Post 302758525 by top.level on Sunday 20th of January 2013 02:04:05 AM
Old 01-20-2013
no and how to can I do that ?

Please explain to me and advice
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Solaris 10 not booting with mirrored disk

Hi all, I have a V490 running with Solaris 10. The OS disk was mirrored. I wanted to break the mirror, boot with the secondary mirror, and re-mirror the OS with a new disk. This is what I did, detached the metadevices of the secondary mirror disk (disk 1) metaclear-ed the metadevices,... (1 Reply)
Discussion started by: nitinp82
1 Replies

2. Solaris

Thoughts/experiences of SAN attaching V880 to EMC SAN

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

3. AIX

Configurin EMC SAN disks on AIX

This may sound like an absolute rookie question, and it is. I have been working on Migrating our HP and Solaris servers to the new EMC SAN and know the routines backwards. Now we've suddenly got a new IBM server and I don't even know how to check if it is connected to the switch. Can someone... (1 Reply)
Discussion started by: ronellevan
1 Replies

4. AIX

hard disk and san

Hello everyone I got several aix boxes with aix 5.3 I got a ibm san ds4500 My question is How can I do a match between my disks on aix and the san? I try to do a match with the LUN but for example. In my san I got several 1 LUN and on one of my aix box I got this If I type lscfg... (4 Replies)
Discussion started by: lo-lp-kl
4 Replies

5. Solaris

SAN disk failure

hi all, have a solaris 9 OS and a SAN disk which used to work fine is not getting picked up by my machine. can anyone point out things to check in order to troubleshoot this ?? thanks in advance. (3 Replies)
Discussion started by: cesarNZ
3 Replies

6. UNIX for Dummies Questions & Answers

Booting off of a SAN

Hello, I'm posting this in the "Unix for Dummies" forum, since it is more of a theoretical question than an exact problem/fix I'm inquiring about. I have a SunFire T2000 server with 4 internal hard drives, running Solaris 10. (So far so good :) The company just purchased a large EMC SAN. ... (5 Replies)
Discussion started by: FredSmith
5 Replies

7. Solaris

How to read EMC disk space

Hi I am using Solaris8.I want to find the total disk space of my server.Can anyone please tell that which field in below mentioned code signifies the disk space and whether this space is in Mb or GB. c11t0d52 <EMC-SYMMETRIX-5264 cyl 4 alt 2 hd 15 sec 64> ... (4 Replies)
Discussion started by: sharmaankur85
4 Replies

8. Solaris

Installing Solaris OS on LDOM SAN Disk

I have viewed a few previous posts regarding this, but none of them quite described or worked with my issue. I am out of local disk space on my LDOM Manager but still have plenty of SAN vCPU and Memory available so I am trying to install a new LDOM OS on SAN. I have exposed the SAN to the... (0 Replies)
Discussion started by: MobileGSP
0 Replies
MADVISE(2)						      BSD System Calls Manual							MADVISE(2)

NAME
madvise, posix_madvise -- give advice about use of memory SYNOPSIS
#include <sys/mman.h> int madvise(void *addr, size_t len, int advice); int posix_madvise(void *addr, size_t len, int advice); DESCRIPTION
The madvise() system call allows a process that has knowledge of its memory behavior to describe it to the system. The advice passed in may be used by the system to alter its virtual memory paging strategy. This advice may improve application and system performance. The behavior specified in advice can only be one of the following values: MADV_NORMAL Indicates that the application has no advice to give on its behavior in the specified address range. This is the system default behavior. This is used with madvise() system call. POSIX_MADV_NORMAL Same as MADV_NORMAL but used with posix_madvise() system call. MADV_SEQUENTIAL Indicates that the application expects to access this address range in a sequential manner. This is used with madvise() system call. POSIX_MADV_SEQUENTIAL Same as MADV_SEQUENTIAL but used with posix_madvise() system call. MADV_RANDOM Indicates that the application expects to access this address range in a random manner. This is used with madvise() system call. POSIX_MADV_RANDOM Same as MADV_RANDOM but used with posix_madvise() system call. MADV_WILLNEED Indicates that the application expects to access this address range soon. This is used with madvise() system call. POSIX_MADV_WILLNEED Same as MADV_WILLNEED but used with posix_madvise() system call. MADV_DONTNEED Indicates that the application is not expecting to access this address range soon. This is used with madvise() system call. POSIX_MADV_DONTNEED Same as MADV_DONTNEED but used with posix_madvise() system call. MADV_FREE Indicates that the application will not need the information contained in this address range, so the pages may be reused right away. The address range will remain valid. This is used with madvise() system call. MADV_ZERO_WIRED_PAGES Indicates that the application would like the wired pages in this address range to be zeroed out if the address range is deallocated without first unwiring the pages (i.e. a munmap(2) without a preceding munlock(2) or the application quits). This is used with madvise() system call. The posix_madvise() behaves same as madvise() except that it uses values with POSIX_ prefix for the advice system call argument. RETURN VALUES
Upon successful completion, a value of 0 is returned. Otherwise, a value of -1 is returned and errno is set to indicate the error. ERRORS
madvise() fails if one or more of the following are true: [EINVAL] The value of advice is incorrect. [EINVAL] The address range includes unallocated regions. [ENOMEM] The virtual address range specified by the addr and len are outside the range allowed for the address space. LEGACY SYNOPSIS
#include <sys/types.h> #include <sys/mman.h> int madvise(caddr_t addr, size_t len, int advice); int posix_madvise(caddr_t addr, size_t len, int advice); The include file <sys/types.h> is necessary. The type of addr has changed. SEE ALSO
mincore(2), minherit(2), mprotect(2), msync(2), munmap(2), compat(5) HISTORY
The madvise function first appeared in 4.4BSD. The posix_madvise function is part of IEEE 1003.1-2001 and was first implemented in Mac OS X 10.2. BSD
June 9, 1993 BSD
All times are GMT -4. The time now is 06:43 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy