On Saturday, 1 March 2003 at 20:43:10 +0200, Vallo Kallaste wrote: > On Thu, Feb 27, 2003 at 11:53:02AM +0200, Vallo Kallaste <vallo> wrote: > >>>> The vinum R5 and system as a whole were stable without >>>> softupdates. Only one problem remained after disabling softupdates, >>>> while being online and user I/O going on, rebuilding of failed disk >>>> corrupt the R5 volume completely. >>> >>> Yes, we've fixed a bug in that area. It had nothing to do with soft >>> updates, though. >> >> Oh, that's very good news, thank you! Yes, it had nothing to do with >> soft updates at all and that's why I had the "remained after" in the >> sentence. >> >>>> Don't know is it fixed or not as I don't have necessary hardware at >>>> the moment. The only way around was to quiesce the volume before >>>> rebuilding, umount it, and wait until rebuild finished. I'll suggest >>>> extensive testing cycle for everyone who's going to work with vinum >>>> R5. Concat, striping and mirroring has been a breeze but not so with >>>> R5. >>> >>> IIRC the rebuild bug bit any striped configuration. >> >> Ok, I definitely had problems only with R5, but you certainly know >> much better what it was exactly. I'll need to lend 50-pin SCSI cable >> and test vinum again. Will it matter on what version of FreeBSD I'll >> try on? My home system runs -current of Feb 5, but if you suggest >> -stable for consistent results, I'll do it. > > So I did. Loaned two SCSI disks and 50-pin cable. Things haven't > improved a bit, I'm very sorry to say it.
Sorry for the slow reply to this. I thought it would make sense to try things out here, and so I kept trying to find time, but I have to admit I just don't have it yet for a while. I haven't forgotten, and I hope that in a few weeks time I can spend some time chasing down a whole lot of Vinum issues. This is definitely the worst I have seen, and I'm really puzzled why it always happens to you. > # simulate disk crash by forcing one arbitrary subdisk down > # seems that vinum doesn't return values for command completion status > # checking? > echo "Stopping subdisk.. degraded mode" > vinum stop -f r5.p0.s3 # assume it was successful I wonder if there's something relating to stop -f that doesn't happen during a normal failure. But this was exactly the way I tested it in the first place. Greg -- See complete headers for address and phone numbers
pgp00000.pgp
Description: PGP signature
