On Friday February 3, [EMAIL PROTECTED] wrote:
> >
> > If it is an internal bitmap.... it should work.
> > Are there any kernel messages during boot that might be interesting?
>
> Sorry, i did not log this, and i dont want to restart the sync and system
> for this.
> Anyway, i add back the bitmap, and the next crash we will see....
>
> I mean this was:
> "bitmap is only support in raid1.
> bitmap is removed."
>
> But not so sure. :(
Close enough. Here is the fix.
NeilBrown
Signed-off-by: Neil Brown <[EMAIL PROTECTED]>
### Diffstat output
./drivers/md/md.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff ./drivers/md/md.c~current~ ./drivers/md/md.c
--- ./drivers/md/md.c~current~ 2006-02-03 08:57:28.000000000 +1100
+++ ./drivers/md/md.c 2006-02-03 11:22:57.000000000 +1100
@@ -763,7 +763,8 @@ static int super_90_validate(mddev_t *md
if (sb->state & (1<<MD_SB_BITMAP_PRESENT) &&
mddev->bitmap_file == NULL) {
- if (mddev->level != 1 && mddev->level != 5 &&
mddev->level != 6
+ if (mddev->level != 1 && && mddev->level != 4
+ && mddev->level != 5 && mddev->level != 6
&& mddev->level != 10) {
/* FIXME use a better test */
printk(KERN_WARNING "md: bitmaps not supported
for this level.\n");
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
