On Wed, Jul 18, 2012 at 12:59 AM, Gary Dale <garyd...@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? > > > -- > To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject > of "unsubscribe". Trouble? Contact listmas...@lists.debian.org > Archive: http://lists.debian.org/5005c43a.4090...@rogers.com > -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cagwvfmk+5t7d7o0k25somngbk5a6pgdhi6rokgguud1jamm...@mail.gmail.com
