Cannot determine current working directory - Suse

This is a discussion on Cannot determine current working directory - Suse ; Hello, I'm having an issue where I receive a "Cannot determine current working directory" when I try to peform an su or other various commands within an NFS mounted filesystem on an Irix 6.5.5 system. The NFS filesystem is being ...

+ Reply to Thread
Results 1 to 4 of 4

Thread: Cannot determine current working directory

  1. Cannot determine current working directory

    Hello,

    I'm having an issue where I receive a "Cannot determine current
    working directory" when I try to peform an su or other various
    commands within an NFS mounted filesystem on an Irix 6.5.5 system.
    The NFS filesystem is being exported by an Open SuSE 10.2 system
    (fully patched). So far, I haven't hand any problem traversing the
    NFS filesystem on the Irix system.

    On the Irix platform I have the following config:

    excript from /etc/fstab
    padme:/powervault/usr1 /usr1 nfs vers=3,rw,soft,intr,bg 0 0

    output from ls -la / | grep usr1 commands
    drwxrwxrwx 65 root sys 4096 Mar 6 15:19 usr1

    output from mount command
    padme:/powervault/usr1 on /usr1 type nfs
    (vers=3,rw,soft,intr,bg,dev=140003)

    On the OpenSuSE 10.2 platform I have the following config:

    excript from /etc/exports
    /powervault/usr1 *(rw,no_root_squash,sync)

    output from exportfs command
    /powervault/usr1


    This filesystem is also being mounted by other OpenSuSE 10.2 (fully
    patched) systems and I'm not experiencing any problems. I've read
    other posts on the web indicating that I should unmount the NFS
    filesystem, change the permissions of the mount point, and then
    remount the filesystem. I've done that already without correcting
    this problem.

    All of these systems are on a closed, flat, 100 base-t, class c
    network.

    Thanks in advance,

    Rob





  2. Re: Cannot determine current working directory

    On 2008-03-06 19:44, Rob wrote:
    > Hello,
    >
    > I'm having an issue where I receive a "Cannot determine current
    > working directory" when I try to peform an su or other various
    > commands within an NFS mounted filesystem on an Irix 6.5.5 system.
    > The NFS filesystem is being exported by an Open SuSE 10.2 system
    > (fully patched). So far, I haven't hand any problem traversing the
    > NFS filesystem on the Irix system.
    >
    > On the Irix platform I have the following config:
    >
    > excript from /etc/fstab
    > padme:/powervault/usr1 /usr1 nfs vers=3,rw,soft,intr,bg 0 0
    >
    > output from ls -la / | grep usr1 commands
    > drwxrwxrwx 65 root sys 4096 Mar 6 15:19 usr1
    >
    > output from mount command
    > padme:/powervault/usr1 on /usr1 type nfs
    > (vers=3,rw,soft,intr,bg,dev=140003)
    >
    > On the OpenSuSE 10.2 platform I have the following config:
    >
    > excript from /etc/exports
    > /powervault/usr1 *(rw,no_root_squash,sync)


    I will say that look crazy :-(
    Anyway, root at your suse box is nobody at your Irix box.
    You maybe need anon=0 mount option. (even more crazy when it
    come to security) You must trust all users on your local network,
    maybe only you have access to it :-)

    Do dmesg and see the error messages from mountd.

    /bb

  3. Re: Cannot determine current working directory

    Hello Again,

    I just wanted to add some more info to my original post. Maybe this
    will help some.

    Again, thanks in advance,

    Rob


    Padme (Dell Precision 470 running Open SuSE 10.2)

    rramsey@padme:~> cat /etc/exports
    /powervault/usr1 *(rw,no_root_squash,sync)
    /powervault/usr2 *(rw,no_root_squash,sync)
    /powervault/usr6 *(rw,no_root_squash,sync)
    /powervault/usr7 *(rw,no_root_squash,sync)
    /powervault/home *(rw,no_root_squash,sync)
    /powervault/admin/ *(rw,no_root_squash,sync)

    padme:/home/rramsey # showmount -a
    All mount points on padme:
    *:/powervault/usr1
    *:/powervault/usr2
    *:/powervault/usr6
    *:/powervault/usr7
    *:/powervault/home
    *:/powervault/admin
    198.49.246.200:*
    198.49.246.208:*
    198.49.246.210:*
    198.49.246.211:*
    198.49.246.220:*
    198.49.246.230:*
    198.49.246.235:*
    198.49.246.236:*
    198.49.246.238:*

    padme:/home/rramsey # exportfs -v
    /powervault/usr1
    (rw,wdelay,no_root_squash)
    /powervault/usr2
    (rw,wdelay,no_root_squash)
    /powervault/usr6
    (rw,wdelay,no_root_squash)
    /powervault/usr7
    (rw,wdelay,no_root_squash)
    /powervault/home
    (rw,wdelay,no_root_squash)
    /powervault/admin
    (rw,wdelay,no_root_squash)

    rramsey@padme:/> ls -la | grep powervault
    lrwxrwxrwx 1 root root 17 2008-02-22 17:54 admin -> powervault/
    admin/
    drwxrwxrwx 10 root root 4096 2008-03-04 21:33 powervault
    lrwxrwxrwx 1 root root 16 2008-02-22 15:38 pvhome -> /powervault/
    home
    lrwxrwxrwx 1 root root 16 2008-03-04 17:08 usr1 -> /powervault/
    usr1
    lrwxrwxrwx 1 root root 16 2008-02-21 22:23 usr2 -> /powervault/
    usr2
    lrwxrwxrwx 1 root root 16 2008-02-21 22:24 usr3 -> /powervault/
    usr3
    lrwxrwxrwx 1 root root 16 2008-03-04 22:43 usr6 -> /powervault/
    usr6
    lrwxrwxrwx 1 root root 16 2008-03-04 22:43 usr7 -> /powervault/
    usr7

    padme:/powervault # ls -la
    total 5620120
    drwxrwxrwx 10 root root 4096 2008-03-04 21:33 .
    drwxr-xr-x 24 root root 4096 2008-03-04 22:43 ..
    drwxrwx--- 8 root root 4096 2008-02-22 17:59 admin
    drwxrwxrwx 11 root root 4096 2008-02-20 18:05 home
    drwx------ 2 root root 16384 2008-02-19 16:47 lost+found
    -rw-r--r-- 1 root root 5749319680 2008-02-21 21:10
    stk_win32_profile_backup.tar
    drwxrwxrwx 65 root root 4096 2008-03-07 21:23 usr1
    drwxrwxrwx 29 root root 4096 2008-02-21 22:24 usr2
    drwxrwxrwx 3 root root 4096 2008-02-21 19:56 usr3
    drwxrwxrwx 4 root root 4096 2007-07-09 22:40 usr6
    drwxrwxrwx 9 root root 4096 2008-01-18 23:38 usr7

    Pine (SGI O2 running Irix 6.5.5)

    $ cat /etc/fstab
    /dev/root / xfs rw,raw=/dev/rroot
    0 0
    #/dev/dsk/dks1d8s7 /usr1 xfs rw 0 0
    #/dev/dsk/dks1d5s0 /usr1/syslogs xfs rw 0 0
    #dismal:/usr7 /usr7 nfs
    vers=3,rw,soft,intr,bg 0 0
    padme:/powervault/usr1 /usr1 nfs
    vers=3,rw,soft,intr,bg 0 0
    padme:/powervault/usr2 /usr2 nfs
    vers=3,rw,soft,intr,bg 0 0
    padme:/powervault/usr6 /usr6 nfs
    vers=3,rw,soft,intr,bg 0 0
    padme:/powervault/usr7 /usr7 nfs
    vers=3,rw,soft,intr,bg 0 0
    padme:/powervault/admin /admin nfs
    vers=3,rw,soft,intr,bg 0 0
    padme:/powervault/home /pvhome nfs
    vers=3,rw,soft,intr,bg 0 0

    pine 6# mount
    /dev/root on / type xfs (rw,raw=/dev/rroot)
    /hw on /hw type hwgfs (rw)
    /proc on /proc type proc (rw)
    /dev/fd on /dev/fd type fd (rw)
    padme:/powervault/usr1 on /usr1 type nfs
    (vers=3,rw,soft,intr,bg,dev=140004)
    padme:/powervault/usr2 on /usr2 type nfs
    (vers=3,rw,soft,intr,bg,dev=140005)
    padme:/powervault/usr6 on /usr6 type nfs
    (vers=3,rw,soft,intr,bg,dev=140006)
    padme:/powervault/usr7 on /usr7 type nfs
    (vers=3,rw,soft,intr,bg,dev=140001)
    padme:/powervault/home on /pvhome type nfs
    (vers=3,rw,soft,intr,bg,dev=140002)
    padme:/powervault/admin on /admin type nfs
    (vers=3,rw,soft,intr,bg,dev=140003)

    pine 7# df -h
    Filesystem Type Size use avail %use Mounted on
    /dev/root xfs 17G 10G 6.9G 60% /
    padme:/powervault/usr1 nfs 538G 126G 412G 24% /usr1
    padme:/powervault/usr2 nfs 538G 126G 412G 24% /usr2
    padme:/powervault/usr6 nfs 538G 126G 412G 24% /usr6
    padme:/powervault/usr7 nfs 538G 126G 412G 24% /usr7
    padme:/powervault/home nfs 538G 126G 412G 24% /pvhome
    padme:/powervault/admin nfs 538G 126G 412G 24% /admin

    pine 16# ls -la / | grep usr
    lrwxr-xr-x 1 root sys 7 Sep 6 2001 bin -> usr/bin
    drwxrwxrwx 4 root sys 60 Jul 9 2007 old_usr6
    drwxr-xr-x 50 root sys 4096 Mar 6 20:10 usr
    drwxrwxrwx 65 root sys 4096 Mar 6 20:06 usr1
    drwxrwxrwx 29 root sys 4096 Feb 21 22:24 usr2
    drwxrwxrwx 4 root sys 4096 Jul 9 2007 usr6
    drwxrwxrwx 9 root sys 4096 Jan 18 23:38 usr7

    $ ls -la /usr1 | grep jerry
    drwxrwxrwx 8 jmeinzer users 4096 Mar 7 21:24 jerry


    $ cd /usr1
    $ su
    Password:
    pine 1# pwd
    /usr1
    pine 2# exit
    pine 3# $ cd jerry
    $ su
    Password:
    Cannot determine current working directory
    $ pwd
    /usr1/jerry

    $ cd /usr1
    $ touch myfile
    $ rm myfile
    $ cd jerry
    $ touch myfile
    $ rm myfile
    $ id
    uid=4205(rramsey) gid=100(users)
    $ su
    Password:
    pine 1# id
    uid=0(root) gid=0(sys)
    pine 2# pwd
    Cannot determine current directory

  4. Re: Cannot determine current working directory

    Hello,

    The final resolution to my problem was to modify the SGI systems /etc/
    fstab to read vers=2 instead of vers=3. I figured this out using the
    two links below.

    Maybe this will help others...

    http://nfs.sourceforge.net/nfs-howto/ar01s08.html

    Irix versions up to 6.5.12 have problems mounting file systems
    exported from Linux boxes - the mount point "gets lost," e.g.,:

    # mount linux:/disk1 /mnt
    # cd /mnt/xyz/abc
    # pwd
    /xyz/abc


    This is known IRIX bug (SGI bug 815265 - IRIX not liking file handles
    of less than 32 bytes), which is fixed in IRIX 6.5.13. If it is not
    possible to upgrade to IRIX 6.5.13, then the unofficial workaround is
    to force the Linux nfsd to always use 32 byte file handles.

    http://www.cse.unsw.edu.au/~neilb/os...ry/nfsd-2.html

    2. Understanding File Handles
    The file handle is a central part of all NFS and related operations. A
    file handle in an opaque string of bits which is used to uniquely
    identify a file or other filesystem object. In Version 2, the file
    handle in 256 bits long (32 bytes). In version 3, it is variable in
    length, up to 512 bits long.

    Thanks,

    Rob

+ Reply to Thread