> Since we (that's I, sorry) seem to discuss the whole bunch (not a bad idea > after, all hoping to get things into their places and finally enjoying a > really beautiful and functioning softraid), I allow myself to add another > question, real life, on a to-be-production system: > Okay, now I have a broken harddisk, one half of the mirror is gone. > Then I will have to dump the partitions, create a new mirror, and restore, > correct? > Next problem: There are quite a number of bays available in my box, > so that I can plug another drive for a local 'dump'. But irrespective > where I plug it, it won't come up:
Your trace shows that it comes up just fine. > > "softraid0 at root > > softraid0: roaming device sd1b -> sd2b > > softraid0: roaming device sd2b -> sd3b > > softraid0: roaming device sd1b -> sd2b > > softraid0: roaming device sd2b -> sd3b > > scsibus3 at softraid0: 1 targets > > sd4 at scsibus3 targ 0 lun 0: <OPENBSD, SR RAID 1, 003> SCSI2 0/direct fixed > > sd4: 285789MB, 512 bytes/sec, 585296066 sec total > > softraid0: volume sd4 is roaming, it used to be sd3, updating metadata You inserted a disk in front of others. From where I am sitting it is all working as designed. > > root on sd0a swap on sd0b dump on sd0b > > Automatic boot in progress: starting file system checks. > /dev/rsd0a: file system is clean; not checking > Can't open /dev/rsd3h: Device not configured > CAN'T CHECK FILE SYSTEM. > /dev/rsd3h: UNEXPECTED INCONSISTENCY; RUN fsck_ffs MANUALLY. > Can't open /dev/rsd3d: Device not configured > CAN'T CHECK FILE SYSTEM. > /dev/rsd3d: UNEXPECTED INCONSISTENCY; RUN fsck_ffs MANUALLY. > Can't open /dev/rsd3f: Device not configured > CAN'T CHECK FILE SYSTEM. > /dev/rsd3f: UNEXPECTED INCONSISTENCY; RUN fsck_ffs MANUALLY. > Can't open /dev/rsd3e: Device not configured > CAN'T CHECK FILE SYSTEM. > /dev/rsd3e: UNEXPECTED INCONSISTENCY; RUN fsck_ffs MANUALLY. > Can't open /dev/rsd3g: Device not configured > CAN'T CHECK FILE SYSTEM. > /dev/rsd3g: UNEXPECTED INCONSISTENCY; RUN fsck_ffs MANUALLY. > Can't open /dev/rsd3i: Device not configured > CAN'T CHECK FILE SYSTEM. > /dev/rsd3i: UNEXPECTED INCONSISTENCY; RUN fsck_ffs MANUALLY. > Can't open /dev/rsd3j: Device not configured > CAN'T CHECK FILE SYSTEM. > /dev/rsd3j: UNEXPECTED INCONSISTENCY; RUN fsck_ffs MANUALLY. > THE FOLLOWING FILE SYSTEMS HAD AN UNEXPECTED INCONSISTENCY: > > ffs: /dev/rsd3h (/home), ffs: /dev/rsd3d (/tmp), ffs: /dev/rsd3f > (/usr), ffs: /dev/rsd3e (/var), ffs: /dev/rsd3g (/var/mail), ffs: /dev/rsd3i > (/var/www), > ffs: /dev/rsd3j (/backup) > Automatic file system check failed; help! > > Enter pathname of shell or RETURN for sh: " > > Now that roaming is in the way. I wonder if softraid really should do this: > You plug an additional disk, higher or lower, and automatically it will > roam the mirror to drives of its liking, and inevitably fail the RAID thereby. This is not a softraid problem this is an OpenBSD problem. We don't have uuids or labels on disks so when disks move around bad things happen. This is a fact of life today that needs to be deal with accordingly.
