You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Sander Temme (JIRA)" <ji...@apache.org> on 2005/11/02 17:58:56 UTC
[jira] Created: (INFRA-604) Find out how to mirror/stripe drives in Xserves
Find out how to mirror/stripe drives in Xserves
-----------------------------------------------
Key: INFRA-604
URL: http://issues.apache.org/jira/browse/INFRA-604
Project: Infrastructure
Type: Sub-task
Reporter: Sander Temme
Assigned to: Sander Temme
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (INFRA-604) Find out how to mirror/stripe drives in Xserves
Posted by "Sander Temme (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/INFRA-604?page=comments#action_12357961 ]
Sander Temme commented on INFRA-604:
------------------------------------
Full blow-by-blow for Sander Striker's benefit when he gets to do the other one:
The SF system came with all four of its drive bays filled, two with 60Gb drives and two with 180Gb. Since the 60Gb mirror already had the OS installed, I had to go through the initial boot and setup before I could change the Startup Disk to the CD. I had to boot from CD to re-create the mirror with auto-rebuild set.
You can run Disk Utility from the installer after booting from CD (Utilities menu). To create a RAID, select one of the disks and click the RAID tab (yes this is bogus UI). Select striped or mirrored, and drag constituent disks from the left pane to the array list. Click 'create'. Whatever was on those disks is now gone.
I made a 60Gb mirror for the OS (named MirrorBoot), and a 2x180Gb stripe for spool (x1, in good ASF tradition).
> Find out how to mirror/stripe drives in Xserves
> -----------------------------------------------
>
> Key: INFRA-604
> URL: http://issues.apache.org/jira/browse/INFRA-604
> Project: Infrastructure
> Type: Sub-task
> Reporter: Sander Temme
> Assignee: Sander Temme
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Closed: (INFRA-604) Find out how to mirror/stripe drives in Xserves
Posted by "Sander Temme (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/INFRA-604?page=all ]
Sander Temme closed INFRA-604:
------------------------------
Resolution: Fixed
Thank you Chris.
Turns out the 60Gb drives were already mirrored and had the OS installation on them. However, the 'rebuild array automatically' checkbox was not checked, so I re-created the array. It is now empty.
I striped the other two (180Gb) drives for use as spool.
> Find out how to mirror/stripe drives in Xserves
> -----------------------------------------------
>
> Key: INFRA-604
> URL: http://issues.apache.org/jira/browse/INFRA-604
> Project: Infrastructure
> Type: Sub-task
> Reporter: Sander Temme
> Assignee: Sander Temme
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (INFRA-604) Find out how to mirror/stripe drives in Xserves
Posted by "Chris Pepper (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/INFRA-604?page=comments#action_12356882 ]
Chris Pepper commented on INFRA-604:
------------------------------------
Note that mirroring should be done before putting data on the drive. It's theoretically possible to convert a standalone disk to a degraded mirror, and then add another, but this isn't really supported (and didn't work for me).
>From the GUI, use /Applications/Utilities/Disk Utility.app.
>From the CLI, use diskutil.
pepper@www:~$ diskutil
Disk Utility Tool
Utility to manage local disks and volumes.
Most options require root access to the device
Usage: diskutil <verb> <options>
<verb> is one of the following:
list (List the partitions of a disk)
information | info (Get information on a disk or volume)
unmount (Unmount a single volume)
unmountDisk (Unmount an entire disk (all volumes))
eject (Eject a disk)
mount (Mount a single volume)
mountDisk (Mount an entire disk (all mountable volumes))
rename (Rename a volume)
enableJournal (Enable HFS+ journaling on a mounted HFS+ volume)
disableJournal (Disable HFS+ journaling on a mounted HFS+ volume)
verifyVolume (Verify the structure of a volume)
repairVolume (Repair the structure of a volume)
verifyPermissions (Verify the permissions of a volume)
repairPermissions (Repair the permissions of a volume)
repairOS9Permissions (Repair the permissions for the current
Classic boot volume)
eraseDisk (Erase an existing disk, removing all volumes)
eraseVolume (Erase an existing volume)
reformat (Reformat an existing volume)
eraseOptical (Erase an optical media (CD/RW, DVD/RW, etc.))
zeroDisk (Erase a disk, writing zeros to the media)
randomDisk (Erase a disk, writing random data to the media)
secureErase (Securely erase a disk or freespace on a volume)
partitionDisk ((re)Partition a disk, removing all volumes)
createRAID (Create a RAID set on multiple disks)
destroyRAID (Destroy an existing RAID set)
checkRAID (Check a RAID set for errors)
enableRAID (Convert a disk to a degraded RAID mirror set)
convertRAID (Convert a RAID 1.x (pre-Tiger) to a RAID 2.x (Tiger))
updateRAID (Update the settings of an existing RAID)
addToRAID (Add a spare or member disk to an existing RAID)
removeFromRAID (Remove a spare or member disk from an existing RAID)
repairMirror (Repair a damaged RAID mirror set)
diskutil <verb> with no options will provide help on that verb
pepper@www:~$ man diskutil|cat
diskutil(8) BSD System Manager's Manual diskutil(8)
NAME
diskutil -- Modify, verify and repair local disks.
SYNOPSIS
diskutil verb [options]
DESCRIPTION
diskutil uses the Disk Management framework to manipulate local disks.
VERBS
Each verb is listed with its description and individual arguments.
list [device]
List the partitions of a disk or all disks. If no device is
listed, than all partitions on all disks will be displayed.
info | information device
Get information on a disk or volume.
unmount [force] device
Unmount a single volume. Force will force unmount the vol-
ume.
unmountDisk [force] device
Unmount an entire disk (all volumes). Force will force
unmount the volumes.
eject device
Eject a disk.
mount device
Mount a single volume.
mountDisk device
Mount an entire disk (all mountable volumes).
rename device name
Rename a volume.
enableJournal device
Enable HFS+ journaling on a mounted HFS+ volume. Ownership of
the affected disk is required.
disableJournal device
Disable HFS+ journaling on a mounted HFS+ volume. Ownership
of the affected disk is required.
verifyVolume device
Verify the disk structure of a volume. Ownership of the
affected disk is required.
repairvolume device
Repair the structure of a volume. Ownership of the affected
disk is required.
verifyPermissions device
Verify the permissions of a Mac OS X boot volume.
repairPermissions device
Repair the permissions of a Mac OS X boot volume. Ownership
of the affected disk is required.
repairOS9Permissions
Repair the permissions of the user selected Classic System and
Applications folder.
eraseDisk format name [OS9Drivers] device
Erase an existing disk, removing all volumes. Format dis-
cussed below. Ownership of the affected disk is required.
eraseVolume format name device
Erase an existing volume. Format discussed below. Ownership
of the affected disk is required.
reformat device
Reformat an existing device in the same name and format. Own-
ership of the affected disk is required.
eraseOptical [quick] device
Erase an optical media (CD/RW, DVD/RW, etc.). Quick specifies
whether the disc recording stack should do a full erase or a
quick erase. Ownership of the affected disk is required.
zeroDisk device
Erase a disk, writing zeros to the media. Ownership of the
affected disk is required.
randomDisk [times] device
Erase a disk, writing random data to the media. Times is num-
ber of times to write random information. Ownership of the
affected disk is required.
secureErase [freespace] level device
Securely erase a disk or freespace on a mounted volume. Level
should be one of the following
1 - Single pass randomly erase the disk.
2 - US DoD 7 pass secure erase.
3 - Gutmann algorithm 35 pass secure erase. Ownership
of the affected disk is required.
partitionDisk device numberOfPartitions [OS9Drivers] [MBRFormat]
<part1Format part1Name part1Size> <part2Format part2Name
part2Size> <part3Format part3Name part3Size> ...
(re)Partition a disk, removing all volumes. All volumes on
this disk will be destroyed. Format is the specific filesys-
tem name you want to erase it as. (HFS+, etc.) MBRFormat
specifies that the partition map should be written in DOS com-
patible format. (OS9Drivers will be ignored in this case)
Valid sizes are B(ytes), K(ilobytes), M(egabytes), G(iga-
bytes), T(erabytes) Example: 10G (10 gigabytes), 4.23T (4.23
terabytes), 5M (5 megabytes) You cannot partition the boot
disk. Ownership of the affected disk is required.
createRAID mirror|stripe setName format device device ...
Create a RAID set on multiple disks or volumes. Ownership of
the affected disks is required.
destroyRAID device
Destroy an existing RAID set. Ownership of the affected disks
is required.
checkRAID
Print out the list of available RAID sets.
enableRAID mirror|concat device
Convert single filesystem disk or volume into a unpaired mir-
ror RAID set or concat set. Ownership of the affected disk is
required.
convertRAID device
Convert a 1.x RAID (built on Panther or earlier) into a 2.x
RAID (Tiger). Ownership of the affected disks is required.
repairMirror raidDisk newDisk
Repair a failed mirror. Supply the existing RAID as the raid-
Disk parameter. Supply the new disk as the last parameter of
the request. newDisk and raidDisk are only Device Nodes or
Disk Identifiers. Ownership of the affected disk is required.
updateRAID key value raidDisk
Update the key|value parameters of an existing RAID set. Own-
ership of the affected disk is required.
addToRAID type newDisk raidDisk
removeFromRAID newDisk raidDisk
Add or remove a slice or spare from an existing RAID set.
Type is one of 'member' or 'spare'. newDisk and raidDisk are
only Device Nodes or Disk Identifiers. Ownership of the
affected disk is required.
FORMAT
The format parameter of erase and partitioning (and RAID creation) is the
filesystems name. You can determine this name by looking in the /Sys-
tem/Library/Filesystems/<fs>.fs/Contents/Info.plist.
Some examples include HFS+, HFS, JournaledHFS+, UFS, MS-DOS, etc.
EXAMPLES
Erase a disk
diskutil eraseDisk UFS UntitledUFS disk3
Erase a volume
diskutil eraseVolume HFS+ UntitledHFS /Volumes/SomeDisk
Partition a disk
diskutil partitionDisk disk3 3 HFS+ Untitled 10G UFS UntitledUFS 10G MS-
DOS DOS 10G
Create a RAID
diskutil createRAID mirror MirrorDisk HFS+ disk disk2
Destroy a RAID
diskutil destroyRAID /dev/disk3
Repair a damaged RAID
diskutil repairMirror disk2 disk3
DEVICES
A device parameter to any of the above commands (except where explicitly
defined otherwise) is any of the following
The device node entry. Any entry of the form of /dev/disk*. ex.
/dev/disk2
The disk identifier. Any entry of the form of disk*. ex. disk1s9
The volume mount point. Any entry of the form of /Volumes/Mountpoint.
ex. /Volumes/Untitled
SEE ALSO
authopen(1), hdid(8), hdiutil(1), ufs.util(8), msdos.util(8),
hfs.util(8), drutil(1), diskarbitrationd(8.)
Mac OS 24 Jan 2003 Mac OS
pepper@www:~$
> Find out how to mirror/stripe drives in Xserves
> -----------------------------------------------
>
> Key: INFRA-604
> URL: http://issues.apache.org/jira/browse/INFRA-604
> Project: Infrastructure
> Type: Sub-task
> Reporter: Sander Temme
> Assignee: Sander Temme
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira