Date: Fri, 26 May 2000 10:15:21 +0100 From: "Darren Evans" <darren@profero.com> To: "Greg Lehey" <grog@lemis.com> Cc: <freebsd-questions@FreeBSD.ORG> Subject: RE: copying from a nfs mounted filesystem onto a vinum volume crashes Message-ID: <000301bfc6f2$eab74d90$a99d24d4@vindaloo.profero.com> In-Reply-To: <20000526094609.C13702@freebie.lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Greg, sorry about the confusion. The box running software RAID aka provided by vinum has runaway processes. Anything that read's/ writes /raid becomes a runaway process. I cannot kill it. There's no kernel panic. I've also tried a ktrace on the "runaway" processes to see if there any system calls. There is no activity. No, the remote filesystem is not running under a RAID configuration. /mnt is not a RAID point, it's a local mount point that i've NFS mounted a remote filesystem onto. Then tried to copy from there onto the RAID filesystem. Hope i'm making sense :) thanks Darren -----Original Message----- From: Greg Lehey [mailto:grog@lemis.com] Sent: Friday, May 26, 2000 1:16 AM To: Darren Evans Cc: freebsd-questions@FreeBSD.ORG Subject: Re: copying from a nfs mounted filesystem onto a vinum volume crashes [Format recovered--see http://www.lemis.com/email/email-format.html] On Thursday, 25 May 2000 at 12:24:27 +0100, Darren Evans wrote: > On Friday, 28 April 2000 at 20:32:44 +0530, Rahul Siddharthan wrote: >> Hi, >> We need to set up an NFS fileserver which will serve around 10-20 >> machines. The hardware would preferably be Intel, for cost >> reasons, though fairly high-end (say a Pentium III 550+ MHz, 256 MB >> RAM, SCSI disks). The expected exported volume would be perhaps >> 50-60 GB. Is it a good idea to export a vinum volume over NFS? > > Greg Wrote... >> NFS doesn't know about the volume, it just knows about the file >> system. There's no reason why it shouldn't be on a Vinum volume. > > Hi Greg, > > what if a remote volume is nfs mounted not on the vinum volume > (actually mounted on /mnt) and then a cp -r /mnt/software /raid/software/ > is performed. /raid obviously being the vinum raid directory in a 1+0 > configuration. This actually crashes our box. I cannot SIGKILL the cp > command and have to /sbin/reboot to restore the system. > > Are there any nfs/vinum issues at present? Or am I being stupid? You're at least being confusing. Are you saying you /mnt is a remotely mounted Vinum volume? Which box crashes? What does the dump say? > I'm running 3.4-STABLE/SMP with the latest kernel tree and 2 Adaptec > aic7895 Ultra SCSI adapter controllers. There are some issues with 3-STABLE, though none which would explain this particular issue. I've fixed a number of bugs in 4-STABLE and -CURRENT, but it'll take me a few days to get them fixed and tested in 3-STABLE. > cvsup'd yesterday with *default release=cvs tag=RELENG_3. I'm led > to believe this tag is correct for 3.4-STABLE but not 100% confident > about that. Yes, that's correct for 3-STABLE. > Here's my vinum.conf Looks OK. > I've been reading / writing / deleting a 70 meg archive onto the > RAID volume without any problems at all. It's just NFS that causes > the headache :-( Strange. Get me the dump info and I'll take a look. Greg -- When replying to this message, please copy the original recipients. For more information, see http://www.lemis.com/questions.html 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-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?000301bfc6f2$eab74d90$a99d24d4>