On Sat, Apr 01, 2000 at 09:11:40AM +0930, Greg Lehey wrote:
> On Friday, 31 March 2000 at 21:32:22 +0200, Søren Schmidt wrote:
> > Yup, Greg and I know of this problem, it also happens with the wd
> > driver and with CAM, so the problem is probably not the driver.
> > I'm investigating this right now, and it looks like vinum is
> > botching a struct buf in action somehow.
>
> I'm not sure that this is the same problem. Please supply the
> information I ask for in http://www.lemis.com/vinum/how-to-debug.html.
>
> The problem that Søren and I are looking at is usually a panic. We
> don't really know where it's happening, but we're each sure it's not
> in *our* code :-) From a Vinum standpoint, it happens between the time
> that Vinum sends a request to the driver and when the I/O completes,
> so it's difficult to blame Vinum. On the other hand, we've seen it
> with SCSI as well, so it's difficult to blame the driver. I'm half
> guessing that it's something else altogether which is spamming freed
> data. Vinum mallocs the buffer headers rather than using geteblk(),
> which could explain why it happens only with Vinum.
Greg - I'm using vinums raid5 code since months now for FreeBSDs CVS-Tree on
7x 200M disks - it does not hang for me since a long time.
The latest current I tested R5 well is from 19th March on alpha. That's shortly
before PHKs changes - I don't beleave that it introduced something new.
The only problem with R5 I know of is parity corruption because of a bug in
lockrange() for which I've already send you a fix. Even it is a general bug it
seems only to cause problems together with softupdates.
--
B.Walter COSMO-Project http://www.cosmo-project.de
[EMAIL PROTECTED] Usergroup [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
