Sponsored Content
Operating Systems Solaris Cannot remove disk added to zpool Post 302933688 by jlliagre on Sunday 1st of February 2015 04:36:01 PM
Old 02-01-2015
You should tell the disks capacity and what is the intended usage of the pool.

Bartus suggestion will provide the best performance while a raidz will give you 50% more storage. Both will sustain a full disk failure.
 

10 More Discussions You Might Find Interesting

1. Solaris

Remove the exported zpool

I had a pool which was exported and due to some issues on my SAN i was never able to import it again. Can anyone tell me how can i destroy the exported pool to free up the LUN. I tried to create a new pool on the same pool but it gives me following error # zpool create emcpool4 emcpower0c... (0 Replies)
Discussion started by: fugitive
0 Replies

2. Solaris

Can't remove a LUN from a Zpool!

I am not seeing anyway to remove a LUN from a Zpool... Am I missing something? or do i have to destroy the zpool and recreate it? (2 Replies)
Discussion started by: BG_JrAdmin
2 Replies

3. Red Hat

Partitioning newly added disk to Redhat

Hi Everyone, I have added new Virtual disk to OS. The main point is I need to bring this whole Disk into LVM control, is it necessary to partition the disk using fdisk command and assign partition type as '8e', or can I directly add that disk into LVM, by running pvcreate command with out... (2 Replies)
Discussion started by: bobby320
2 Replies

4. AIX

Remove the disk online

Hi I have one of the disk missing in my NIMVG. My doubt is can I remove this hdisk2 online ? few of the file systems seems to be spread over 7 PV's. that's why i'm worried. Can someone suggest if I can replace this disk online. Also how to check if there is some data present in hdisk2 alone... (2 Replies)
Discussion started by: newtoaixos
2 Replies

5. Solaris

Bad exchange descriptor : not able to remove files under zpool

Hi , One of my zone went down and when i booted it up i could see the pool in degraded state with some check sum errors . we have brought the pool online after scrubbing. But few files are showing this error Bad exchange descriptor Please let me know how to remove these files (2 Replies)
Discussion started by: chidori
2 Replies

6. Solaris

Add disk to zpool

Hi, Quick question. I have a data zpool that consists of 1 disk. pool: data state: ONLINE scrub: none requested config: NAME STATE READ WRITE CKSUM data ONLINE 0 0 0 c0t50002AC0014B06BEd0 ONLINE... (2 Replies)
Discussion started by: general_lee
2 Replies

7. AIX

LPAR cannot added disk

Dear All, I created a new partition through "Integrated Virtualization Manager" but there have an error when I added a new disk to the partition. The disk already created without any issue, Below error is to add the disk to the partition An error occured while modifying the assignments... (5 Replies)
Discussion started by: lckdanny
5 Replies

8. Solaris

Exporting zpool sitting on different disk partition

Hello, I need some help in recovering ZFS pool. Here is scenerio. There are two disks - c0t0d0 - This is good disk. I cloned it from other server and boot server from this disk. c0t1d0 - This is original disk of this server, having errors. I am able to mount it on /mnt. So that I can copy... (1 Reply)
Discussion started by: solaris_1977
1 Replies

9. Solaris

Replace zpool with another disk

issue, I had a zpool which was full pool_temp1 199G 197G 1.56G 99% ONLINE - pool_temp2 199G 196G 3.09G 98% ONLINE - as you can see, full so I replaced with a larger disk. zpool replace pool_temp1 c3t600144F0FF8BA036000058CC1DB80008d0s0... (2 Replies)
Discussion started by: rrodgers
2 Replies

10. Solaris

How to clear a removed single-disk pool from being listed by zpool import?

On an OmniOS server, I removed a single-disk pool I was using for testing. Now, when I run zpool import it will show it as FAULTED, since that single disk not available anymore. # zpool import pool: fido id: 7452075738474086658 state: FAULTED status: The pool was last... (11 Replies)
Discussion started by: priyadarshan
11 Replies
voldiskadd(8)						      System Manager's Manual						     voldiskadd(8)

NAME
voldiskadd - Adds one or more disks for use with the Logical Storage Manager SYNOPSIS
/usr/sbin/voldiskadd disk-address-list DESCRIPTION
The voldiskadd utility sets up new disks that are added to the system after the initial system installation and configures the disks for use by the Logical Storage Manager. A valid disk label must exist on the disk before using the voldiskadd utility. One or more disks may be specified using a disk-address-list. Disk addresses in the list have the form dskn (for the entire disk) or dsknp (for a specific partition). When specifying multiple disks, use a space between entries. Disk address names relate directly to device names in the /dev/disk directory. For example, here are some valid voldiskadd disk-address-list specifications: # voldiskadd dsk1 # voldiskadd dsk2 dsk3a The file, /etc/vol/disks.exclude, may be used to exclude disks from use by voldiskadd. Each line of the file specifies the name of a disk to exclude (for example, dsk5). The voldiskadd utility prompts the user for a disk group name and disk media name for the disks. If a new disk group name is specified, that disk group is created for the new disks. If no disk group name is specified, the disks are left as unassigned replacement disks for future use. If an existing disk group name is specified, the user is prompted for whether the disks should be designated as spares for the disk group. If a disk is found to already contain non-Logical Storage Manager partitioning, the user is asked whether the disk should be encapsulated. Encapsulation turns each partition of the disk into a volume. A disk should be encapsulated if it contains file systems or data that should not be overwritten. If encapsulation is not desired for a disk, the disk can be initialized as a new disk for use by the Logical Storage Manager. For new disks, all space on the disk becomes free space in the disk's disk group. Context-sensitive help is available at every prompt by typing ?. Also, a list option can be used to get information on available target disks for an operation. The voldiskadd utility supports the following general classes of actions: Initializing a disk with reserved regions and partitions. Disk initialization is performed by calling voldisksetup command. Adding a disk to an existing disk group. This operation can be performed independently of the initialization of the disk drive to add a disk's storage space to a disk group's free space pool. The volassist command may subsequently allocate from that free space. The disk can also be added as a hot spare device. Creating new disk groups in which to import new disks. If no disk group exists for importing disks, the option of creating the disk group is offered. Encapsulating disks that have exist- ing contents. This is the default action for disks that do not have a valid, existing Logical Storage Manager private region, but that do have a disk label. Encapsulation is performed by calling volencap. Reconnecting a drive that was temporarily inaccessible. This situation is detected automatically, by noting that the specified drive has a disk ID that matches a disk media record with no currently associated physical disk. After reconnection, any stale plexes referring the disk are reattached, and any stopped volumes referring the disk are restarted. This reattach action is performed by calling the volrecover script. ERRORS
You may receive the following messages when using the voldiskadd command: Initialization of disk device special-device failed. Error: special-device or an overlapping partition is open. This message indicates that the partition you specified or an overlapping partition on the disk is actively in use. The partition could be a mounted UFS or AdvFS filesystem, initialized as an LSM disk or used as a swap device. special-device is marked in use for fstype in the disklabel. If you continue with the operation you can possibly destroy existing data. Would you like to continue?? [y,n,q,?] (default: n) This message indicates that the fstype of a partition or an overlapping partition is set in the disk label. The voldiskadd command prints this message to warn that a disk partition may have valid data which could be destroyed. If you are sure that the disk partition does not have valid data and that the partition can be added to LSM, you can ignore the warning message by entering y at the prompt. The voldiskadd command will proceed to initialize the disk partition and add it to LSM. FILES
A list of disks to exclude from use by voldiskadd. SEE ALSO
disklabel(8), volassist(8), voldisk(8), voldiskadm(8), voldisksetup(8), voldg(8), volintro(8) voldiskadd(8)
All times are GMT -4. The time now is 06:00 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy