Hi Guys,
Need to add 2 disks into a JBOD array (3310).
Does anyone see anything wrong with my Procedure / Doco below?
1> Logon to system, check system logs for abnormal entries.
2> Make backups of related system files:
A>cp -p /etc/system /etc/system.backup.081505
B>cp -p /etc/vfstab... (3 Replies)
Hi there,
My task is to replace the two 73 G disks with two 143 G disks , which has vxvm 4.1 running on it. I would like to know whether the steps iam following are correct.
1. Break the sub-disks, plexes of the root mirror.
2. Remove the sub-disks,plexes of the root mirror.
3. Remove one of... (10 Replies)
Hi all,
we have an existing system that was configured using just one of the (two) internal disks. I want to mirror the disk using SVM, but have realised there is no free slice for creating the metadb's. Is there a workaround I can use for this?
In the past we have always kept slice 7 free -... (8 Replies)
Really sorry for the long posting. But i would really want to clear all the doubts.
I have 2 disk c0t0d0 & c0t1d0, i wanted to mirror c0t1d0 (mirror) to c0t0d0 (main).
Creating state database replica:
metadb -a -c3 -f c0t0d0s7
... (3 Replies)
Hello All,
I am trying to mirror two non-root hard drives using zfs. But "fmthard" fails when I try to copy the vtoc due to disk mismatch. Please help me.
--- iostat command shows the disk to be similiar
--- format command shows disk to be different :confused:
--- c1t2d0 is the active... (8 Replies)
Need a procedure document to do "root disk mirroring in solaris volume manager for solaris 10". I hope some one will help me asap. I need to do it production environment.
Let me know if you need any deatils on this.
Thanks,
Rama (1 Reply)
We have two node cluster with OS disk mirrored under SVM. There is slight disk problem on one of the mirror disk causing cluster to panic.
Failure of one mirror disk causing VCS to panic the node. Why VCS is not able to write /var filesystem, as one of the disk is healthy.
... (1 Reply)
Discussion started by: amlanroy
1 Replies
LEARN ABOUT NETBSD
genfb
GENFB(4) BSD Kernel Interfaces Manual GENFB(4)NAME
genfb -- generic framebuffer console driver
SYNOPSIS
genfb* at pci?
genfb* at sbus?
wsdisplay* at genfb?
DESCRIPTION
The genfb driver provides support for generic framebuffers that have no native driver. All it needs are some parameters to describe the
framebuffer and an address.
PCI
When attaching to a pci(4) bus the driver is configured via device properties:
width (uint32)
Width in pixels.
height (uint32)
Height in pixels.
stride (uint32)
Line size in bytes.
depth (uint32)
Bits per pixel.
is_console (bool)
If true, genfb will try to become the system console.
address (uint32)
Bus address of the framebuffer.
SBus
When attaching to sbus(4) all those parameters are retrieved from the firmware.
SEE ALSO pci(4), sbus(4), wscons(4), wsdisplay(4)BUGS
There is no way to change the color map even when the firmware supports it. The pci(4) bus frontend has only been tested on macppc, i386,
and amd64 and requires machine dependent code to pass the properties mentioned above. So far only macppc, i386, and amd64 provides them.
BSD August 23, 2009 BSD