On Saturday February 4, [EMAIL PROTECTED] wrote: > > Ahh, i almost forget! > > The mdadm is sometimes drop "cannot allocate memory" and next try > "segfault" > > when i try -G --bitmap=internal on 2TB arrays! > > And after segfault, the full raid is stops... > > > > Cheers, > > Janos > > I think i found the bug, its me. :-) > > Today it happens again, and i see, i have misstyped the "internal" word like > "intarnal". > The mdadm is accepted that, and try to make the bitmap on NFS again, and > crashed the raid. > > I think it is neccessary to better test: > > - the bitmap file's fs > - the filename itself. > (i mean did not allow the current directory, or the internal and none to be > a separated option)
That sound's like a good idea... require a filename to contain at least one '/', and quite possibly test the filesystem type. bitmaps are known to have problems on reiserfs and nfs. They were developed and tested on ext3 and there is some slightly hairy code in there... Thanks for the suggestions. NeilBrown - 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
