From: "J. Bruce Fields" <bfields@fieldses.org>
To: "J.A. Magallón" <jamagallon@ono.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: NFS problems in 2.6.33-rc6: Unknown error 526
Date: Mon, 1 Feb 2010 13:39:58 -0500 [thread overview]
Message-ID: <20100201183958.GC16879@fieldses.org> (raw)
In-Reply-To: <20100131234619.0f8460b9@werewolf.home>
On Sun, Jan 31, 2010 at 11:46:19PM +0100, J.A. Magallón wrote:
> Hi...
>
> With latest kernel I get this between linux boxes with that kernel:
>
> bran:/etc# showmount -e annwn.nfs
> Export list for annwn:
> /scratch/local 192.168.1.0/24,....
Does reverting f39bde24b275ddc45df1ed835725b609e178c7a0 help?
--b.
> bran:~# mount -v -t nfs -o tcp annwn.nfs:/scratch/local /scratch/shared
> mount.nfs: timeout set for Sun Jan 31 23:38:04 2010
> mount.nfs: trying text-based options 'tcp,addr=192.168.1.10,vers=4,clientaddr=192.168.1.1'
> mount.nfs: mount(2): Unknown error 526
> mount.nfs: Unknown error 526
>
> NFS works fine between the client and a Solaris server, and with an older
> linux server.
> Unfortunately, all my boxes got updated, so I can not try between
> a box with latest kernel and other with previous one.
>
> With this scenario, I blame the new kernel server code, any ideas ?
>
> TIA
>
> --
> J.A. Magallon <jamagallon()ono!com> \ Software is like sex:
> \ It's better when it's free
> Mandriva Linux release 2010.1 (Cooker) for x86_64
> Linux 2.6.32.3-desktop-0.rc2.1mnb (gcc 4.4.2 ) SMP
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2010-02-01 18:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-31 22:46 J.A. Magallón
2010-02-01 18:39 ` J. Bruce Fields [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100201183958.GC16879@fieldses.org \
--to=bfields@fieldses.org \
--cc=jamagallon@ono.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome