Date: Fri, 31 Mar 2000 10:09:50 -0500 (EST) From: Systems Administrator <geniusj@ods.org> To: Greg Lehey <grog@lemis.com> Cc: current@FreeBSD.ORG Subject: Re: NFS/Vinum problems Message-ID: <Pine.BSF.4.10.10003311007140.28524-100000@ods.org> In-Reply-To: <20000331153939.O6764@mojave.worldwide.lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
The thing is i'm not sure if it's vinum, I could also duplicate this on
another machine without vinum.. except I duplicated it differently..
Consider the following perl script:
#!/usr/bin/perl
for ( ; ; ) {
system("fetch http://www.web.site/index.html");
}
Of course, replacing the site with something else, but on this one box
(and the raid), it panic'd the box.. See if you can duplicate this on any
4.0/5.0 boxes you have, I have tried on both and it worked, however it
does not crash 3.x boxes..
Try your luck,
Jason DiCioccio
On Fri, 31 Mar 2000, Greg Lehey wrote:
> On Friday, 31 March 2000 at 0:23:04 -0500, Systems Administrator wrote:
> >
> > panic: lockmgr: pid -2, exclusive lock holder 5 unlocking
> >
> > Syncing disks... Timedout SCB handled by another timeout
> > Timedout handled by another timeout
> >
> > That is what I get when doing a 'du -k' on an NFS mount from a remote
> > machine.. THe machine I am speaking of is the actual nfs server, i'm using
> > freebsd's default nfsd/mountd flags as specified by rc.conf.. However,
> > when I do lets say, a du -k on the mounted volume, I get that panic.. If
> > this is a known bug or if anyone knows how to fix this, get back to me
> > asap..
>
> Yes, I've seen something like this. My best guess is that there's a
> problem in the error recovery code in CAM, but that's just a guess.
> If you want to help, give us more information, at least what I'm
> asking for in http://www.lemis.com/vinum/how-to-debug.html. In
> addition, the way you're using NFS would be very helpful.
>
> Greg
> --
> Finger grog@lemis.com for PGP public key
> See complete headers for address and phone numbers
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.10003311007140.28524-100000>
