All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Timothy D. Lenz" <tlenz@vorgon.com>
To: linux-raid@vger.kernel.org
Subject: Re: Converting system to raid
Date: Sat, 11 Apr 2009 11:47:39 -0700	[thread overview]
Message-ID: <007001c9bad6$2525c610$0a00a8c0@vorg> (raw)
In-Reply-To: f19d625d0904110729y30e8bc80m41fcd8f2c3298d49@mail.gmail.com

Yes, the default setup. But that is because the supplied kernel builds raid as modules. I build a new kernel with stuff needed for
my system ecept for dvb stuf which I get by building v4l tree to get newest drivers. And I build raid into the kernel. Since I
havn't needed ramdisk for anything up till now and you are not suposed to need it when raid is built it, ramdisk is not compiled in
or as a module.

----- Original Message ----- 
From: "CoolCold" <coolthecold@gmail.com>
To: "Timothy D. Lenz" <tlenz@vorgon.com>
Cc: <linux-raid@vger.kernel.org>
Sent: Saturday, April 11, 2009 7:29 AM
Subject: Re: Converting system to raid


On Sat, Apr 11, 2009 at 9:29 AM, Timothy D. Lenz <tlenz@vorgon.com> wrote:
> From: "CoolCold" <coolthecold@gmail.com>
>
>> Yes, he should provide correct /etc/mdadm/mdadm.conf and
>> update-initramfs -u on md boot, smth like
>> chroot /mnt/md0
>> update-initramfs -u
>
> How would this help in a system that doesn't ramdisk built in to the kernel or as a module? Or does it change some other stuff?
Looking into "I have 2 computers that I am trying to convert to raid.
Both where setup with debian netinst cd to hda" - debian has initrd
support within their kernels.
>
>
> I started looking at the stuff that was copied to md0 and /md0/dev is empty. Looking through the guides I found a few things. One
> said that using cp had to be from root or not everything would get coppied. I used sudo but I know some things require you to
root.
> Also this:
> ===============================
> # rsync -avHhx --progress / /mnt/raid-md0
>
> * If the system wasn't previously in single user mode, move to single user mode and update the data that changed during the
> first copy:
> (--delete flag tells rsync to delete files from the destination which do not exist on the source):
>
> # rsync -avHhx --progress --delete / /mnt/raid-md0
>
> * Create needed device nodes:
>
> # cd /mnt/raid-md0/dev/ && MAKEDEV generic
> ===============================
> Using rsync from single user mode still left /mnt/md0/dev empty. I read up in "makedev generic" and it seems to be a shotgun fix
> adding way more then is needed. Is there a way to create just what is in /dev?
>
> --
> 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
>



-- 
-- 
Best regards,
[COOLCOLD-RIPN]


  reply	other threads:[~2009-04-11 18:47 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-09 23:44 Converting system to raid Timothy D. Lenz
2009-04-10  9:10 ` KwangErn Liew
2009-04-10  9:55   ` CoolCold
2009-04-10 19:43     ` Timothy D. Lenz
2009-04-10 19:53   ` Robin Hill
2009-04-10 20:45     ` Timothy D. Lenz
2009-04-10 20:59       ` Robin Hill
2009-04-10 21:26         ` Timothy D. Lenz
2009-04-10 21:51           ` Robin Hill
2009-04-11  5:29             ` Timothy D. Lenz
2009-04-11 14:29               ` CoolCold
2009-04-11 18:47                 ` Timothy D. Lenz [this message]
2009-04-12  0:53                   ` Timothy D. Lenz
2009-04-12 11:11                     ` Robin Hill
2009-04-12 19:55                       ` Timothy D. Lenz
2009-04-14  9:30                         ` Robin Hill
2009-04-17  0:47                           ` Timothy D. Lenz
2009-04-17  7:49                             ` Robin Hill
2009-04-11 14:36               ` Robin Hill
2009-04-11 15:04                 ` jim owens
2009-04-11 15:44                   ` Jeff Garzik
2009-04-11 17:40                     ` jim owens
2009-04-12 11:11                       ` Jeff Garzik
2009-04-12 16:43                         ` jim owens
2009-04-12 17:18                           ` Jeff Garzik
2009-04-10 13:22 ` Robin Hill
2009-04-10 19:22   ` Timothy D. Lenz
2009-04-10 19:50     ` Robin Hill
2009-04-11  4:40       ` Jon Lewis
2009-04-11  7:48         ` Jan Ceuleers
2009-04-11  8:50         ` Goswin von Brederlow

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='007001c9bad6$2525c610$0a00a8c0@vorg' \
    --to=tlenz@vorgon.com \
    --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.