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 CENTOS
sd
SD(4) Linux Programmer's Manual SD(4)NAME
sd - driver for SCSI disk drives
SYNOPSIS
#include <linux/hdreg.h> /* for HDIO_GETGEO */
#include <linux/fs.h> /* for BLKGETSIZE and BLKRRPART */
CONFIGURATION
The block device name has the following form: sdlp, where l is a letter denoting the physical drive, and p is a number denoting the parti-
tion on that physical drive. Often, the partition number, p, will be left off when the device corresponds to the whole drive.
SCSI disks have a major device number of 8, and a minor device number of the form (16 * drive_number) + partition_number, where drive_num-
ber is the number of the physical drive in order of detection, and partition_number is as follows:
partition 0 is the whole drive
partitions 1-4 are the DOS "primary" partitions
partitions 5-8 are the DOS "extended" (or "logical") partitions
For example, /dev/sda will have major 8, minor 0, and will refer to all of the first SCSI drive in the system; and /dev/sdb3 will have
major 8, minor 19, and will refer to the third DOS "primary" partition on the second SCSI drive in the system.
At this time, only block devices are provided. Raw devices have not yet been implemented.
DESCRIPTION
The following ioctls are provided:
HDIO_GETGEO
Returns the BIOS disk parameters in the following structure:
struct hd_geometry {
unsigned char heads;
unsigned char sectors;
unsigned short cylinders;
unsigned long start;
};
A pointer to this structure is passed as the ioctl(2) parameter.
The information returned in the parameter is the disk geometry of the drive as understood by DOS! This geometry is not the physical
geometry of the drive. It is used when constructing the drive's partition table, however, and is needed for convenient operation of
fdisk(1), efdisk(1), and lilo(1). If the geometry information is not available, zero will be returned for all of the parameters.
BLKGETSIZE
Returns the device size in sectors. The ioctl(2) parameter should be a pointer to a long.
BLKRRPART
Forces a reread of the SCSI disk partition tables. No parameter is needed.
The SCSI ioctl(2) operations are also supported. If the ioctl(2) parameter is required, and it is NULL, then ioctl(2) will fail
with the error EINVAL.
FILES
/dev/sd[a-h]: the whole device
/dev/sd[a-h][0-8]: individual block partitions
COLOPHON
This page is part of release 3.53 of the Linux man-pages project. A description of the project, and information about reporting bugs, can
be found at http://www.kernel.org/doc/man-pages/.
Linux 2012-05-03 SD(4)