public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Volker Armin Hemmann <volkerarmin@googlemail.com>
To: Bill Davidsen <davidsen@tmr.com>,
	Michael Evans <mjevans1983@gmail.com>,
	linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org,
	Nick Bowler <nbowler@elliptictech.com>
Subject: Re: Linux mdadm superblock question.
Date: Tue, 16 Feb 2010 23:18:33 +0100	[thread overview]
Message-ID: <201002162318.33950.volkerarmin@googlemail.com> (raw)
In-Reply-To: <20100216220020.GA1036@emergent.ellipticsemi.com>

On Dienstag 16 Februar 2010, Nick Bowler wrote:
> On 22:06 Tue 16 Feb     , Volker Armin Hemmann wrote:
> > On Dienstag 16 Februar 2010, Bill Davidsen wrote:
> > > Volker Armin Hemmann wrote:
> > > > On Sonntag 14 Februar 2010, you wrote:
> > > >> In other words, 'auto-detection' for 1.x format devices is using an
> > > >> initrd/initramfs.
> > > > 
> > > > which makes 1.x format useless for everybody who does not want to
> > > > deal with initrd/initramfs.
> > > 
> > > You make this sound like some major big deal. are you running your own
> > > distribution? In most cases mkinitrd does the right thing when you
> > > "make install" the kernel, and if you are doing something in the build
> > > so complex that it needs options, you really should understand the
> > > options and be sure you're doing what you want.
> > > 
> > > Generally this involves preloading a module or two, and if you need it
> > > every time you probably should have built it in, anyway.
> > > 
> > > My opinion...
> > 
> > I am running my own kernels - and of course everything that is needed to
> > boot and get the basic system up is built in. Why should I make the disk
> > drivers modules?
> > That does not make sense.
> 
> I agree that it makes little sense to make something a module when you
> can't unload it anyway, but...
> 
> > And the reason is simple: even when the system is completely fucked up, I
> > want a kernel that is able to boot until init=/bin/bb takes over.
> 
> I put a complete set of recovery tools into my initramfses so that when
> the system is completely fucked up, I have a kernel that is able to boot
> until rdinit=/bin/zsh (or /bin/bb, if you prefer) takes over.
> 
> This has the added advantage of working when the root filesystem cannot
> be mounted at all: a scenario which does not seem too far-fetched when
> the filesystem is located on a raid array.

and what do you do if you have to boot from a cd/usb stick and need to access 
the raid?

Simple with auto assembling. Not so much without.

Glück Auf,
Volker

  reply	other threads:[~2010-02-16 22:18 UTC|newest]

Thread overview: 79+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-14  1:51 Linux mdadm superblock question Volker Armin Hemmann
2010-02-14  4:02 ` Michael Evans
2010-02-14  7:21   ` david
2010-02-14  8:38     ` Michael Evans
2010-02-14 18:40   ` Volker Armin Hemmann
2010-02-14 18:53     ` John Robinson
2010-02-14 21:16       ` Gabor Gombas
2010-02-16 17:18     ` Bill Davidsen
2010-02-16 21:06       ` Volker Armin Hemmann
2010-02-16 22:00         ` Nick Bowler
2010-02-16 22:18           ` Volker Armin Hemmann [this message]
2010-02-17 14:25             ` Nick Bowler
2010-02-18  9:27             ` Ian Dall
2010-02-17  1:03       ` Mr. James W. Laferriere
2010-02-17  2:01         ` Neil Brown
2010-02-17  2:38           ` Volker Armin Hemmann
2010-02-17 23:15             ` Neil Brown
2010-02-17  6:34           ` Kyle Moffett
2010-02-17  9:38             ` Rudy Zijlstra
2010-02-17 13:26               ` Frans Pop
2010-02-17 20:54                 ` Gabor Gombas
2010-02-17 21:29                   ` Frans Pop
2010-02-18  3:40                   ` Goswin von Brederlow
2010-02-17 16:22               ` Kyle Moffett
2010-02-17 17:41                 ` david
2010-02-17 18:10                   ` Nick Bowler
2010-02-17 18:27                     ` Volker Armin Hemmann
2010-02-17 18:37                       ` Nick Bowler
2010-02-17 18:41                         ` david
2010-02-17 18:51                           ` Nick Bowler
2010-02-17 21:17                             ` david
2010-02-17 21:37                               ` Nick Bowler
2010-02-17 22:21                                 ` david
2010-02-17 22:29                                 ` boot times, not mdadm (was: Linux mdadm superblock question.) martin f krafft
2010-02-17 23:24                           ` (boot time consequences of) Linux mdadm superblock question Neil Brown
2010-02-17 23:50                             ` martin f krafft
2010-02-18  2:58                             ` Henrique de Moraes Holschuh
2010-02-18  3:26                               ` martin f krafft
2010-02-17 18:46                         ` Volker Armin Hemmann
2010-02-17 22:26                           ` H. Peter Anvin
2010-02-18  3:33                     ` Goswin von Brederlow
2010-02-18 14:12                       ` Nick Bowler
2010-02-19  9:04                         ` Michael Evans
2010-02-14 19:34   ` Henrique de Moraes Holschuh
2010-02-14 20:07     ` Michael Evans
2010-02-14 21:14       ` Henrique de Moraes Holschuh
2010-02-14 20:47     ` Asdo
2010-02-14 21:26       ` Henrique de Moraes Holschuh
2010-02-14 21:28       ` Gabor Gombas
2010-02-15  9:08         ` martin f krafft
     [not found] ` <201002142013.24922.volkerarmin@googlemail.com>
     [not found]   ` <4B7AAB8D.9030009@anonymous.org.uk>
2010-02-16 14:37     ` Volker Armin Hemmann
2010-02-16 17:23       ` John Robinson
     [not found] <edBWa-K7-9@gated-at.bofh.it>
     [not found] ` <edDXX-3XC-7@gated-at.bofh.it>
     [not found]   ` <edRHA-7bL-13@gated-at.bofh.it>
     [not found]     ` <eezfA-4N7-11@gated-at.bofh.it>
2010-02-16 21:10       ` Bodo Eggert
  -- strict thread matches above, loose matches on Subject: below --
2010-02-11 23:00 Justin Piszcz
2010-02-12  1:52 ` Michael Evans
2010-02-13 19:58   ` H. Peter Anvin
2010-02-13 20:07     ` Justin Piszcz
2010-02-13 20:49       ` david
2010-02-13 21:07         ` Michael Evans
2010-02-13 21:29       ` H. Peter Anvin
2010-02-14 20:25         ` Asdo
2010-02-14 21:18           ` H. Peter Anvin
2010-02-14 21:34             ` Henrique de Moraes Holschuh
2010-02-14 23:20             ` Rudy Zijlstra
2010-02-15  3:40               ` Mr. James W. Laferriere
2010-02-16  0:27     ` Neil Brown
2010-02-16  1:24       ` H. Peter Anvin
2010-02-16  3:18         ` david
2010-02-16  4:42           ` John Robinson
2010-02-16  7:02           ` H. Peter Anvin
2010-02-16  8:46             ` Rudy Zijlstra
2010-02-16 17:05         ` Bill Davidsen
2010-02-16 23:30           ` H. Peter Anvin
2010-02-16  3:40   ` CaT
2010-02-13  6:42 ` martin f krafft
2010-02-16  0:50 ` Neil Brown
2010-02-16 13:14   ` Justin Piszcz
2010-02-17 23:11     ` Neil Brown
2010-02-16 17:24   ` Bill Davidsen

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=201002162318.33950.volkerarmin@googlemail.com \
    --to=volkerarmin@googlemail.com \
    --cc=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=mjevans1983@gmail.com \
    --cc=nbowler@elliptictech.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox