Sponsored Content
Operating Systems Solaris Second Mirror is not booting ! Post 302758893 by top.level on Monday 21st of January 2013 03:30:13 AM
Old 01-21-2013
any advice ..
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

sun mirror

I have a solaris 9 machine which I would like to mirror it system disk using disk suite but my sun solaris machine has one internal disk which has the OS installed on. I have spare external disk of the same size, is it possible to mirror and internal disk with external disk using disk suite? ... (3 Replies)
Discussion started by: hassan2
3 Replies

2. UNIX for Dummies Questions & Answers

mirror device

Hi I'm new Solaris. I'm trying to understand how a root device is being mirrored. When do df -k I get this: Filesystem kbytes used avail capacity Mounted on /dev/md/dsk/d0 49915840 43168158 6248524 88% / /proc 0 0 0 0% /proc... (1 Reply)
Discussion started by: ND6
1 Replies

3. AIX

how to mirror raid5

Hi, I have an ssa filesystem to move to san. We don't want any downtime. I heard that you can do a mirroring of existing file system on the san. The file system is a type of either raid 0, raid 1, or raid 5. Anyone know how to do this? Thanks in advance, itik (4 Replies)
Discussion started by: itik
4 Replies

4. Solaris

ZFS Mirror versus Hardware Mirror

I've looked a little but haven't found a solid answer, assuming there is one. What's better, hardware mirroring or ZFS mirroring? Common practice for us was to use the raid controllers on the Sun x86 servers. Now we've been using ZFS mirroring since U6. Any performance difference? Any other... (3 Replies)
Discussion started by: Lespaul20
3 Replies

5. Solaris

Problems during booting from mirror disk

Hi All, I have detached a mirror and primary disk from my Solaris box. On trying to boot from Primary disk, It boots up good. But from my mirror disk, it is not booting and giving me the login prompt Instead it goes to maintenance state by issuing a coredump. Can you explain why... (9 Replies)
Discussion started by: jegaraman
9 Replies

6. Solaris

Solaris 10: Problems booting off mirror drive -- Error 22: No such partition

Solaris 10 5/08 on Ultra 40 M2 It boots fine off primary disk but having issues booting off the mirror disk. I get this error when booting off mirror disk: Booting 'Solaris 10 ... Mirror disk' root (hd1,0,a) Error 22: No such partition Press any key to continue... Any... (7 Replies)
Discussion started by: etc
7 Replies

7. Solaris

What is mirror and sub mirror in RAID -1 SVM

Hi , I am new to SVM .when i try to learn RAID 1 , first they are creating two RAID 0 strips through metainit d51 1 1 c0t0d0s2 metainit d52 1 1 c1t0d0s2 In the next step metainit d50 -m d51 d50: Mirror is setup next step is metaattach d50 d52 d50 : submirror d52 is... (7 Replies)
Discussion started by: vr_mari
7 Replies

8. Solaris

Mirror patching

HI Friends.... kindly explain os mirror patching?in SVM and Vxvm. :wall: (1 Reply)
Discussion started by: Rajesh_Apple
1 Replies

9. HP-UX

What is the difference between DRD and Root Mirror Disk using LVM mirror ?

what is the difference between DRD and Root Mirror Disk using LVM mirror ? (3 Replies)
Discussion started by: maxim42
3 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:40 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy