It seems Vallo Kallaste wrote: > > Here's the sequence of what I did: > > 1. I had i386 system with two 20GB IBM ATA disks and 5.0-current system > built from March 31 sources. First I used striping over two disks and > put /usr filesystem onto it, did overnight testing and all was well. > 2. Same system, same sources plus two same disks. Now I tried raid5 over > four disks and failed to extract pax archive, got deadlock, not panic. > 3. Same system, downgraded to 4.0-RELEASE. Raid5 over four disks and I > failed to extract pax archive, got panic. > No softupdates. Same story here, but using softupdates or async mounts I can reproduce the hang or panic in less than 60 secs.. Vinum with raid5 is plain broken, include INVARIANTS in the kernel and see why... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
- Re: Deadlock with vinum raid5 Soren Schmidt
- Re: Deadlock with vinum raid5 Alfred Perlstein
- Re: Deadlock with vinum raid5 Soren Schmidt
- Re: Deadlock with vinum raid5 Bernd Walter
- Re: Deadlock with vinum raid5 Soren Schmidt
- Re: Deadlock with vinum raid5 Greg Lehey
- Re: Deadlock with vinum raid5 Matthew Dillon
- Re: Deadlock with vinum raid5 Bernd Walter
- Re: Deadlock with vinum raid5 Alfred Perlstein
- Re: Deadlock with vinum raid5 Vallo Kallaste
- Re: Deadlock with vinum raid5 Soren Schmidt
- Re: Deadlock with vinum raid5 Matthew Dillon
- Re: Deadlock with vinum raid5 Soren Schmidt
- Re: Deadlock with vinum raid5 Greg Lehey
- Re: Deadlock with vinum raid5 Greg Lehey
- Re: Deadlock with vinum raid5 Vallo Kallaste
- Re: Deadlock with vinum raid5 Bernd Walter
- Re: Deadlock with vinum raid5 Greg Lehey
- Re: Deadlock with vinum raid5 Bernd Walter
- Re: Deadlock with vinum raid5 Soren Schmidt
- Re: Deadlock with vinum raid5 Greg Lehey