Quoth Andrew Sharp <[EMAIL PROTECTED]>:
> There is some info about this in the archives a while back I believe.
> It's a networking problem IIRC. Try setting the MTU on the client and/or
> server to something lower, and/or fiddle with the [rw]size options of the
MTU was the same on all machines,
On Mon, Jul 19, 2004 at 08:14:01PM +, Michael Rex wrote:
> Quoth Michael Rex <[EMAIL PROTECTED]>:
> > I mounted the share, copied a small file to it, everything went fine.
> > I copied a larger file (about 300kb), the process hangs and the latter
> > messages appear in syslog.
>
> After some m
Quoth Michael Rex <[EMAIL PROTECTED]>:
> I mounted the share, copied a small file to it, everything went fine.
> I copied a larger file (about 300kb), the process hangs and the latter
> messages appear in syslog.
After some more fiddling I found out the following:
When I mount the share on my PC
Quoth Mike Edwards <[EMAIL PROTECTED]>:
> Check /var/log/messages and/or /var/log/syslog on both the client and
> the server.
Well, the only NFS related message on the server is
Jul 19 19:30:48 yog-sothoth rpc.mountd: authenticated mount request from
fuckup.local:611 for /test (/test)
when I mou
Check /var/log/messages and/or /var/log/syslog on both the client and
the server.
On Mon, Jul 19, 2004 at 03:23:51PM +, Michael Rex said:
> Date: 19 Jul 2004 15:23:51 GMT
> From: Michael Rex <[EMAIL PROTECTED]>
> To: debian-sparc@lists.debian.org
> Subject: NFS problem
Hi,
I'm having a problem with NFS here. I tried to set up my Sparcstation 5
as NFS server using Sarge with the kernel NFS server. Everything works
fine as long as I don't copy anything to the NFS shares. I can copy
files from the share, I can creates directories and files there, I can
even copy sm
Hi,
mounting nfs with 2.2.19 has a known bug.
regards
On Mon, 2002-03-04 at 17:52, Heinrich Rebehn wrote:
> Hi,
>
> when i try to mount a filesystem from an NFS server, the mount hangs for
> several
> minutes and syslog prints the following errors:
>
> kernel: lockd_up: no pid, 2 users??
> ke
> > Hi,
> >
> > mounting nfs with 2.2.19 has a known bug.
> >
> > regards
>
>
> Thanks. Do older versions work better?
>
> Heinrich
>
>
Personally I would rather up- the downgrade...,
bye
--
Hakan Kuecuekyilmaz, University of Applied Sciences Esslingen, Germany
<[EMAIL PROTECTED]> | <[
> outland kernel: Kernel panic: Whee. Kernel does fpu/atomic unaligned
> load/store.
(...)
> @outland:~$ uname -a
> Linux outland 2.2.19 #1 Mon Apr 2 14:21:55 EDT 2001 sparc64 unknown
(...)
> Perhaps I should upgrade (compile) to a more recent kernel. Suggestions
> please?
Yeap. You sould upg
Thanks to those who replied. Just to give a few more details about
what is happening, here is the kernel panic string.
outland kernel: Kernel panic: Whee. Kernel does fpu/atomic unaligned
load/store.
Perhaps I should upgrade (compile) to a more recent kernel. Suggestions
please?
@outland:~$ u
the kernel, which potato is using has a known nfs mount kernel bug.
regards
On Tue, 2002-02-19 at 18:26, Jim Crumley wrote:
> On Tue, Feb 19, 2002 at 08:48:54AM -0800, John Mastrolia wrote:
> > Basically, I'm trying to mount a nfs partition exported from a
> > Solaris 2.7 box (using both v2 and
On Tue, Feb 19, 2002 at 08:48:54AM -0800, John Mastrolia wrote:
> Basically, I'm trying to mount a nfs partition exported from a
> Solaris 2.7 box (using both v2 and v3 nfs) and get a panic error
> that freezes the local workstation. Could someone point me to the
> document that points out the er
Being relatively new to debian, I was surprised that my system
will panic when mounting an nfs partition. I checked the man-page
for mount options, read a few FAQ's, and searched through the last
few months of list archives. Nothing was mentioned about this
problem, so it must be something I'm d
13 matches
Mail list logo
