On Thursday March 6, taeuber@xxxxxxx wrote: > > What is this internal bitmap good for? Is there a documentation > somewhere on the net about this? man md and search for BITMAP. There is a section of BITMAP WRITE-INTENT LOGGING. > > I just repeated the following: > > monosan:~ # mdadm -C /dev/md9 -l1 -n2 -x0 /dev/md4 /dev/etherd/e22.0 > mdadm: Defaulting to verion 1.0 metadata > mdadm: /dev/md4 appears to be part of a raid array: > level=raid1 devices=2 ctime=Thu Mar 6 09:39:37 2008 > mdadm: /dev/etherd/e22.0 appears to be part of a raid array: > level=raid1 devices=2 ctime=Thu Mar 6 09:39:37 2008 > Continue creating array? y > mdadm: array /dev/md9 started. > > monosan:~ # mdadm -V > mdadm - v2.6.2 - 21st May 2007 > > monosan:~ # mdadm /dev/md9 -f /dev/etherd/e22.0 > mdadm: set /dev/etherd/e22.0 faulty in /dev/md9 > > monosan:~ # mdadm /dev/md9 -r /dev/etherd/e22.0 > mdadm: hot removed /dev/etherd/e22.0 > > monosan:~ # mdadm /dev/md9 -a /dev/etherd/e22.0 > mdadm: /dev/etherd/e22.0 not large enough to join array Hmm.. I just read through the change logs and I see there was a bug here that was fixed in 2.6.3. If you want an update from SuSE you would need to log a bug report in the Novell bugzilla. Alternately request v0.90 metadata (--metadata=0.90) That will avoid the bug. NeilBrown -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
