Linux NFS development
 help / color / mirror / Atom feed
From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: nfs@lists.sourceforge.net
Subject: intermittent EPERM
Date: Wed, 04 Oct 2006 07:36:41 -0400	[thread overview]
Message-ID: <1159961801.9991.11.camel@pc.ilinx> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 726 bytes --]

Since having upgraded my Ubuntu (edgy) kernel I have noticed the last
few revs of it cause intermittent EPERM errors on NFS clients.  For
example:

brian@pc:~$ sudo mount pc:/home/brian /mnt/test
brian@pc:~$ cd /mnt/test
brian@pc:/mnt/test$ cat .bash_profile
cat: .bash_profile: Permission denied
brian@pc:/mnt/test$ cat .bash_profile
cat: .bash_profile: Permission denied
brian@pc:/mnt/test$ cat .bash_profile
# .bash_profile

# Get the aliases and functions
if [ -f ~/.bashrc ]; then
        . ~/.bashrc
fi

It took three attempts at reading that file to not get an EPERM.

Is this a known issue of any sort?

Thanx,
b.

-- 
My other computer is your Microsoft Windows server.

Brian J. Murrell

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 348 bytes --]

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

[-- Attachment #3: Type: text/plain, Size: 140 bytes --]

_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

             reply	other threads:[~2006-10-04 11:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-04 11:36 Brian J. Murrell [this message]
2006-10-09  5:17 ` intermittent EPERM Neil Brown

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=1159961801.9991.11.camel@pc.ilinx \
    --to=brian@interlinx.bc.ca \
    --cc=nfs@lists.sourceforge.net \
    /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