topic Re: exported filesystem problems in Operating System - HP-UX

exported filesystem problems

Chet Woods — Tue, 06 Apr 2004 14:07:49 GMT

I've had several filesystems mounted for quite some time now and could always connect to them in by mapping a network drive letter(in windows) to them. As of yesterday I could no longer do this. I'm getting 2 errors: 1)the network pathe found and 2)RPC timed out error. I've rebooted the
/sbin/init.d/nfs.server, didn't work, then rebooted the server itself. It's still not working. Looking at the processes that are running everything looks right with NFS/RPC. Anyone have any suggestions??

Your help is appreciated in advance,
Chet

Re: exported filesystem problems

A. Clay Stephenson — Tue, 06 Apr 2004 14:26:48 GMT

It would help to see the output of nfsstat -snr. It would also help to know if these are automounted filesystems or hardmounted.

My first task would be to attempt to mount one of these filesystems from a UNIX client as a hardmount. If this fails, the error messages would mean more to this Forum and if it works, you know where to concentrate your efforts.

Among the things to check are the permissions of the underlying mountpoints of the exported filesystem(s). You will need to unexport the filesystems and then unmount the filesystems to determine this.

Re: exported filesystem problems

Chet Woods — Tue, 06 Apr 2004 14:39:07 GMT

Here's something that might help: I tried to "remove" an exported filesystem through SAM and it gave me an error message of:
UILIB ERROR:
ui_get_object_field() returned UILIB_FIELD_NOT_FOUND

Arguments were:
field_name: "FS_AT_WHERE_CONF"
buffer:0x74073440

I hit "ok", it appeared to removed the filesystem, I then tried to re-export it and SAM stated it was already exported.

Attached is the output from nfsstat -nsr.

Thanks,
Chet

Re: exported filesystem problems

Sundar_7 — Tue, 06 Apr 2004 14:42:15 GMT

Hi Chet,

if you are not able to map the unix shares from a windows box, then check to see if smbd and nmbd are running in the system.

Thanks,

Sundar.

Re: exported filesystem problems

A. Clay Stephenson — Tue, 06 Apr 2004 14:45:49 GMT

Those error messages are associated with SAM. You need to get SAM completely out of the picture and use the command-line for this --- like a real UNIX guy. We don't need other distractions getting in the way. Note that your readdir's are 0 --- this strongly suggests a permissions problem. You also didn't answer if the aoutmounter is in play. Above all, try a manual NFS mount from another UNIX client.

Re: exported filesystem problems

A. Clay Stephenson — Tue, 06 Apr 2004 14:47:53 GMT

I am making the silly assumption that since you specifically mentioned NFS that this is not Samba; ie, you really are running NFS clients on your PC's?

Re: exported filesystem problems

Sundar_7 — Tue, 06 Apr 2004 14:54:46 GMT

Hi Chet, also post the showmount -e output.

Re: exported filesystem problems

Chet Woods — Tue, 06 Apr 2004 14:59:39 GMT

It doesn't appear to be a permission issue (see showmount output below) These are NOT automounted. Yes, we are using a "Reflection" nfs client on the PC's.

Showmount -e output:
root@uxpdev2:/etc/rc.config.d>showmount -e
export list for uxpdev2:
/apps/act (everyone)
/unload/vertex2/registerdata (everyone)
/opt/vertextmp/registerdata (everyone)
/unload/vertex/archive/registerdata (everyone)
/unload/vertex/uxpprod/archive_migration_12312001 (everyone)
/unload/vertex/uxpprod/archive_migration_12312002 (everyone)
/unload/vertex/archive_2002/registerdata (everyone)
/unload/actuate (everyone)
/unload/vertex/uxpprod/archive_migration_12312003 (everyone)
/cdrom (everyone)

Thanks.

Re: exported filesystem problems

Sundar_7 — Tue, 06 Apr 2004 15:10:17 GMT

pcnfsd running in the system ?

Re: exported filesystem problems

Chet Woods — Tue, 06 Apr 2004 15:14:15 GMT

pcnfsd is running...looks like this:
root 1533 1 0 12:45:12 ? 0:02 /usr/sbin/rpc.pcnfsd

Re: exported filesystem problems

A. Clay Stephenson — Tue, 06 Apr 2004 15:20:52 GMT

Showmount is not all that useful as the data can be very stale. If you don't have another UNIX box to server as a client then you can at least do an NFS mount to the same server:

e.g.
mkdir /testmount
chmod 755 /testmount
mount -F nfs hostname:/apps/act /testmount

ls /testmount

Re: exported filesystem problems

Chet Woods — Tue, 06 Apr 2004 15:21:34 GMT

I CAN mount an exported filesystem on another UNIX server. So the problem lies somewhere on the PC or possibly with PCNFS or RPC deamons???

Re: exported filesystem problems

Chet Woods — Tue, 06 Apr 2004 15:26:18 GMT

Tried the automount process verbatim and it didn't work (on either the same or another server). Here's the output:
mount: uxpdev2:/apps/act/testmount was either ignored or not found in /etc/fstab

Re: exported filesystem problems

A. Clay Stephenson — Tue, 06 Apr 2004 15:40:59 GMT

That's not an automount command; that's a mount command but anyway there needs to be a space between the filesystem and the mountpoint.

Re: exported filesystem problems

Chet Woods — Tue, 06 Apr 2004 15:48:18 GMT

Yeah, mount I meant,...with the space it works.

Thanks.

Re: exported filesystem problems

A. Clay Stephenson — Tue, 06 Apr 2004 16:02:59 GMT

Now see if you can access files under the NFS mountpoint, /testmount, as a regular user. If that works then there is nothing wrong with the NFS server. You can then do a umount /testmount to remove this NFS mount.

If all is well up to this point, it is time to start debugging on the other end. Follow Reflections Troubleshooting Tips for NFS in the manual and that should zero in on the problem.