Sponsored Content
Full Discussion: qtree & quota in netapp
Special Forums Hardware Filesystems, Disks and Memory qtree & quota in netapp Post 302320854 by funksen on Friday 29th of May 2009 06:19:10 AM
Old 05-29-2009
exported via nfs?

then add root=yourunixhost, rw=youunixhost to the exports file and run exportfs /yourfilesystem on the filer

now mount it and you will be able to delete all directories

which security style do you use for the qtree?
 

9 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

backup NetApp using dump command

I have been trying to backup my NetApp /vol/vol0 data to local tape drive. It is around 68GB. The tape I am using is DLT tape and should be able to handle 70GB data. However, dump always aborted around reaching 57~58GB data. Tape drive is attached on NetApp. 1st try to dump /vol/vol0 to... (2 Replies)
Discussion started by: yellowfish
2 Replies

2. Solaris

Use DFM Netapp 3.01 R1 on Solaris 8

I have this problem when i integrate a new san switch in DFM 3.01 R1 : dfm fcswitch add switchname1 Error: Host switchname2 (11197) already exists. switchname2 is a similar san switch but in another fabric, switchname2 is already integrated in DFM database. Bests Regards Olivier (2 Replies)
Discussion started by: omainfroy
2 Replies

3. Cybersecurity

netapp security

Hi all Background some of the users shuold have access to a folder on the netapp and for other users the access should be denied Question How can I doing that ? Thanks at advance Sam (3 Replies)
Discussion started by: skfn1203
3 Replies

4. UNIX for Dummies Questions & Answers

can not get netapp to mount RPC Not registered error

getting "NFS mount: netapp : RPC: Program not registered" error searched the site but none of the fixes from previous threads are helping (2 Replies)
Discussion started by: calamine
2 Replies

5. Solaris

Can't see Netapp LUN on Solaris using LPFC after reboot.

Hi, I've just edited this post. I found the solution for this. Thanks. (0 Replies)
Discussion started by: gwhelan
0 Replies

6. Filesystems, Disks and Memory

NFSv4 on Netapp and Redhat 5.3 as Client

Hi Folks! I'm new in using NFSv4 and do have a little trouble. I had a partition working with NFSv3, at the beginning i couldn't see on the client the German umlauts letters {ö,ä,ü} a manipulation of the LANG environment variable helped and the filenames with this letters were shown normally... (2 Replies)
Discussion started by: oku
2 Replies

7. AIX

Netapp iscsi lun

Hi, I have aix 6.1 box. I want to configure iscsi luns from netapp storage. I tried in google but not getting proper solution for that. i m not getting the proper iqn name. Please share me the steps to complete this requirements. Thanks in advance. (1 Reply)
Discussion started by: sunnybee
1 Replies

8. Solaris

Netapp filer details - command?

What command can I use to find out details about a netapp filer. I have a directory that is a filer i would like to know details about the source host/folder that it points to. Thanks. (2 Replies)
Discussion started by: jjohnson
2 Replies

9. Hardware

Flexvols NetApp FlexClone technology

Hello, Please help me understand Copy on Write technology in reference to Flexvols. NetApp FlexClone technology This is in reference to Snap Clone: Instant, self-serviced database-on-demand Best regards, Vishal (0 Replies)
Discussion started by: admin_db
0 Replies
exportfs(8)						      System Manager's Manual						       exportfs(8)

NAME
exportfs - maintain list of NFS exported file systems SYNOPSIS
/usr/sbin/exportfs [-avi] [-o options,..] [client:/path ..] /usr/sbin/exportfs -r [-v] /usr/sbin/exportfs [-av] -u [client:/path ..] /usr/sbin/exportfs [-v] DESCRIPTION
The exportfs command is used to maintain the current table of exported file systems for NFS. This list is kept in a separate file named /var/lib/nfs/xtab which is read by mountd when a remote host requests access to mount a file tree, and parts of the list which are active are kept in the kernel's export table. Normally this xtab file is initialized with the list of all file systems named in /etc/exports by invoking exportfs -a. However, administrators can choose to add and delete individual file systems without modifying /etc/exports using exportfs. Any export requests which identify a specific host (rather than a subnet or netgroup etc) are entered directly into the kernel's export ta- ble as well as being written to /var/lib/nfs/xtab. Further, any mount points listed in /var/lib/nfs/rmtab which match a non host-specific export request will cause an appropriate export entry for the host given in rmtab to be entered into the kernel's export table. OPTIONS
-a Export or unexport all directories. -o options,... Specify a list of export options in the same manner as in exports(5). -i Ignore the /etc/exports file, so that only default options and options given on the command line are used. -r Reexport all directories. It synchronizes /var/lib/nfs/xtab with /etc/exports. It removes entries in /var/lib/nfs/xtab which are deleted from /etc/exports, and remove any entries from the kernel export table which are no longer valid. -u Unexport one or more directories. -v Be verbose. When exporting or unexporting, show what's going on. When displaying the current export list, also display the list of export options. DISCUSSION
Exporting Directories The first synopsis shows how to invoke the command when adding new entries to the export table. When using exportfs -a, all directories in exports(5) are added to xtab and the resulting list is pushed into the kernel. The host:/path argument specifies the directory to export along with the host or hosts to export it to. All formats described in exports(5) are supported; to export a directory to the world, simply specify :/path. The export options for a particular host/directory pair derive from several sources. There is a set of default options which can be over- ridden by entries in /etc/exports (unless the -i option is given). In addition, the administrator may overide any options from these sources using the -o argument which takes a comma-separated list of options in the same fashion as one would specify them in exports(5). Thus, exportfs can also be used to modify the export options of an already exported directory. Modifications of the kernel export table used by nfsd(8) take place immediately after parsing the command line and updating the xtab file. The default export options are sync,ro,root_squash,no_delay. Unexporting Directories The third synopsis shows how to unexported a currently exported directory. When using exportfs -ua, all entries listed in xtab are removed from the kernel export tables, and the file is cleared. This effectively shuts down all NFS activity. To remove individial export entries, one can specify a host:/path pair. This deletes the specified entry from xtab and removes the corre- sponding kernel entry (if any). Dumping the Export Table Invoking exportfs without further options shows the current list of exported file systems. When giving the -v option, the list of flags pertaining to each export are shown in addition. EXAMPLES
The following adds all directories listed in /etc/exports to /var/lib/nfs/xtab and pushes the resulting export entries into the kernel: # exportfs -a To export the /usr/tmp directory to host djando, allowing asynchronous writes, one would do this: # exportfs -o async django:/usr/tmp DEPENDENCIES
Exporting to IP networks, DNS and NIS domains does not enable clients from these groups to access NFS immediately; rather, these sorts of exports are hints to mountd(8) to grant any mount requests from these clients. This is usually not a big problem, because any existing mounts are preserved in rmtab across reboots. When unexporting a network or domain entry, any current exports to members of this group will be checked against the remaining valid exports and if they themselves are nolonger valid they will be removed. SEE ALSO
exports(5), mountd(8) AUTHORS
Olaf Kirch, <okir@monad.swb.de> Neil Brown, <neilb@cse.unsw.edu.au> 7 Sep 1999 exportfs(8)
All times are GMT -4. The time now is 06:36 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy