Sponsored Content
Full Discussion: nfs issue.
Top Forums UNIX for Dummies Questions & Answers nfs issue. Post 302446581 by pinga123 on Thursday 19th of August 2010 07:16:21 AM
Old 08-19-2010
nfs issue.

Hi whenever i execute ls -ltr i get following entry.
But there is no such user as 501 .What is the issue.

Code:
#ls -ltr
drwxrwxrwx  2  501  501      3896 Aug 19 10:46 File1

Code:
# cat /etc/passwd | grep 501

The problem is this folder is mouted on client machine using nfs.But after mouting client machine get hang when i run df -h.
 

10 More Discussions You Might Find Interesting

1. Red Hat

nfs issue

Hello, I am running RHEL4 AS. /net/hostname is not always accessible. To solve the problem, I restart nfs, nfslock and portmap. in /var/log/messages, I keep on receiving: nfs_statfs: statfs error = 116 1] What does the above error mean? 2] any idea why portmap becomes dead? thanks. (1 Reply)
Discussion started by: melanie_pfefer
1 Replies

2. Red Hat

NFS Access Issue

Hi, I am facing issue on NFS. I have shared /data file file system on Server 192.192.192.1, added below lines in /etc/exports /data 192.192.192.2(rw,no_root_squash,sync) the owner of /data directory was test(uid 500) and same I have mounted on another server 192.192.192.2 where the... (3 Replies)
Discussion started by: manoj.solaris
3 Replies

3. Solaris

New Member with NFS Issue

Hi Guys. Maybe someione can assist here. Solaris 9 with a NFS mount point to a Netapp Filer. NFS V3 Changes in the environment: Moved from 1 building to a new one. (All the equipment and network stayed the same) Errors: nfs: NFS read failed for server netapp: error 11 (RPC: Server... (2 Replies)
Discussion started by: Boesman
2 Replies

4. UNIX for Dummies Questions & Answers

Copies over NFS and buffer issue

Hi All, i'm experiencing some strange behavior (at least for me) of my NFS server. In few words I have a server that exposes a directory via NFS and a client that mount it. I tested a simple copy from the client to the exposed directory of a file of 2GB and i see that on the server the file... (1 Reply)
Discussion started by: nichele
1 Replies

5. AIX

Weird nfs issue after TL upgrade

We recently upgraded 2 of our AIX 6.1 servers from TL4 to TL5. Both servers are on the same p7 780 frame, installed at the same time from the same image. Both servers are mounting the same nfs share after reboot what worked perfectly fine until the upgrade. Since the patching, one of the two... (5 Replies)
Discussion started by: zxmaus
5 Replies

6. Red Hat

NFS Performance Issue

Hi, I have a conflict. I have 2 servers: the 1st creates an application logs and the 2nd is an empty server. I want to export (read-only) from the 1st server by NFS the directory that contains the logs to the 2nd server. Now, the question is: If in the 2nd server i'm doing a lot of... (3 Replies)
Discussion started by: moshesa
3 Replies

7. Red Hat

NFS-Mount issue

Hi, While i try to mount the NFS file system on the client linux server i am getting the error message as (4 Replies)
Discussion started by: gsiva
4 Replies

8. Red Hat

NFS mount issue

Hi Friends, My source server is HP and my destination is linux. I have to mount a dir thru nfs from source to destn. almost 8 servers i did the same thing and it is working fine but on the 9th server i can't able to mount. Everything i have did for nfs configuration.Even i can able to ping... (1 Reply)
Discussion started by: Mohamed Thamim
1 Replies

9. Red Hat

NFS mounting issue

The server ip is 10.2.2.24. I have installed nfs-utils package the i have edited /etc/exports i have added the following line /home 10.2.2.0/24(rw,sync,no_root_squash,no_all_squash) i have saved, i have started the nfs service, then i am trying to mount nfs sharing from client machine using... (5 Replies)
Discussion started by: ainstin
5 Replies

10. Red Hat

NFS mount issue

we are facing a weird NFS mount issue on one of the linux host , a NFS volume of 2.4TB is mounted in the linux host , but df only reports 131g , which exactly matches rootfilesytem size nfs mount filer_filer1:/vol/bug_test/q0 131G 116G 8.5G 94% /nas/bug_test root... (2 Replies)
Discussion started by: skamal4u
2 Replies
MHPATH(1)                                                            [nmh-1.5]                                                           MHPATH(1)

NAME
mhpath - print full pathnames of nmh messages and folders SYNOPSIS
mhpath [+folder] [msgs] [-version] [-help] DESCRIPTION
mhpath expands and sorts the message list `msgs' and writes the full pathnames of the messages to the standard output separated by new- lines. If no `msgs' are specified, mhpath outputs the current mail folder's pathname instead. If the only argument is `+', your nmh "Path" is output; this can be useful in shell scripts. Contrasted with other nmh commands, a message argument to mhpath may often be intended for writing. Because of this: 1) the name "new" has been added to mhpath's list of reserved message names (the others are "first", "last", "prev", "next", "cur", and "all"). The new message is equivalent to the message after the last message in a folder (and equivalent to 1 in a folder without mes- sages). The "new" message may not be used as part of a message range. 2) Within a message list, the following designations may refer to messages that do not exist: a single numeric message name, the single message name "cur", and (obviously) the single message name "new". All other message designations must refer to at least one existing message, if the folder contains messages. 3) An empty folder is not in itself an error. A message number less than that of the smallest existing message in a folder is treated as if the message already exists. A message number greater than that of the highest existing message in a folder causes an "out of range" error message to be displayed. As part of a range designation that contains messages that do exist, message numbers less than the smallest, or greater than the highest, existing message in a folder are ignored. Examples: The current folder foo contains messages 3 5 6. Cur is 4. % mhpath /r/phyl/Mail/foo % mhpath all /r/phyl/Mail/foo/3 /r/phyl/Mail/foo/5 /r/phyl/Mail/foo/6 % mhpath 2001 mhpath: message 2001 out of range 1-6 % mhpath 1-2001 /r/phyl/Mail/foo/3 /r/phyl/Mail/foo/5 /r/phyl/Mail/foo/6 % mhpath new /r/phyl/Mail/foo/7 % mhpath last new /r/phyl/Mail/foo/6 /r/phyl/Mail/foo/7 % mhpath last-new mhpath: bad message list last-new % mhpath cur /r/phyl/Mail/foo/4 % mhpath 1-2 mhpath: no messages in range 1-2 % mhpath first:2 /r/phyl/Mail/foo/3 /r/phyl/Mail/foo/5 % mhpath 1 2 /r/phyl/Mail/foo/1 /r/phyl/Mail/foo/2 mhpath is also useful in back-quoted operations: % cd `mhpath +inbox` % echo `mhpath +` /r/phyl/Mail FILES
$HOME/.mh_profile The user profile PROFILE COMPONENTS
Path: To determine the user's nmh directory Current-Folder: To find the default current folder SEE ALSO
folder(1) DEFAULTS
`+folder' defaults to the current folder `msgs' defaults to none CONTEXT
None BUGS
Like all nmh commands, mhpath expands and sorts [msgs]. So don't expect mv `mhpath 501 500` to move 501 to 500. Quite the reverse. But mv `mhpath 501` `mhpath 500` will do the trick. Out of range message 0 is treated far more severely than large out of range message numbers. MH.6.8 11 June 2012 MHPATH(1)
All times are GMT -4. The time now is 05:11 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy