08-11-2007
Hi there.
I ended up installing Disksuite and mirroring the drives and it went very smoothly (mirrored drive 0 to drive 2).
Since I have no free partitions on drive 1 and was considering using raidctl but I was wondering how automatic failover works with that? Disksuite modified vfstab, but if the live drive fails with raidctl, how does the second drive take over?
Thanks
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Does anyone know which packages I need to install to run Disk Suite on Solaris 7, or where I can find some documentation? (2 Replies)
Discussion started by: 98_1LE
2 Replies
2. Filesystems, Disks and Memory
Hi,
Ihave a Netra T1405 and would like to add 2 news disk (in mirror with SDS) in order to grow the size of the initial file system.
The idea is to mount a new partition in order to setup new products...
Could some one tell me the difrents steps to do this or give me links to documents.
... (1 Reply)
Discussion started by: guillaume35
1 Replies
3. 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
4. Solaris
Hi
I'm completely new to Solaris Disk Suite. Where can I go and read up about it. I've seen consultants run the meta- commands, but it doesn't make any sense to me. I would like to learn how it works and how to use it.
Thanks (1 Reply)
Discussion started by: soliberus
1 Replies
5. Solaris
hello everybody,
I have a system in Solaris 8 with SDS 4.2.1
I need to mirror the system disk which has the following characteristics :
* /dev/rdsk/c0t0d0s2 partition map
*
* Dimensions:
* 512 bytes/sector
* 133 sectors/track
* 27 tracks/cylinder
* 3591 sectors/cylinder... (3 Replies)
Discussion started by: aribault
3 Replies
6. Solaris
Solaris 9
We had a problem server where only root was not mirrored (before my time). When I tried to mirror it, the live root slice bailed with errors at 97% so it couldn't be mirrored.
It's a matched pair of boxes (nfs1 and nfs2) and they are interchangeable with regards to the NFS... (0 Replies)
Discussion started by: BOFH
0 Replies
7. Solaris
I am new to Solaris so please bear with me. I have spent enough time searching to get somewhat of a grip here but I am not sure what to do next. I am trying to grow a file system on a Solaris 8 server.
B_root@server:>df -k
Filesystem kbytes used avail capacity Mounted on... (9 Replies)
Discussion started by: NewSolarisAdmin
9 Replies
8. Solaris
I am doing disk mirroring and this command I entered:
metainit d202 1 1 c0t1d0s0
gives me this error "metainit: d202: no such file or directory"
The nmd value in /kernel/drv/md.conf is set to 2000.
Any ideas what this error means? (3 Replies)
Discussion started by: bluridge
3 Replies
9. 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
10. HP-UX
what is the difference between DRD and Root Mirror Disk using LVM mirror ? (3 Replies)
Discussion started by: maxim42
3 Replies
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:
+3 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) fails 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 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 2017-09-15 SD(4)