lkml.org 
[lkml]   [2002]   [Apr]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: RAID superblock confusion

> > >
> > > Ehh, I ran into this a while ago. When you compile raid as modules
> > > it doesn't use the raid superblocks for anything except for
> > > verification. I took a quick glance at the source and the
> > > auto-detect code is ifdefed out if you compiled as a module.
> >
> > Exactly where is this? A scan with find and grep don't reveal this.
> >
>
> drivers/md/md.c
>
> in the ifndef MODULE sectioin.
>
> > > Ever since I have had raid compiled into my kernels.
> >
> > This is my relevant .config:
> > CONFIG_MD=y
> > CONFIG_BLK_DEV_MD=y
> > CONFIG_MD_LINEAR=m
> > CONFIG_MD_RAID0=m
> > CONFIG_MD_RAID1=m
> > CONFIG_MD_RAID5=m
> > CONFIG_MD_MULTIPATH=m
> >
>
> Set this to =y and you're set.
>
> I'd like to see this working from modules though.

NO, please. There are hundreds of scenarios where that could be dangerous.
Suppose you load the RAID
module when all partitions are mounted, and two partiton in mirror are
mount on different mount point (you can do this, raid module is not
loaded, and so...). And now you load the module and md device is
registered. That would not be really nice, also if it is ulikely that you
could damnage your system




-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:22    [W:0.074 / U:4.832 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site