With the 4 disks that are showing the same geometry I just wonder whether format is seeing the same 2 drives twice; or are there really four separate physical drives? (ie, 5 in all)?
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 FREEBSD
atapicam
ATAPICAM(4) BSD Kernel Interfaces Manual ATAPICAM(4)NAME
atapicam -- CAM XPT (transport) module for ATAPI devices
SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file:
device scbus
device ata
device atapicam
Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):
atapicam_load="YES"
DESCRIPTION
The ATAPI/CAM module allows ATAPI devices (CD-ROM, CD-RW, DVD drives, floppy drives such as Iomega Zip, tape drives) to be accessed through
the SCSI subsystem, cam(4).
ata(4) and scbus(4) must be configured in the kernel as well. The SCSI target drivers (cd(4), da(4), or st(4)) can then be used to access
the devices. The generic passthrough device, pass(4), can also be used to send SCSI commands directly to the devices through the CAM API.
A separate CAM bus is created for each ATA bus in the system. On each of these buses, target ID 0 is assigned to the master device, and ID 1
is assigned to the slave (provided they are ATAPI devices).
IMPLEMENTATION NOTES
Some SCSI commands are intercepted by the driver, and undergo special processing in order to work around limitations of ATAPI devices. Such
limitations can be consequences of the ATAPI specification. For example, ATAPI devices do not implement the 6-byte versions of MODE_SELECT,
MODE_SENSE, READ, or WRITE. They can also be common bugs, such as hanging when queried for extended INQUIRY information.
EXAMPLES
device ata
device atapicam
device scbus
device cd
device pass
Add the atapicam driver to the kernel.
camcontrol devlist
Print the list of all devices available through CAM.
mount -t cd9660 /dev/cd0 /mnt
Mount a CD-ROM from an ATAPI CD-ROM drive (the command above assumes that the ATAPI drive is the only CD-ROM unit).
SEE ALSO ata(4), cam(4), scsi(4), atacontrol(8), camcontrol(8)HISTORY
The ATAPI/CAM driver first appeared in FreeBSD 4.8 and FreeBSD 5.0.
AUTHORS
The ATAPI/CAM driver was written by Thomas Quinot <thomas@FreeBSD.org>.
BUGS
atapicam and ATAPI-specific target drivers (acd(4), ast(4), and afd(4)) can be configured in the same kernel. Simultaneous access to the
same device through the SCSI generic drivers and the ATAPI-specific drivers may cause problems and is strongly discouraged.
BSD October 22, 2009 BSD