On Thursday, 30 January 2003 at 17:05:02 +0000, Matthew Seaman wrote: > On Thu, Jan 30, 2003 at 06:55:50AM -0800, steve heistand wrote: >> I have a machine running 4.7-release (possibly and old build) with >> 4 disks I am using vinum to make a raid5 volume out of. When I >> write large amounts of data to it the machine crashes. I can dd >> one big file and it crashes at 154M, if I copy in smaller files it >> dies around 100M (varies) > > Have you looked at the http://www.vinumvm.org/vinum/how-to-debug.html > page? It's going to be practically impossible to help you unless you > can supply a whole lot more detailed information about what's gone > wrong.
On Thursday, 30 January 2003 at 11:07:05 -0800, steve heistand wrote: > --- "J. Seth Henry" <[EMAIL PROTECTED]> wrote: >> I strongly suspect you have a hardware problem. Either in the >> controller, or one of the disks. It is possible that something is >> crapping out in vinum, or in the kernel, but I've dumped massive >> amounts of data to a vinum raid5 volume before, and it didn't even >> burp - much less crash. I've also had bad EIDE disks cause the >> system to panic, and they weren't even in a RAID configuration; >> just normal data drives. >> >> As it is, Greg Lehey is "the man" when it comes to >> vinum, (something about >> writing it or other) so I'll ask the obligatory >> questions >> >> +What hardware is this (SCSI/EIDE/other?) >> +Can you post a copy of any console messages or >> panic info? > > It locks tight, not even anything to the console before it > hangs.... ;( They are eide drives. I have another fileserver in the > same type of setup (different hardware) and its never had a problem > at all. > > Am trying a debug kernel, not hopeful since it locks up without > sending any messages. Next will be to try a PCI eide controller > and or using the drives individually for a bit to see if they are > bad. I took note of these messages when they were sent. I haven't replied earlier because basically Matthew and Seth have told you what to do. Supply that info and we'll see where we go from there. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message