08-04-2006
Oops, sorry. You are right. It is /dev/md...
What version of Disksuite are you using? What Sun architecture?
I remember such errors having to do with the block size of the file system.
10 More Discussions You Might Find Interesting
1. HP-UX
Being somewhat extremely new to Unix, I have just had a system crash
One of my Volume Groups has crashed
However, this Volume Group is actually mirrored
How do I switch to use the mirrored copy?
Any assistance greatly appreciated
Thanks (1 Reply)
Discussion started by: cobdeng
1 Replies
2. Solaris
Is it possible to create a Mirror with zfs ??
I'm experimented user with Solstice Disk suite.
Or Sun Volume manager or veritas volume manager.
But, i would like switch from Disksuite to Zfs.
All my mirrored disks. (1 Reply)
Discussion started by: simquest
1 Replies
3. UNIX for Dummies Questions & Answers
I have 2 drives on a sun solaris 8 server that is a live server. I am putting in an additional 2 drives and want to mirror the the first 2. I was thinking of using disksuite but one drive is the root drive with 1 maybe 2 free paritions. The other is only one partition (36G). I was wondering... (2 Replies)
Discussion started by: csgonan
2 Replies
4. AIX
Hello,
I've got 2 system disks (hdisk0 and hdisk1) in the mirror (RAID1) on AIX 5.3. Since the hdisk1 makes some troubles, we want to replace it with the new one. How can I disable this hdisk1 disk and prepare the mirror to use the new physical disk? As far as I know, I must remove disk from the... (3 Replies)
Discussion started by: Yac
3 Replies
5. UNIX for Dummies Questions & Answers
hi.. newbie here, just wonder why there is a need for mirroring in some servers whereby we already had backups by cron jobs ? (4 Replies)
Discussion started by: Exposure
4 Replies
6. Solaris
Hi all
I wish to mirror for the root disk, but last time i do, make the server cannot boot up. :p So this time, hope you guys can assist me on it. =)
At the last code, is the step i wish to do. Please help to check and correct me if got any wrong.
root@leo # format </dev/null
Searching for... (17 Replies)
Discussion started by: SmartAntz
17 Replies
7. Solaris
Long time Linux, relatively new to Solaris.
Currently I have a Solaris 9 machine which has a mirrored root disk. We will be running some tests on this machine, and when those tests are done we want to restore it to "pre-test" status.
What I would like to do is break the mirror, pull the first... (2 Replies)
Discussion started by: brianr
2 Replies
8. AIX
hello folks,
I have a 300GB ROOTVG volume groups with one filesystem /backup having 200GB allocated space
Now, I cannot alt disk clone or mirrorvg this hdisk with another smaller disk. The disk size has to be 300GB; I tried alt disk clone and mirrorvg , it doesn't work. you cannot copy LVs as... (9 Replies)
Discussion started by: filosophizer
9 Replies
9. HP-UX
what is the difference between DRD and Root Mirror Disk using LVM mirror ? (3 Replies)
Discussion started by: maxim42
3 Replies
10. Solaris
Hello all,
i have the mirror disk problem with SunOS 5.10.
here's the message:
# metastat d15
d15: Mirror
Submirror 0: d16
State: Needs maintenance
Submirror 1: d17
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel... (4 Replies)
Discussion started by: rwprabowo
4 Replies
MEM(4) Linux Programmer's Manual MEM(4)
NAME
mem, kmem, port - system memory, kernel memory and system ports
DESCRIPTION
/dev/mem is a character device file that is an image of the main memory of the computer. It may be used, for example, to examine (and even
patch) the system.
Byte addresses in /dev/mem are interpreted as physical memory addresses. References to nonexistent locations cause errors to be returned.
Examining and patching is likely to lead to unexpected results when read-only or write-only bits are present.
Since Linux 2.6.26, and depending on the architecture, the CONFIG_STRICT_DEVMEM kernel configuration option limits the areas which can be
accessed through this file. For example: on x86, RAM access is not allowed but accessing memory-mapped PCI regions is.
It is typically created by:
mknod -m 660 /dev/mem c 1 1
chown root:kmem /dev/mem
The file /dev/kmem is the same as /dev/mem, except that the kernel virtual memory rather than physical memory is accessed. Since Linux
2.6.26, this file is available only if the CONFIG_DEVKMEM kernel configuration option is enabled.
It is typically created by:
mknod -m 640 /dev/kmem c 1 2
chown root:kmem /dev/kmem
/dev/port is similar to /dev/mem, but the I/O ports are accessed.
It is typically created by:
mknod -m 660 /dev/port c 1 4
chown root:kmem /dev/port
FILES
/dev/mem
/dev/kmem
/dev/port
SEE ALSO
chown(1), mknod(1), ioperm(2)
COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the
latest version of this page, can be found at https://www.kernel.org/doc/man-pages/.
Linux 2015-01-02 MEM(4)