WWW.SA.I-PDF.INFO
FREE ELECTRONIC LIBRARY - Abstracts, books, theses
 
<< HOME
CONTACTS



Pages:     | 1 |   ...   | 2 | 3 || 5 | 6 |

«EMC® VNX™ Series Release 7.0 Managing Volumes and File Systems on VNX™ Manually P/N 300-011-808 REV A01 EMC Corporation Corporate Headquarters: ...»

-- [ Page 4 ] --

(Optional) Create a mount point Before you use a newly created file system, you can optionally create a mount point on a Data Mover. The server_mount command creates the mount point if a mount point does not exist.

A mount point name must begin with a slash (/), followed by alphanumeric characters (for example, /new). The name can include multiple components that make the mounted file system appear to be a logical subdirectory (for example, /new1/new2 or /new1/new2/new3/new4). A mount point name can have a maximum of seven components (for example, new1/new2/new3/.../new7).

With the exception of NMFS, mount a file system only on the last component of a multicomponent mount point name. No file system should be mounted on intermediate components of a mount point name. For example, if you have a file system mounted on the /new1 mount point, do not mount a file system on a mount point named /new1/new2.

Action

To create a mount point on a Data Mover, use this command syntax:

$ server_mountpoint movername -create pathname

where:

movername = name of the Data Mover pathname = path to mount point

Example:

To create a mount point named server_3, type:

$ server_mountpoint server_3 -create /ufs1 Output server_3: done

–  –  –

Note: The server_mount command creates a mount point if one does not exist.

Commands to obtain the information you need to mount a file system:

◆ nas_fs -list command to list existing file systems ◆ nas_server -list command to view Data Mover names ◆ server_mountpoint movername -list command to view mount points on a Data Mover A file system can be mounted read/write on one Data Mover (default) or read-only on multiple Data Movers concurrently. When a file system is mounted read/write on a Data Mover, only that Data Mover is allowed access to the file system. No other Data Mover is allowed access.

When a file system is mounted read-only on a Data Mover, clients cannot write to the file system regardless of the client’s access permissions. A file system can be mounted read-only on multiple Data Movers concurrently, as this is the default for checkpoint and TimeFinder/FS file systems.

File systems are mounted permanently by default. If you unmount a file system temporarily and then restart the file server, the file system is remounted automatically.

–  –  –

If you create a mount point on a Data Mover, mount the file system on that mount point.

The -option argument is used to specify a number of mount options. The VNX Command Line Interface Reference for File provides a complete list of mount options available.

–  –  –

Action mount_point = path to mount point for the Data Mover; a mount_point must begin with a forward slash (/)

Example:

To mount ufs1 on mount point /ufs1 with access checking policy set to NATIVE and nooplock turned on, type:

$ server_mount server_2 -option accesspolicy=NATIVE,nooplock ufs1 /ufs1 Output server_2: done (Optional) Create an NMFS An NMFS must be mounted read-only on the Data Mover.

Use the server_mount command to mount the file system for read-only access on each Data Mover from which you want to provide read-only access to the file system. Unmount all file systems from a Data Mover on page 78 explains how to unmount a file system from a

Data Mover:

1. Create an NMFS by using this command syntax:

$ nas_fs -name name -type nmfs -create

–  –  –

3. Mount the NMFS as read-only on the Data Mover by using this command syntax:

$ server_mount movername -option options fs_name mount_point

–  –  –

Create a new component file system The steps to create a new component file system and to mount it on an NMFS are similar to

steps followed for mounting any file system:

1. Create a volume for the component file system.

2. Create the component file system on the new volume by using this command syntax:

$ nas_fs -name name -create volume_name

–  –  –

3. Mount the component file system to the NMFS by using this command syntax:

$ server_mount movername -option options fs_name mount_point

–  –  –

= pathname of the NMFS which is in the format /nmfs path/component mount_point file system name

Example:

To mount ufs1, as a part of the NMFS nmfs1, type:

$ server_mount server_2 ufs1 /nmfs1/ufs1

Output:

server_2: done

–  –  –

This section provides information on how to manage existing volumes manually. Unless otherwise noted, the procedures apply to all the system models.

Note: List volumes on page 35 describes how to view a list of volumes.

The tasks to manage volumes are:

◆ Check volume capacity on page 52 ◆ Rename a volume on page 52 ◆ Clone a volume on page 53 ◆ Delete a metavolume or stripe volume on page 54 ◆ Delete a slice volume on page 56

–  –  –





Clone a volume You can make an exact copy of a stripe volume, slice volume, or metavolume by cloning it.

Cloning duplicates only the volume structure. It does not copy the file system or the data in the file system at the time of cloning.

If -option disktype and source_volume:destination_volume are used together, the behavior differs depending on which option is specified first.

Action

To clone a volume, use this command syntax:

$ nas_volume -Clone volume_name -option disktype=disktype source_volume:destination_volume,...

where:

volume_name = name of the volume to be cloned disktype = type of disk to be created source_volume = sets a specific disk volume set for the source volume destination_volume = sets a specific disk volume set for the destination volume

Example:

To clone the metavolume mtv1, type:

$ nas_volume -Clone mtv1 Output

–  –  –

Delete a metavolume or stripe volume You cannot delete a metavolume or stripe volume in use by a file system. The tasks to delete

a metavolume or stripe volume are:

◆ List metavolume information on page 54 ◆ Delete a metavolume or stripe volume on page 55 List metavolume information To ensure that the metavolume or stripe volume that you want to delete is not in use, list the volume information and check the in_use parameter.

–  –  –

Delete a metavolume or stripe volume Remove all file systems from a volume that you want to delete. If the volume is part of a larger metavolume configuration, remove file systems from the larger metavolume and delete the larger metavolume before deleting the volume.

Action

To delete a metavolume, use this command syntax:

$ nas_volume -delete volume_name

where:

volume_name = name of the metavolume to delete

Example:

To delete a metavolume named mtv1, type:

$ nas_volume -delete mtv1 Output

–  –  –

List slice volume information To ensure that the slice volume you want to delete is not in use, list the volume information and check the in_use parameter.

–  –  –

Delete a slice volume If the slice volume is part of a metavolume configuration, remove file systems from the metavolume and delete the metavolume before deleting the slice volume.

Action

To delete a slice volume, use this command syntax:

$ nas_slice -delete slice_name

where:

slice_name = name of the slice volume to delete

Example:

To delete slice volume information for slv1, type:

$ nas_slice -delete slv1

–  –  –

This section provides information on how to manage existing file systems.

Unless otherwise noted, these procedures apply to all system models.

The tasks to manage file systems are:

◆ Export a file system on page 60 ◆ List file systems on page 62 ◆ View the file system configuration information on page 63 ◆ List mount points on page 63 ◆ List mounted file systems on page 64 ◆ Check disk space capacity for a single mounted file system on page ◆ Check disk space capacity for all mounted file systems on page 65 ◆ Check inode capacity on page 66 ◆ Extend a file system on page 68 ◆ Extend replicated file systems on page 69 ◆ Adjust file system size threshold on page 72 ◆ Add an existing file system to an NMFS on page 73 ◆ Move an NMFS on page 74 ◆ Rename a file system on page 75 ◆ Enhance file read/write performance on page 76 ◆ Unmount all file systems from a Data Mover on page 78 ◆ Delete a file system or NMFS on page 80

Managing Volumes and File Systems on VNX Manually 7.0 59Managing File Systems

Export a file system To make a file system available to NFS users, you must export a path to the file system from a Data Mover by using the server_export command. Each time the server_export command is run, an entry is added to the existing entries in an export table. Entries to the table are permanent and are automatically reexported when the system restarts.

Use the -option argument to specify:

◆ Level of access ◆ Authentication method for each exported file system ◆ Whether the exported file system can be accessed by using only NFSv4 For CIFS clients, the component file system is shared.

The tasks to export a file system are:

◆ Export a file system from a Data Mover for NFS access on page 60 ◆ Export a file system from a Data Mover for CIFS access on page 61 ◆ Export an NMFS on page 61 Export a file system from a Data Mover for NFS access

–  –  –

pathname = pathname of the file system to mount

Example:

To export the file system ufs2 on an NFS client, type:

$ server_export server_3 -Protocol nfs -option root=10.1.1.1 /ufs2

–  –  –

Export a file system from a Data Mover for CIFS access Action

To export a file system for CIFS access, use this command syntax:

$ server_export movername -Protocol cifs -name sharename/pathname

where:

movername = name of the Data Mover sharename = name of the shared component file system pathname = pathname of the file system to mount

Example:

To export the file system ufs2 on a CIFS client, type:

$ server_export server_3 -Protocol cifs -name ufs2 /ufs2 Output server_3: done Export an NMFS When you export an NMFS, you export and mount the NMFS root which provides access to all component file systems. Any options set on the NMFS root propagate to the component file systems. However, you can export the component file system with different export options.

When you export a component file system in an NMFS hierarchy, you can export only the mount point path of the component file system. Subdirectories of the component file system cannot be exported.

–  –  –

Note

Column definitions:

id — ID of the file system (assigned automatically) inuse — Indicates whether the file system registered into the mount table of a Data Mover; y indicates yes, n indicates no type — Type of file system acl — Access control value for the file system volume — Volume on which the file system resides name — Name assigned to the file system server — ID of the Data Mover that is accessing the file system

–  –  –

View the file system configuration information If a file system is created by using the AVM feature, it has an associated storage pool. The pool option identifies the storage pool associated with that file system. Otherwise, the pool option has no value or is blank.

Action

To view configuration information of a specific file system, use this command syntax:

$ nas_fs -info fs_name

where:

fs_name = name of the file system

Example:

To view configuration information on ufs1, type:

$ nas_fs -info ufs1

–  –  –

List mount points Action

To list the mount points on a Data Mover, use this command syntax:

$ server_mountpoint movername -list

where:

movername = name of the Data Mover

Example:

To list mount points on server_3, type:

$ server_mountpoint server_3 -list

–  –  –

List mounted file systems You can view a list of all file systems currently mounted on a specific Data Mover and the options assigned to each of them.

–  –  –

Check disk space capacity for a single mounted file system You must maintain file system space with care because it is a limited resource. The nas_fs command lets you view the disk space on the file system, that is, the total amount of allocated space, the current free and used space, and the percentage of used space.

Action

To display disk space of a file system, use this command syntax:

$ nas_fs -size fs_name

where:

fs_name = name of the file system

Example:

To view the total space available on ufs1, type:

$ nas_fs -size ufs1 Output total = 2041959 avail = 2041954 used = 6 ( 0% )(sizes in MB) (blockcount = 4246732800 ) volume: total = 2073600 (sizes in MB) ( blockcount = 4246732800 ) root_fs_3 on / uxfs,perm,rw Check disk space capacity for all mounted file systems Action

To display the total disk space of all file systems on a Data Mover, use this command syntax:

$ server_df movername

where:

movername = name of the Data Mover

Example:

To view the total disk space of all file systems on server_2, type:

$ server_df server_2 Output

–  –  –

Check inode capacity The number of inodes defines the number of filenames and directory names that the file system can contain. You can check the inode capacity of a single file system or all file systems on a specific Data Mover. A specific number of inodes is allocated to a file system when you create it.

The nas_fs command lists the total number of inodes allocated to the file system, the available and used inodes, and the percentage of total inodes in use by the file system.

The tasks to check the inode capacity of a file system on a Data Mover are:

◆ View the inode capacity of a single file system on a Data Mover on page 66 ◆ View the inode capacity of all file systems on a Data Mover on page 67 View the inode capacity of a single file system on a Data Mover

–  –  –

Note

Column definitions:

Filesystem — Name of the file system inodes — Total number of inodes allocated to the file system used — Number of inodes in use by the file system avail — Number of free inodes available for use by the file system capacity — Percentage of total inodes in use Mounted on — Name of the file system mount point on the Data Mover View the inode capacity of all file systems on a Data Mover Action

To view the inode capacity of all file systems on a Data Mover, use this command syntax:

$ server_df movername -inode

where:

movername = name of the Data Mover

Example:



Pages:     | 1 |   ...   | 2 | 3 || 5 | 6 |


Similar works:

«UNITED STATES ENVIRONMENTAL PROTECTION AGENCY WASHINGTON, D.C. 20460 OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE 3N 2 4 A MEMORANDUM SUBJECT: Superfund Oversight Guidance &&omFROM: Susan E. Bromm, Director Office of Site Remediation Enforcement TO: Office of Regional Counsel Superfund Branch Chiefs Regional CERCLA Program Branch Chiefs Regional Finance Office Branch Chiefs The purpose of this memo is to transmit two guidance documents regarding Superfund oversight. These guidance...»

«THE AUTHENTIC MEDINA Home to more than 300,000 people, Marrkech’s Medina, or ancient quarter, is a maze of narrow, winding lanes brimming with activity. Stroll through this vibrant community.THE EXCURSION INCLUDES: Visit to the tanneries An appointed guide will escort you through the tanneries near Bab Debbagh and offer you a walking tour of the Medina with a visit to a Moufek and Foundouks Moukef, a gathering of labourers; to Foundouks, original lodging and trading houses for merchants, as...»

«2016 TEXAS Effective: March 15, 2016 TABLE OF CONTENTS Table of Contents Specifications Revisions Section A General Definitions and Abbreviations General Information, Requirements, & Conditions Warranty Provisions Section B Bus Body & Chassis Specifications Aisle Width Alternator Battery (ies) Battery and Electrical Compartments Body Data (Identification) Plate Brake, Parking Brakes, Service Bumper, Front Bumper, Rear Child Check System Cooling System Daytime Running Lamps Drive Shaft Guards...»

«SGC Rapport 2013:270 Biogas upgrading – Review of commercial technologies (Biogasuppgradering – Granskning av kommersiella tekniker) Fredric Bauer, Christian Hulteberg, Tobias Persson, Daniel Tamm ”Catalyzing energygas development for sustainable solutions” SGC Rapport 2013:270 Svenskt Gastekniskt Center AB, SGC Om SGC SGC är ett spjutspetsföretag inom hållbar utveckling med ett nationellt uppdrag. Vi arbetar under devisen ”Catalyzing energygas development for sustainable...»

«UNDERSTANDING POWER PURCHASE AGREEMENTS Understanding Understanding Power Power Purchase Purchase Agreements Agreements Funded by Developed by Institutional Partners Understanding Power Purchase Agreements – Version 1.3 Published Under the Creative Commons Attribution-Noncommercial-Share Alike 4.0 International License (cc by no sa) PDF and EPUB Editions Available Here: http://go.usa.gov/FBzH Please contact Mohamed Badissy (CLDP) at mbadissy@doc.gov with any questions regarding this...»

«Chapter Twelve Federalism and the Liberal Party John Roskam Thank you to John Stone and The Samuel Griffith Society for the opportunity to present this paper. As someone who attended the first meeting of the Society in Melbourne in July, 1992 I welcome the opportunity to reflect upon what has occurred since that first meeting – even if such a reflection provides little cause for joy. It is entirely appropriate that this topic be considered, given that at a previous meeting of the Society...»

«WESTERN AND NORTHERN CANADIAN PROTOCOL (WNCP) Our Way Is a Valid Way Professional Educator Resource A WNCP Professional Development Resource for Educators Cover Blanket Graphic © Manitoba Education. 2000 History and culture roll across the provinces and territories in colourful unity, blending in spiritual and creative energy that accentuates the beauty of the First people. Diversity as well as Unity become the celebration as we join forces to share the wealth of learning and living. This...»

«STATEMENT OF SUZAN SHOWN HARJO, PRESIDENT, THE MORNING STAR INSTITUTE, FOR THE OVERSIGHT HEARING ON “STOLEN IDENTITIES: THE IMPACT OF RACIST STEREOTYPES ON INDIGENOUS PEOPLE,” BEFORE THE COMMITTEE ON INDIAN AFFAIRS, UNITED STATES SENATE, WASHINGTON, D.C., MAY 5, 2011 Mr. Chairman, Mr. Vice Chairman and Members of the Committee on Indian Affairs, thank you for holding this oversight hearing on this important issue. I am Suzan Shown Harjo, President of The Morning Star Institute, a national...»

«Chronic Lymphocytic Leukemia Overview The information that follows is an overview of this type of cancer. It is based on the more detailed information in our document, Leukemia-Chronic Lymphocytic. This document and other information can be obtained by calling 1-800-227-2345 or visiting our website at www.cancer.org. What is chronic lymphocytic leukemia? Cancer starts when cells in the body begin to grow out of control. Cells in nearly any part of the body can become cancer, and can spread to...»

«Preprints of the Max Planck Institute for Research on Collective Goods Bonn 2008/43 Systemic Risk in the Financial Sector: An Analysis of the Subprime-Mortgage Financial Crisis Martin Hellwig MAX PLANCK SOCIETY Preprints of the Max Planck Institute for Research on Collective Goods Bonn 2008/43 Systemic Risk in the Financial Sector: An Analysis of the Subprime-Mortgage Financial Crisis Martin Hellwig November 2008 Max Planck Institute for Research on Collective Goods, Kurt-Schumacher-Str. 10,...»

«Advice on completing the Expression of Interest to Undertake a VET Course 2014 Read this introductory section before completing the Expression of Interest form This Expression of Interest to Undertake a VET Course provided by 5 Star Training & Consulting Pty Ltd is provided to assist with the placement of students into the appropriate VET courses. A separate Expression of Interest is required for each VET course a student wishes to be considered for placement. The student completes Parts 1, 2,...»

«JOURNAL OF SCIENTIFIC EXPLORATION A Publication of the Society for Scienti¢c Exploration Volume 22, Number 1 2008 Page Editorial 1 Editorial Peter A. Sturrock 5 Theme and Variations: The Life and Work of Ian Stevenson Emily Williams Kelly Carlos S. Alvarado Essays 11 Ian Stevenson: Recollections Kerr L. White 18 Reflections on the Life and Work of Ian Stevenson Alan Gauld 36 Ian Stevenson and Cases of the Reincarnation Type Jim B. Tucker 44 Ian Stevenson and the Modern Study of Spontaneous ESP...»





 
<<  HOME   |    CONTACTS
2017 www.sa.i-pdf.info - Abstracts, books, theses

Materials of this site are available for review, all rights belong to their respective owners.
If you do not agree with the fact that your material is placed on this site, please, email us, we will within 1-2 business days delete him.