[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: trying to understand assemble option in mdadm please help.



On 17/07/12 04:24 PM, Muhammad Yousuf Khan wrote:
On Wed, Jul 18, 2012 at 12:59 AM, Gary Dale<garydale@rogers.com>  wrote:
On 17/07/12 03:48 PM, Muhammad Yousuf Khan wrote:
or just one thing if you please explain these commands. i think my
confusion will be cleared
mdadm --assemble /dev/md1 /dev/hda1
mdadm --assemble /dev/md3 /dev/hda3

mdadm --add /dev/md1 /dev/hdb1
mdadm --add /dev/md3 /dev/hdb3

what is the difference in both command thanks. any help will be highly
appreciated.

The first set of commands should give you error messages unless the disk
devices are actually part of the array. Assemble normally doesn't need to
know the disk partitions that form the array, but you can list them. This
could be done if the superblocks were damaged, for example. You need to get
the order right in that case or the device may not be readable.

The normal command would be just mdadm --assemble /dev/md1. The alternative
would be to relist all the constituent devices.

The second set of commands should give you error messages if the disk
devices are already part of the array. Add puts a new drive into the array.
The drive will be assumed to be dirty and a re-syncing operation will
commence.


just one last question what do you mean by build. do you mean the sync
which shows in "cat /proc/mdstat" and show the sync status b/w the two
partition. does this called build?
I didn't use the term "build". I used re-sync.



--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject
of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: [🔎] 5005C43A.4090805@rogers.com">http://lists.debian.org/[🔎] 5005C43A.4090805@rogers.com




Reply to: