Sponsored Content
Full Discussion: Root disk mirroring in SVM
Operating Systems Solaris Root disk mirroring in SVM Post 302760535 by hicksd8 on Thursday 24th of January 2013 07:23:58 AM
Old 01-24-2013
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)?

Post the output of:

Code:
 
mount

so we can see what the mounted devices are.
 

9 More Discussions You Might Find Interesting

1. Solaris

Solaris mirroring / non-root disk

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)
Discussion started by: BG_JrAdmin
3 Replies

2. Solaris

Veritas root disk mirroring

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)
Discussion started by: Jartan
10 Replies

3. Solaris

mirroring root disk using svm - but no free slices for metadb's

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)
Discussion started by: badoshi
8 Replies

4. Solaris

SVM, mirroring

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)
Discussion started by: beginningDBA
3 Replies

5. Solaris

Root Disk mirroring in SVM

Dear All, Please help me to configure root mirroring using SVM in Solaris 9. Thanks and Regards, Lakkireddy BR (3 Replies)
Discussion started by: lbreddy
3 Replies

6. Solaris

Disk mismatch while trying to zfs mirroring non-root disks

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)
Discussion started by: pingmeback
8 Replies

7. Solaris

root disk mirroring in solaris volume manager for solaris 10

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)
Discussion started by: ramareddi16
1 Replies

8. Solaris

Root disk mirroring in Solaris 10

I would like to perform root disk mirroring task. Can someone please help me out on this. Thanks !! Regards, Rama (2 Replies)
Discussion started by: ramagore85
2 Replies

9. UNIX for Advanced & Expert Users

VCS triggerring panic on 1 node, root disk under SVM

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
UDISKS(7)							      udisks								 UDISKS(7)

NAME
udisks - Storage Management DESCRIPTION
udisks provides an interface to enumerate storage devices and perform operations on them. Any application can access the org.freedesktop.UDisks service on the system message bus. Some operations (such as formatting disks etc.) is restricted using polkit. DEVICE INFORMATION
On Linux, udisks relies on recent versions of udev(7) and the kernel. Influential device properties in the udev database include: UDISKS_PRESENTATION_HIDE If set to 1 this is a hint to presentation level software that the device should not be shown to the user. UDISKS_PRESENTATION_NOPOLICY If set to 1 this is a hint to presentation level software that the device should not be automounted or autoassembled (for e.g. components of a multi-disk device). UDISKS_DISABLE_POLLING If set to 1 this will disable the polling of drives for media changes, for devices which do not send out media notifications by themselves (this mostly affects CD drives). Some CD drives cause bad effects such as very high CPU usage when being polled. UDISKS_PRESENTATION_NAME The name to user for the device when presenting it to the user. UDISKS_PRESENTATION_ICON_NAME The icon to use when presenting the device to the user. If set, the name must follow the freedesktop.org icon theme specification. The ID_DRIVE_* properties are used to describe what kind of physical media can be used in a device. These are typically set on the main block device (e.g. /dev/sdb) and more than one these properties can be set if the device supports multiple kinds of media. ID_DRIVE_EJECTABLE Whether the media in the drive is physically ejectable. Only set this to 1 (or 0) if the drive truly uses (or doesn't) ejectable media. In particular, it is not necessary to set this for e.g. iPod or Kindle devices where it is necessary to send a command via eject(1) since the desktop user session will offer this option for removable devices regardless of whether they are ejectable. If this property is not set, a heuristic will be used to determine if the media is ejectable (drives using optical, Zip or Jaz media are considered ejectable). ID_DRIVE_DETACHABLE Whether the device is detachable. It is only meaningful to set this to 0 (to avoid marking a device as detachable) since the code for detaching the device is part of udisks itself. If this property is not set, a heuristic will be used to determine if the drive is detachable (currently only devices connected through USB are detachable). ID_DRIVE_CAN_SPINDOWN Whether the device can spin down. It is only meaningful to set this to 0 (to avoid marking a device as being capable of spinning down) since the code for spinning down the device is part of udisks itself. If this property is not set, a heuristic will be used to determine if the drive can spin down (currently only ATA devices, including those USB devices with a SAT layer) can be spun down). ID_DRIVE_FLASH The device is compatible with flash. ID_DRIVE_FLASH_CF The device is compatible with Compact Flash. ID_DRIVE_FLASH_MS The device is compatible with Memory Stick. ID_DRIVE_FLASH_SM The device is compatible with SmartMedia. ID_DRIVE_FLASH_SD The device is compatible with SecureDigital. ID_DRIVE_FLASH_SDHC The device is compatible with High-Capicity SecureDigital. ID_DRIVE_FLASH_MMC The device is compatible with MultiMediaCard. ID_DRIVE_FLOPPY The device is compatible with floppy disk. ID_DRIVE_FLOPPY_ZIP The device is compatible with Zip. ID_DRIVE_FLOPPY_JAZ The device is compatible with Jaz. The ID_DRIVE_MEDIA_* properties describe the current media in a device. As with the ID_DRIVE_* properties, these properties are typically set on the main block device (e.g. /dev/sdb). Typically only one of these properties are set. ID_DRIVE_MEDIA_FLASH The physical media currently inserted into the device is flash. ID_DRIVE_MEDIA_FLASH_CF The physical media currently inserted into the device is Compact Flash. ID_DRIVE_MEDIA_FLASH_MS The physical media currently inserted into the device is Memory Stick. ID_DRIVE_MEDIA_FLASH_SM The physical media currently inserted into the device is SmartMedia. ID_DRIVE_MEDIA_FLASH_SD The physical media currently inserted into the device is SecureDigital. ID_DRIVE_MEDIA_FLASH_SDHC The physical media currently inserted into the device is High-Capicity SecureDigital. ID_DRIVE_MEDIA_FLASH_MMC The physical media currently inserted into the device is MultiMediaCard. ID_DRIVE_MEDIA_FLOPPY The physical media currently inserted into the device is floppy disk. ID_DRIVE_MEDIA_FLOPPY_ZIP The physical media currently inserted into the device is Zip. ID_DRIVE_MEDIA_FLOPPY_JAZ The physical media currently inserted into the device is Jaz. REMOTE CLIENTS
TODO: write me. AUTHOR
Written by David Zeuthen david@fubar.dk with a lot of help from many others. BUGS
Please send bug reports to either the distribution bug tracker or the upstream bug tracker at http://bugs.freedesktop.org/enter_bug.cgi?product=udisks. SEE ALSO
udev(7), polkit(8), udisks-daemon(8), udisks-tcp-bridge(1), udisks(1) udisks March 2008 UDISKS(7)
All times are GMT -4. The time now is 12:47 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy