03-16-2008
Well, I had very old server running 2.2 kernel and on that system I could see other submounts. It was my guess that it should be possible with new nfs too and defaults are only changed.
10 More Discussions You Might Find Interesting
1. Solaris
My 2GB /export/home/ directory is almost 100% full
df -k | grep /export/home
/dev/vx/dsk/rootdg/vl73 2031711 1951009 19751 99% /export/home
I intend to relocate it to a different 4GB filesystem late at night when there is no user on the system.
How do I go... (3 Replies)
Discussion started by: Msororaji
3 Replies
2. HP-UX
Hello,
If I have an export like:
/usr/temp -rw=ram:alligator
means that /usr/temp has "rw" permissions to ram and alligator machines and has "ro" to everyone else? (1 Reply)
Discussion started by: psimoes79
1 Replies
3. Solaris
Hey guys how do you determine what kind of Filesystem(vxfs) does a particular partition has.
Also how do you determine how many inodes it has and how my is used and free. (3 Replies)
Discussion started by: sbn
3 Replies
4. Linux
Hey guys how do you determine what kind of Filesystem(ext3) does a particular partition has.
Also how do you determine how many inodes it has and how my is used and free. (3 Replies)
Discussion started by: sbn
3 Replies
5. Solaris
I created a zpool and two ZFS volumes in OpenSolaris. I would like both ZFS volumes to be exportable. However, I don't know how to set that up.
These are the steps I did:
1) Create the zpool using raidz1 across five disks.
I have six disks and created a zpool across 5 of them. c4t0d0... (3 Replies)
Discussion started by: sqa777
3 Replies
6. Solaris
Hey Guys.
Could someone said if is possible take a NFS resource get it from a original Server a export it and mount it in a third server ?
Thank in Advace....
SUN ADMIN (3 Replies)
Discussion started by: aggadtech08
3 Replies
7. Solaris
we have a Solaris 8 nfs server that exported two shares. entries are in /etc/dfs/dfstab.
clients have been accessing these shares for several years.
we just rebooted this nfs server and noticed that no share gets exported. I don't see relevant messages from dmsg nor messages file, is there... (6 Replies)
Discussion started by: jalite19
6 Replies
8. AIX
Hi
How to export a file system from my aix box named ABC in such a way that everyone on the network should be able to import it
When on the client side if they give showmount -e ABC it should show like this:
# showmount -e ABC
export list for ABC:
/sybase/software (everyone) (2 Replies)
Discussion started by: newtoaixos
2 Replies
9. Red Hat
Hi Guys,
need help here.
i have windows server that share a folder C:/ABCDE
i configure samba client in Linux server as /EDCBA and it working fine.
then i want to share this /EDCBA to another Linux server using NFS.
in the /etc/exportfs i have put
/EDCBA - *(rw,no_root_squash)
... (1 Reply)
Discussion started by: prossits
1 Replies
10. AIX
Hi Guys,
need help here.
i have windows server that share a folder C:/ABCDE
i configure samba client in AIX server as /EDCBA and it working fine.
then i want to share this /EDCBA to another AIX server using NFS.
in the /etc/exportfs i have put
/EDCBA... (1 Reply)
Discussion started by: prossits
1 Replies
share(1M) share(1M)
NAME
share - make local resource available for mounting by remote systems
SYNOPSIS
share [-F FSType] [-o specific_options] [-d description] [pathname]
The share command exports, or makes a resource available for mounting, through a remote file system of type FSType. If the option -F FSType
is omitted, the first file system type listed in /etc/dfs/fstypes is used as default. For a description of NFS specific options, see
share_nfs(1M). pathname is the pathname of the directory to be shared. When invoked with no arguments, share displays all shared file sys-
tems.
-F FSType
Specify the filesystem type.
-o specific_options
The specific_options are used to control access of the shared resource. (See share_nfs(1M) for the NFS specific options.) They may be
any of the following:
rw
pathname is shared read/write to all clients. This is also the default behavior.
rw=client[:client]...
pathname is shared read/write only to the listed clients. No other systems can access pathname.
ro
pathname is shared read-only to all clients.
ro=client[:client]...
pathname is shared read-only only to the listed clients. No other systems can access pathname.
Separate multiple options with commas. Separate multiple operands for an option with colons. See .
-d description
The -d flag may be used to provide a description of the resource being shared.
Example 1: Sharing a Read-Only Filesystem
This line will share the /disk file system read-only at boot time.
share -F nfs -o ro /disk
Example 2: Invoking Multiple Options
The following command shares the filesystem /export/manuals, with members of the netgroup having read-only access and users on the speci-
fied host having read-write access.
share -F nfs -o ro=netgroup_name,rw=host1:host2:host3 /export/manuals
/etc/dfs/dfstab
list of share commands to be executed at boot time
/etc/dfs/fstypes
list of file system types, NFS by default
/etc/dfs/sharetab
system record of shared file systems
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
mountd(1M), nfsd(1M), share_nfs(1M), shareall(1M), unshare(1M), attributes(5)
Export (old terminology): file system sharing used to be called exporting on SunOS 4.x, so the share command used to be invoked as
exportfs(1B) or /usr/sbin/exportfs.
If share commands are invoked multiple times on the same filesystem, the last share invocation supersedes the previous--the options set by
the last share command replace the old options. For example, if read-write permission was given to usera on /somefs, then to give read-
write permission also to userb on /somefs:
example% share -F nfs -o rw=usera:userb /somefs
This behavior is not limited to sharing the root filesystem, but applies to all filesystems.
9 Dec 2004 share(1M)