> Ok, but the portmap service have to run on the server. Correct me if I
> get wrong, but the CentOS clients are asking the server for the port to
> use and this is what portmap does.
Actually I have a little more information, but I'm having a hard time
putting the pieces together. It looks like
Russell Miller wrote:
Hello.
>> > We're using nfs3 over tcp. rsize and wsize are 32768. Async is
>> > default, though I've tried sync.
>> Try rsize=8192 and wsize=8192. And my settings for /etc/hosts.allow,
>> maybe helpful?
> I can try it. But there's a reason that we're using 32768, apparen
On Mon, Dec 1, 2008 at 11:51 AM, Olaf Mueller <[EMAIL PROTECTED]>wrote:
> Russell Miller wrote:
>
> Hello.
>
> > We're using nfs3 over tcp. rsize and wsize are 32768. Async is
> > default, though I've tried sync.
> Try rsize=8192 and wsize=8192. And my settings for /etc/hosts.allow,
> maybe hel
Russell Miller wrote:
Hello.
> We're using nfs3 over tcp. rsize and wsize are 32768. Async is
> default, though I've tried sync.
Try rsize=8192 and wsize=8192. And my settings for /etc/hosts.allow,
maybe helpful?
portmap:127.0.0. 192.168.0.
lockd: 127.0.0. 192.168.0.
rquotad:
On Mon, Dec 1, 2008 at 11:48 AM, Olaf Mueller <[EMAIL PROTECTED]>wrote:
>
>
> > Funny thing is, turning on nfs debug and trying to trigger this
> > problem
> > seems to cause data corruption. Once it even managed to corrupt the
> > local disk writes to the points where the journals aborted and I
Russell Miller wrote:
Hello.
> We're using nfs3 over tcp. rsize and wsize are 32768. Async is
> default, though I've tried sync.
>
> Funny thing is, turning on nfs debug and trying to trigger this
> problem
> seems to cause data corruption. Once it even managed to corrupt the
> local disk w
On Mon, Dec 1, 2008 at 11:27 AM, Akemi Yagi <[EMAIL PROTECTED]> wrote:
> On Mon, Dec 1, 2008 at 11:10 AM, Russell Miller <[EMAIL PROTECTED]>
> wrote:
> > All 5.2 versions have this problem.
> >
> > --Russell
>
> You might want to look into upstream bugzilla reports:
>
> https://bugzilla.redhat.com
On Mon, Dec 1, 2008 at 11:10 AM, Russell Miller <[EMAIL PROTECTED]> wrote:
> All 5.2 versions have this problem.
>
> --Russell
You might want to look into upstream bugzilla reports:
https://bugzilla.redhat.com/show_bug.cgi?id=436004
and
https://bugzilla.redhat.com/show_bug.cgi?id=448130
and se
>
> Example settings from my /etc/auto.* (automount):
> *
> -fstype=nfs4,rw,tcp,port=2049,soft,intr,rsize=8192,wsize=8192,nosuid
> ://&
>
> Maybe the options *async* and the settings for rsize and wsize could be
> helpful for you?
We're using nfs3 over tcp. rsize and wsize are 32768. Async is
All 5.2 versions have this problem.
--Russell
On Mon, Dec 1, 2008 at 11:03 AM, Akemi Yagi <[EMAIL PROTECTED]> wrote:
> On Mon, Dec 1, 2008 at 10:32 AM, Russell Miller <[EMAIL PROTECTED]>
> wrote:
> > Hi, I was hoping someone would have an idea of what's going on here...
> >
> > We have two NFS i
Russell Miller wrote:
Hello.
> directory via NFS. To duplicate, I cd into a share in two windows,
> copy a
> 1G file in the first window, and just do an ls in the other. The ls
> will hang until the write is done.
> Has anyone seen problems like this? How did you solve them?
Your nfs settings
On Mon, Dec 1, 2008 at 10:32 AM, Russell Miller <[EMAIL PROTECTED]> wrote:
> Hi, I was hoping someone would have an idea of what's going on here...
>
> We have two NFS issues. One of which is certainly centos based, one of
> which we're not sure of.
>
> First issue is: As of Centos 5, we can't ma
Hi, I was hoping someone would have an idea of what's going on here...
We have two NFS issues. One of which is certainly centos based, one of
which we're not sure of.
First issue is: As of Centos 5, we can't make simultaneous access to a
directory via NFS. To duplicate, I cd into a share in tw
13 matches
Mail list logo
