I am running HP9000 Containers version A.03.01. I have the container up and running. I now need to mount an exported file system from another HPUX server with both read and write permissions. I can get the mount okay but from the container I cannot read or write properly to the mounted file system. The NFS server exporting the file system is running HPUX 11.31, here is the dfstab export line:
The container /etc/fstab entry is this:
When logged into the container as root, I am able to touch a file. The ownership of this file is odd. It is:
I would have expected the owner be root. There are other files in this exported file system owned by root that from the container, root is unable to read.
What am I doing incorrectly?
Moderator's Comments:
Please view this code tag video for how to use code tags when posting code and data.
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)
Dear all,
Kindly need your advice on swap issue on my container, SunOS 5.10.
We have allocated swap 20GB and memory 8 GB. We have some application installed on the container.
A few days ago we experienced a very slow system response...even for command like ls, df -k, etc..
I tried to... (8 Replies)
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)
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)
Hi whenever i execute ls -ltr i get following entry.
But there is no such user as 501 .What is the issue.
#ls -ltr
drwxrwxrwx 2 501 501 3896 Aug 19 10:46 File1
# cat /etc/passwd | grep 501
The problem is this folder is mouted on client machine using nfs.But after mouting client... (4 Replies)
Hi All,
I have a problem as follows.
Historically, there was an Ultra10 workstation running Solaris 8 using automount to access NFS volumes on a Solaris 8 server.
The Ultra 10 was retired and the Solaris 8 server has been migrated to a Legacy Container (Solaris 8 Branded, whole root,... (9 Replies)
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)
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)
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)
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
LEARN ABOUT ULTRIX
fstab
fstab(5) File Formats Manual fstab(5)Name
fstab - file containing static information about known file systems
Description
The file contains descriptive information about the known file systems. By convention, is created and maintained as a read-only file by
the system administrator. Each file system is described by its own line within The order of these lines and the file systems they repre-
sent is important because and sequentially process in the performance of their tasks.
The format of each file system description in is as follows:
spec:file:type:freq:passno:name:options
The meanings of these fields are:
spec The block special file name of the device on which the file system is located. It can also be a network name for such as or
file The pathname of the directory on which the file system is mounted.
type How the file system is mounted. The ways in which a file system can be mounted are:
rw - mount the file system read-write
ro - mount the file system read only
rq - mount the file system read-write with quotas
sw - make the special file part of the swap space
xx - ignore the entry
freq The frequency (in days) with which the command dumps the rw, ro, and rq file systems.
passno The order in which the command checks the rw, ro, and rq file systems at reboot time.
name The name of the file system type. File systems can have the following types: ufs -- ULTRIX file system and nfs -- SUN Network
file system.
options The options field. This field contains an arbitrary string meaningful only when mounting file systems with the specified file
system type name, such as NFS. The specific options are described in the reference pages.
Special actions occur for file systems of type sw and rq at system boot time. File systems of type sw are made part of the swap space by
the command and disk quotas are automatically processed by the command and then enabled by the command for rq file systems.
Examples
Here is a sample file:
/dev/ra0a:/:rw:1:1:ufs::
/dev/ra1g:/usr:rw:1:2:ufs::
/@bigvax:/bigvax:rw:0:0:nfs::
/usr/uws2.0@bigvax:/usr/uws2.0:rw:0:0:nfs:soft,bg,nosuid:
/usr/dec@bigvax:/usr/dec:rw:0:0:nfs:bg,soft,nosuid:
/usr/pro/xyz@vax:/usr/pro/xyz:rw:0:0:nfs:bg,soft,intr,nosuid:
The last three entries in the sample shown use NFS options as described in the reference page.
Restrictions
The passno field of the root file system should be specified as 1. Other file systems should have larger values. File systems on the same
device should have distinct passno fields. File systems on different devices may have the identical passno fields to allow them to be
simultaneously checked.
All field delimiters (:) must exist within each file system description; only the options field may not be present. However, only the
fields spec and type are meaningful to sw file systems and only the type field is meaningful to xx file systems.
The file system description within should be parsed only through use of the routines.
Files
File system information file
See Alsogetfsent(3x), dump(8), fsck(8), mount(8), mount(8nfs), mount(8ufs)quotacheck(8), quotaon(8), swapon(8)fstab(5)