Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 27 May 2000 12:37:55 +0930
From:      Greg Lehey <grog@lemis.com>
To:        Darren Evans <darren@profero.com>
Cc:        freebsd-questions@FreeBSD.ORG
Subject:   Re: copying from a nfs mounted filesystem onto a vinum volume crashes
Message-ID:  <20000527123755.B30853@freebie.lemis.com>
In-Reply-To: <000301bfc6f2$eab74d90$a99d24d4@vindaloo.profero.com>
References:  <20000526094609.C13702@freebie.lemis.com> <000301bfc6f2$eab74d90$a99d24d4@vindaloo.profero.com>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Friday, 26 May 2000 at 10:15:21 +0100, Darren Evans wrote:
> On  Friday, May 26, 2000 1:16 AM, Greg Lehey wrote:
>> 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.
>>>
>>> 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'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.
>
> 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.

What do you mean by "runaway process"?  Is it using CPU time?  Or is
it just hanging?  What does ps l say?

> 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.

A process looping in the kernel won't show any activity with ktrace.

> 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.

Above you say "This actually crashes our box.".  What do you mean by
that?

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: <http://docs.FreeBSD.org/cgi/mid.cgi?20000527123755.B30853>