Sponsored Content
Special Forums UNIX and Linux Applications Virtualization and Cloud Computing is mdadm --incremental --rebuild --run --scan destructive? Post 302538379 by Habitual on Tuesday 12th of July 2011 08:57:58 PM
Old 07-12-2011
is mdadm --incremental --rebuild --run --scan destructive?

Hello Unix Community:

My task to figure out how to add a 20G volume to an existing EBS Array (RAID0) at AWS.

I haven't been told that growing the existing volumes isn't an option, or adding another larger volume to the existing array is the way to go. The client's existing data-store is growing fast and he needs more space.
The boss said "Add".... but I am free to conceptualize some solutions he may not have thought of.

I have RTFM'd today for about 3 hours and came to these 2 possibilities. Add or grow...

After a cursory review (and some in depth reading) I am uncertain, so I have to ask
is "mdadm --incremental --rebuild --run --scan" destructive to data or will it simply incorporate the new volume into the designated mdX?

Code:
-I, --incremental
Add a single device into an appropriate array, and possibly start the array.

"Possibly start the array" implies that it is not started, but what if the array is already started?

I further wonder if I can just create a new volume and edit the /etc/mdadm/mdadm.conf
and --scan and/or --rebuild and if that would be destructive?

Thank you for your time.

Edit: Solved. See https://www.unix.com/virtualization-c...array-aws.html

Last edited by Habitual; 07-18-2011 at 08:36 PM..
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Self destructive script

How should i write a script so that the script will destroy(delete) itself once it completes execution. Thanks? (7 Replies)
Discussion started by: proactiveaditya
7 Replies

2. Linux

mdadm - Swapping 500GB disks for 1TB

Hi, I have a three disk raid 5, with 500GB disks. This is close to being full, and whilst I can just add another disk and rebuild to add another 500GB, I would prefer to replace with 1TB disks. So i have some questions. Can I replace these disks one by one with bigger disks? I... (1 Reply)
Discussion started by: snoop2048
1 Replies

3. Emergency UNIX and Linux Support

mdadm unable to fail a resyncing drive?

Hi All I have a RAID 5 array consisting of 4 drives that had a partial drive failure in one of the drives. Rebooting shows the faulty drive as background rebuilding and mdadm /dev/ARRAYID shows three drives as in sync with the fourth drive as spare rebuilding. However the array won't come... (9 Replies)
Discussion started by: Bashingaway
9 Replies

4. UNIX for Advanced & Expert Users

mdadm question

Hello, I have 4 drives (500G each) in a raid 10, I got a power failior and this is the result? cat /proc/mdstat Personalities : md126 : inactive sdb sdc sdd sde 1953536528 blocks super external:-md127/0 md127 : inactive sdd(S) sde(S) sdb(S) sdc(S) 9028 blocks super... (3 Replies)
Discussion started by: rmokros
3 Replies

5. UNIX for Advanced & Expert Users

mdadm container! How does it work

Hi everyone, I am not sure if I understand how mdadm --create /dev/md0 --level=container works? A device called /dev/md0 appears in /proc/mdstat but I am not sure how to use that device? I have 2 blank drives with 1 500GB partition on each. I would like to setup mirroring, but not in the... (0 Replies)
Discussion started by: hytron
0 Replies

6. Cybersecurity

Destructive one word unix commands

Hi I'm trying to hack a web server as part of an assignment and have gotten it to exec commands but I cannot pass commands arguments as the program splits up space separated words and only execs the first one. Is there anything I can pass to cause any sort of damage in one word? Btw webserver runs... (1 Reply)
Discussion started by: aydinh
1 Replies

7. Red Hat

mdadm for / and /boot

had this RHEL 5 installation with /dev/sda1 and /dev/sda2 running.. created two more partitions /dev/sdj1 and /dev/sdj2 , the same sized partition as /dev/sda trying to use mdadm to create RAID1 .. I cannot even do it in "rescue" mode, I wonder if it can be done.. it kept... (2 Replies)
Discussion started by: ppchu99
2 Replies

8. HP-UX

Format unit requires destructive mode???

I am trying to format a Seagate 2 Gb SCSI drive using the HP-UX 9.0 support disc and I receive a message that says: DESTRUCTIVE MODE REQUIRED TO EXECUTIVE THIS COMMAND (SCD2WARN 106). I have entered this command several times on other SCSI drives and never got this message. Anyone ever see this... (8 Replies)
Discussion started by: edspit
8 Replies

9. Filesystems, Disks and Memory

MDADM Failure - where it came from?

Hello, i have a system with 6 sata3 seagate st3000dm01 disks running on stable Debian with software raid mdadm. i have md0 for root and md1 for swap and md2 for the files. i now want to add one more disk = sdh4 for md2 but i got this errors: The new disk is connected to an 4 port sata... (7 Replies)
Discussion started by: Sunghost
7 Replies

10. UNIX for Advanced & Expert Users

How to fix mistake on raid: mdadm create instead of assemble?

Hi guys, I'm new to RAID although I've had a server running raid5 for a while. It was delivered preinstalled like this and I never really wondered how to monitor and maintain it. This quick introduction just to let you understand why I'm such an idiot asking such a silly question. Now what... (0 Replies)
Discussion started by: chebarbudo
0 Replies
Gluster(8)							   Gluster Inc. 							Gluster(8)

NAME
gluster - Gluster Console Manager (command line utility) SYNOPSIS
gluster To run the program and display gluster prompt: gluster (or) To specify a command directly: gluster [commands] [options] DESCRIPTION
The Gluster Console Manager is a command line utility for elastic volume management. You can run the gluster command on any export server. The command enables administrators to perform cloud operations, such as creating, expanding, shrinking, rebalancing, and migrating volumes without needing to schedule server downtime. COMMANDS
Volume Commands volume info [all|<VOLNAME>] Display information about all volumes, or the specified volume. volume create <NEW-VOLNAME> [device vg] [stripe <COUNT>] [replica <COUNT>] [transport <tcp|rdma|tcp,rdma>] <NEW-BRICK> ... Create a new volume of the specified type using the specified bricks and transport type (the default transport type is tcp). To create a volume with both transports (tcp and rdma), give 'transport tcp,rdma' as an option. device vg parameter specifies volume should use block backend instead of regular posix backend. In this case NEW-BRICK should specify an existing Volume Group and there can be only one brick for Block backend volumes. Refer Block backend section for more details volume delete <VOLNAME> Delete the specified volume. volume start <VOLNAME> Start the specified volume. volume stop <VOLNAME> [force] Stop the specified volume. volume rename <VOLNAME> <NEW-VOLNAME> Rename the specified volume. volume set <VOLNAME> <OPTION> <PARAMETER> [<OPTION> <PARAMETER>] ... Set the volume options. volume help Display help for the volume command. Block backend By specifying "device vg" in volume create, a volume capable of exporting block devices(ie Volume Groups (VG)) is created. As of now exporting only VG is supported. While creating block backend volume the "VG" (mentioned in NEW-BRICK) must exist (ie created with vgcre- ate). VG is exported as a directory and all LVs under that VG will be exported as files. Please refer BD commands section for Block backend related commands Brick Commands volume add-brick <VOLNAME> <NEW-BRICK> ... Add the specified brick to the specified volume. volume remove-brick <VOLNAME> <BRICK> ... Remove the specified brick from the specified volume. Note: If you remove the brick, the data stored in that brick will not be available. You can migrate data from one brick to another using replace-brick option. volume rebalance-brick <VOLNAME>(<BRICK> <NEW-BRICK>) start Start rebalancing the specified volume. volume rebalance <VOLNAME> stop Stop rebalancing the specified volume. volume rebalance <VOLNAME> status Display the rebalance status of the specified volume. volume replace-brick <VOLNAME> (<BRICK> <NEW-BRICK>) start|pause|abort|status|commit Replace the specified brick. Log Commands volume log filename <VOLNAME> [BRICK] <DIRECTORY> Set the log directory for the corresponding volume/brick. volume log locate <VOLNAME> [BRICK] Locate the log file for corresponding volume/brick. volume log rotate <VOLNAME> [BRICK] Rotate the log file for corresponding volume/brick. Peer Commands peer probe <HOSTNAME> Probe the specified peer. peer detach <HOSTNAME> Detach the specified peer. peer status Display the status of peers. peer help Display help for the peer command. BD commands bd create <VOLNAME:/path-to-image> <size> Creates a new image of given size in the volume. Size can be suffixed with MB, GB etc, if nothing specified MB is taken as default. bd delete <VOLNAME:/path-to-image> Deletes a image in the volume bd clone <VOLNAME:/path-to-image> <new-image> Clones an existing image (full clone) bd snapshot <VOLNAME:/path-to-image> <new-image> <size> Creates a linked clone of an existing image with given size. Size can be suffixed with MB, GB etc, if nothing specified MB is taken as default. Other Commands help Display the command options. quit Exit the gluster command line interface. FILES
/var/lib/glusterd/* SEE ALSO
fusermount(1), mount.glusterfs(8), glusterfs(8), glusterd(8) COPYRIGHT
Copyright(c) 2006-2011 Gluster, Inc. <http://www.gluster.com> 22 November 2012 Gluster command line utility Gluster(8)
All times are GMT -4. The time now is 02:53 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy