public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: parinay <parinay@gmail.com>
To: "Peter Åstrand" <astrand@cendio.se>
Cc: nfs@lists.sourceforge.net
Subject: Re: PyNFS
Date: Wed, 24 May 2006 13:07:34 +0530	[thread overview]
Message-ID: <ea2ed4af0605240037h6f706bcre628a991de7b96a7@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0605240919340.6128@maggie.lkpg.cendio.se>

[-- Attachment #1: Type: text/plain, Size: 3213 bytes --]

Peter,
Sorry to bother you.
I am attempting to run, PyNFS and it is giving me tracebacks, I dont know
python at all.
Can you help me, getting it run ?

Following are the things that I have tried,
                    -As per the steps, executed, rpcgen.py  nfs4.x and
./setup.py install
                    -The binaries are installed @ ~python/bin

Hereafter i I try to run the nfs4stest, it give this trace back.Same is the
case for test_tree_net.py

My objective is to run this , on NetApp filer, from Linux/solaris NFS
client.
Please let me know, If I am missing something or If you want some more
information on this.
Awaiting.

thanks & regards
parina

-----------------snippet------------------------------------------------------------
[zorba@akam bin]$ ./test_tree_net.py 10.55.63.1 /mnt/test/
sys:1: DeprecationWarning: Non-ASCII character '\xc5' in file
./test_tree_net.py on line 5, but no encoding declared; see
http://www.python.org/peps/pep-0263.html for details
10.55.63.1 None
Traceback (most recent call last):
  File "./test_tree_net.py", line 426, in ?
    main(ncl, directory)
  File "./test_tree_net.py", line 91, in main
    ncl.init_connection()
  File "/root/python/lib/python/nfs4lib.py", line 538, in init_connection

  File "/root/python/lib/python/nfs4lib.py", line 793, in check_result

nfs4lib.BadCompoundRes: operation OP_SETCLIENTID returned result
NFS4ERR_INVAL
[zorba@akam bin]

[zorba@akam bin]$ ./nfs4stest.py nfs://myfiler:2049  -t -v st_lock

======================================================================
ERROR: LOCK range over 32 bits should work or return NFS4ERR_BAD_RANGE
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/root/python/lib/python/nfs4st/st_lock.py", line 12, in setUp
    self.init_connection()
  File "/root/python/lib/python/nfs4st/base_st_classes.py", line 540, in
init_connection
    self.failIfRaises(rpc.RPCException, ncl.init_connection,*args,**kwargs)
  File "/root/python/lib/python/nfs4st/base_st_classes.py", line 493, in
failIfRaises
    self.fail(e)
  File "/usr/src/build/475206-i386/install/usr/lib/python2.3/unittest.py",
line 270, in fail
    raise self.failureException, msg
AssertionError: operation OP_SETCLIENTID returned result NFS4ERR_INVAL

On 5/24/06, Peter Åstrand <astrand@cendio.se> wrote:
>
> > Any help on PyNFS for NFSv2 NFSv3 ??
> > I have downloaded  PyNFS for NFSv4.In process of onfiguring and running
it.
> > Any help on that will also be very much helpfull.
>
> I haven't looked at PyNFS for two years, but then, I was able to generate
> Python code for the mount protocol, by using rpcgen.py. This "mount
> client" can be found in the UNFS3 CVS.
>
> Don't know about the rest of NFSv2/v3, though.
>
> Kind regards,
> --
> Peter Åstrand           ThinLinc Chief Developer
> Cendio                  http://www.cendio.se
> Teknikringen 3
> 583 30 Linköping        Phone: +46-13-21 46 00
>


-- 
easy is right
begin right and you're easy
continue easy and you're right
the right way to go easy is to forget the right way
and forget that the going is easy....

[-- Attachment #2: Type: text/html, Size: 4351 bytes --]

  reply	other threads:[~2006-05-24  7:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-24  3:59 PyNFS parinay
2006-05-24  7:22 ` PyNFS Peter Åstrand
2006-05-24  7:37   ` parinay [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-03-09 22:36 pynfs J. Bruce Fields

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=ea2ed4af0605240037h6f706bcre628a991de7b96a7@mail.gmail.com \
    --to=parinay@gmail.com \
    --cc=astrand@cendio.se \
    --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