From: Ulrich Gemkow <ulrich.gemkow@ikr.uni-stuttgart.de>
To: Harald Dunkel <harald.dunkel@aixigo.de>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Linux 3.7 + Sun solaris 10: Problems when reading dir from application
Date: Sat, 6 Jul 2013 16:57:03 +0200 [thread overview]
Message-ID: <201307061657.04988.ulrich.gemkow@ikr.uni-stuttgart.de> (raw)
In-Reply-To: <20130705082740.3df4245a@dpcl082.ac.aixigo.de>
Hello Harald,
On Friday 05 July 2013 08:27:40 Harald Dunkel wrote:
> Hi Ulrich,
>
> On Mon, 4 Feb 2013 21:24:08 +0100
> Ulrich Gemkow <ulrich.gemkow@ikr.uni-stuttgart.de> wrote:
>
> > Hello,
> >
> > please allow a followup of my own on this:
> >
> > On Monday 04 February 2013 11:12:03 Ulrich Gemkow wrote:
> > > Hello,
> > >
> > > we upgraded our fileserver from Linux 3.2 to linux 3.7.6 and now have
> > > problems when accessing our nfs-mounted user homes from some sun-
> > > applications (i.e. Adobe Framemaker):
> > >
> > > In the applications file open box, no files are displayed. When entering
> > > the filename by path, the file can be opened. So it seems some kind of
> > > dir enumeration which is used by the sun applications is broken.
> > >
> > > Other programs on the sun like ls work as before and show all files.
> > >
> > > We are using NFSv3 (and cannot switch to v4). Our sun is a very old
> > > machine running Sun Solaris 10.
> >
> > When mounting with vers=2 on the sun (using NFSv2) the files
> > "reappear", so this is a clear regression in NFSv3 between
> > Linux 3.2 and Linux 3.7.
> >
>
> Have you considered upgrading your Solaris version? I had tons
> of problems with NFS on Solaris10u6 and 10u8, including unresponsive
> mount points, problems with delegations (esp. in the users' .ssh
> directories and .Xauthority files) and strange "permission
> denied" error messages for some ACL feature I never configured on
> the server.
>
> NFS in Solaris 10u10 works much better together with Linux. I
> haven't tried Solaris 11.
Thank you for your answer and your tip. For different reasond it
is difficult for us to update this machine.
In the time since my original post I found the reason for the
problem and a solution. I will explain this in a second mail
responding to Bruce which answered your mail yesterday.
Thanks again and best regards
Ulrich
>
> My servers run Squeeze and the Linux kernel from the squeeze-
> backports repository (3.2.0-0.bpo.4-amd64).
>
> > Maybe this can be fixed. I will be happy to give more info
> > if someone is interested.
> >
>
> That would be nice.
>
> Good luck
> Harri
>
--
|-----------------------------------------------------------------------
| Ulrich Gemkow
| University of Stuttgart
| Institute of Communication Networks and Computer Engineering (IKR)
|-----------------------------------------------------------------------
prev parent reply other threads:[~2013-07-06 15:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-04 10:12 Linux 3.7 + Sun solaris 10: Problems when reading dir from application Ulrich Gemkow
2013-02-04 20:24 ` Ulrich Gemkow
2013-07-05 6:27 ` Harald Dunkel
2013-07-05 19:27 ` J. Bruce Fields
2013-07-06 15:00 ` Ulrich Gemkow
2013-07-08 14:18 ` J. Bruce Fields
2013-07-06 14:57 ` Ulrich Gemkow [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=201307061657.04988.ulrich.gemkow@ikr.uni-stuttgart.de \
--to=ulrich.gemkow@ikr.uni-stuttgart.de \
--cc=harald.dunkel@aixigo.de \
--cc=linux-nfs@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;
as well as URLs for NNTP newsgroup(s).