All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kurt Newman <kurt@lamer.org>
To: linux-raid@vger.kernel.org
Subject: Re: Simple Raid-1 setup question
Date: Fri, 13 Nov 2009 17:26:06 -0600	[thread overview]
Message-ID: <4AFDEB0E.7000004@lamer.org> (raw)
In-Reply-To: <70ed7c3e0911131302o21bd47cbua1f2858c98edb201@mail.gmail.com>

That clears up a lot of my questions.  Although, --assume-clean isn't
doing what I'd like, I did some searches using the keyword,
'--assume-clean'.  That lead me back to the linux raid wiki.

Apparently I lack the ability to read 'Initial Array Creation' the last
time I was there.

Thank you for the help.

Majed B. wrote:
> 1) No need to sync if both disks are new (or have no data).
> That can be accomplished using: --assume-clean
> 
> 2) It shouldn't be a problem. If you still can't force mdadm, use dd
> (be very sure you're writing to the correct disks!!)
> dd if=/dev/zero of=/dev/sdx bs=10M count=1
> 
> That will write 10MB of zeros to the disk. It should corrupt any
> filesystem laying there.
> 
> Remember to change the partition type to "FD" for RAID auto-detect.
> 
> Create your filesystem on the array after you create it & that's it.
> 
> On Fri, Nov 13, 2009 at 11:34 PM, Kurt Newman <kurt@lamer.org> wrote:
>> My questions are as follows:
>>
>> 1) If you're creating a completely new array (e.g. raid-1) on new
>> partitions that aren't formatted, do you still have to sync?  I'm having
>> difficulty finding information on why and when a sync is needed.  I was
>> under the impression a sync is only needed when there's existing
>> information on one or more of the drives.
>>
>> 2) If there used to be information on each device, but has since been
>> repartitioned, so that new partitions and a raid device can be
>> created... is there any way to prevent mdadm from asking if you really
>> want to create the array?  Using `--force' doesn't seem to help.
>>
>> mdadm: /dev/sda1 appears to contain an ext2fs file system
>>   size=1464840K mtime=Fri Nov 13:04:09 2009
>> mdadm: /dev/sdb1 appears to contain an ext2fs file system
>>   size=1464840K mtime=Fri Nov 13:04:09 2009
>> Continue creating array?
>>
>> As a side note, there really isn't an existing ext3 fs on it, but there
>> used to be.  To re-use the device, I issued the following commands:
>>  > parted -s /dev/sda mklabel msdos
>>  > parted -s /dev/sda mkpart primary ext3 0 1500
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
> 
> 
> 


  reply	other threads:[~2009-11-13 23:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-13 20:34 Simple Raid-1 setup question Kurt Newman
2009-11-13 21:02 ` Majed B.
2009-11-13 23:26   ` Kurt Newman [this message]
2009-11-13 22:24 ` Neil Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4AFDEB0E.7000004@lamer.org \
    --to=kurt@lamer.org \
    --cc=linux-raid@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.