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



Pages:     | 1 |   ...   | 3 | 4 || 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 5 ] --

To view the inode capacity of all file systems on server_2, type:

$ server_df server_2 -inode

–  –  –

Extend a file system Before you begin When a file system nears its maximum capacity, you can increase the file system size by adding volumes. To increase the total capacity of the NMFS, extend an existing component file system or add new component file systems. You can also extend a file system with any unused disk volume, slice volume, stripe volume, or metavolume. Adding volume space to a file system adds the space to the metavolume on which it is built. So, when you extend a file system, the total size of its underlying metavolume is also extended.

When you extend a file system, extend it with the same volume type as the original file system. For example, if the metavolume underlying the file system is made up of stripe volumes, you should extend the file system with stripe volumes of the same size and type.

File systems created with AVM have associated storage pools. These file systems can be extended by size. View the file system configuration information on page 63 provides the information to determine whether a file system has an associated pool. Managing Volumes and File Systems with VNX AVM provides additional information on extending file systems created with AVM.

–  –  –

id = 18 name = ufs1 acl =0 in_use = True type = uxfs volume = mtv1, emtv2b profile = rw_servers= server_2 ro_servers= rw_vdms = ro_vdms = symm_devs = 002804000190-0034,002804000190-0035,002804000190-0036, 002804000190-0037,002804000190-0040,002804000190-0041,002804000190-0042, 002804000190-0043 disks = d3,d4,d5,d6,d15,d16,d17,d18 disk=d3 symm_dev=002804000190-0034 addr=c0t3l8-15-0 server=server_2 disk=d4 symm_dev=002804000190-0035 addr=c0t3l9-15-0 server=server_2 disk=d5 symm_dev=002804000190-0036 addr=c0t3l10-15-0 server=server_2 disk=d6 symm_dev=002804000190-0037 addr=c0t3l11-15-0 server=server_2 disk=d15 symm_dev=002804000190-0040 addr=c0t4l4-15-0 server=server_2 disk=d16 symm_dev=002804000190-0041 addr=c0t4l5-15-0 server=server_2 disk=d17 symm_dev=002804000190-0042 addr=c0t4l6-15-0 server=server_2 disk=d18 symm_dev=002804000190-0043 addr=c0t4l7-15-0 server=server_2

3. Check the size of the file system after extending it by using this command syntax:

$ nas_fs -size fs_name

–  –  –

Extend replicated file systems Replicated file systems can be manually extended when VNX Replicator is running. A slice volume is required to extend a source file system.

Before you extend a source file system:

◆ Use the nas_fs -size command to verify the current size of the file system. When you extend the source file system by using the -xtend option of the nas_fs command, the destination file system is extended first and then the source file system. This operation maintains identical file system sizes at the source and destination sites.

Extend replicated file systems 69Managing File Systems

◆ You can extend the size of the source (production) file system without impacting the destination file system by using the -xtend src_only option. The VNX Command Line Interface Reference for File provides a detailed synopsis of the commands associated with the VNX Replicator.

◆ Verify whether there is enough volume space to extend the source and destination file systems.

1. On the primary site, verify the current sizes of the source and destination file systems

by using this command syntax:

$ nas_fs -size fs_name

–  –  –

Adjust file system size threshold Because file system performance can degrade as its used space approaches 100 percent full, the VNX system monitors the amount of space in use in its file systems and triggers an event when the used space in a file system exceeds 90 percent. To get a notification of this event, you need to set up event logging (an SNMP trap or email notification) as described in Configuring Events and Notifications on VNX for File.

When the file system size threshold is exceeded, there are corrective actions you can take to manage the issue. You can either move files from the file system or extend the file system size. Either action helps reduce the percentage of used space to a percentage below the threshold.

For example, if you anticipate that the amount of used space in your file system might grow at a rapid rate, you can decrease the file system size threshold to a smaller percentage.

The tasks to adjust file system size threshold are:

◆ Adjust the file system size threshold for all file systems on page 72 ◆ Adjust the file system size threshold on a single Data Mover on page 73 Adjust the file system size threshold for all file systems

1. Change the size threshold for all file systems by using this command syntax:

$ server_param ALL -facility facility_name -modify param_name

-value new_value

–  –  –

Adjust the file system size threshold on a single Data Mover

1. Change the file system size threshold on a single Data Mover by using this command

syntax:

$ server_param movername -facility facility_name -modify param_name





-value new_value

–  –  –

Example:

To change the size threshold for all file systems on server_2, type:

$ server_param server_2 -facility file -modify fsSizeThreshold -value 85

2. Restart the Data Mover for the change to take effect by using this command syntax:

$ server_cpu movername -reboot now

–  –  –

Example:

To restart server_2 for the change to take effect, type:

$ server_cpu server_2 -reboot now Add an existing file system to an NMFS You can add an existing file system to an NMFS or remove a file system from an NMFS

without modifying or changing the file system:

1. Permanently unmount the file system from a Data Mover by using this command syntax:

$ server_umount movername -perm fs_name

–  –  –

Note: To permanently unmount a file system from a Data Mover by specifying the mount point path, use the -perm mount_point option instead of the -perm fs_name option.

–  –  –

Move an NMFS

You can move an NMFS from one Data Mover to another:

1. Permanently unmount each of the component file systems.

2. Permanently unmount the NMFS.

3. Mount the NMFS on the new Data Mover.

4. Mount each component file system on the NMFS on the new Data Mover.

–  –  –

Rename a file system Action

To rename a file system, use this command syntax:

$ nas_fs -rename old_name new_name

where:

old_name = existing name of the file system new_name = new name of the file system

Example:

To rename a file system ufs as ufs1, type:

$ nas_fs -rename ufs ufs1 Output id = 18 name = ufs1 acl = 0 in_use = False type = uxfs volume = mtv1 rw_servers= ro_servers= rw_vdms = ro_vdms = symm_devs = 002806000209-006,002806000209-007,002806000209-008,002806000209-009 disks = d3,d4,d5,d

–  –  –

Enhance file read/write performance The system includes internal mechanisms for enhancing read/write performance characteristics for certain types of files. The read prefetch mechanism is designed to optimize read operations of large files. It can speed up reading to 100 percent on large files. This mechanism is turned on by default on the server. It should be turned off only if the read access pattern for files in the file system primarily consists of small random accesses. The

tasks to enhance file read/write performance are:

◆ Turn off read prefetch for a specific file system on page 76 ◆ Turn off read prefetch for all file systems on a Data Mover on page 77 ◆ Enable uncached write mechanism on page 78 Turn off read prefetch for a specific file system Action

To turn off the read prefetch mechanism, use this command syntax:

$ server_mount movername -option options,noprefetch fs_name mount_point

where:

movername = name of the Data Mover options = specifies mount options, separated by commas

–  –  –

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

Example:

To turn off the read prefetch mechanism for ufs1, type:

$ server_mount server_3 -option rw,noprefetch ufs1 /ufs1

–  –  –

Turn off read prefetch for all file systems on a Data Mover

1. Turn off the read prefetch mechanism for all file systems on a Data Mover by using this

command syntax:

$ server_param movername -facility facility_name -modify prefetch -value 0

–  –  –

Example:

To turn off the prefetch mechanism for all file systems on server_2, type:

$ server_param server_2 -facility file -modify prefetch -value 0

2. Restart the Data Mover by using this command syntax:

$ server_cpu movername -reboot

–  –  –

Enable uncached write mechanism The write mechanisms are designed to improve performance for applications, such as databases, with many connections to a large file. These mechanisms can enhance database access through the NFS protocol by 30 percent or more. The mechanism is turned off by default. However, it can be turned on for a file system.

Action

To turn on the uncached write mechanism for a file system, use this command syntax:

$ server_mount movername -option options,uncached fs_name mount_point

where:

movername = name of the Data Mover options = specifies mount options, separated by commas

–  –  –

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

Example:

To turn on the uncached write mechanism for the file system ufs1, type:

$ server_mount server_3 -option rw,uncached ufs1 /ufs1

–  –  –

Unmount all file systems from a Data Mover Unexport NFS exports and unshare CIFS shares of the file systems before you unmount all file systems on the Data Mover, particularly when you are unmounting file systems permanently.

To change the way in which a file system is mounted, use the server_umount command to unmount the file system permanently from the Data Mover and then remount the file system.

You can also unmount component file systems from the NMFS.

The tasks to unmount all file systems are:

◆ Unmount all file systems temporarily on page 79 ◆ Unmount all file systems permanently on page 79

–  –  –

Unmount all file systems temporarily The -temp option of the server_umount command is the default and does not need to be specified as part of the command.

Action

To temporarily unmount all file systems on a Data Mover, use this command syntax:

$ server_umount movername -temp -all

where:

movername = name of the Data Mover

Example:

To temporarily unmount all file systems on server_2, type:

$ server_umount server_2 -temp -all Output server_2: done Unmount all file systems permanently Permanently unmounting all file systems from a Data Mover deletes the contents of the mount table. To reestablish client access to the file systems, you must rebuild the mount table by remounting each file system on the Data Mover.

Action

To permanently unmount all file systems on a Data Mover, use this command syntax:

$ server_umount movername -perm -all

where:

movername = name of the Data Mover Action

Example:

To permanently unmount all file systems on server_2, type:

$ server_umount server_2 -perm -all Output server_2: done

–  –  –

Delete a file system or NMFS To delete a file system and free its disk space, you must delete or disconnect all entities associated with the file system: all checkpoints, BCVs, slice volumes, stripe volumes, and metavolumes. After you delete or disconnect all the file system entities, the disk volumes that provide storage space to the file system become part of the available free space on the file server.

Deleting a file system deletes all data on the file system. If there are checkpoints associated with the file system, delete the checkpoints before deleting the file system. Deleting the file system does not delete data from BCVs associated with the file system. Using TimeFinder/FS, NearCopy, and FarCopy on VNX provides information on how to unmirror a BCV.

To delete an NMFS, first permanently unmount all component file systems mounted in the NMFS and then permanently unmount the NMFS. Use the nas_fs command -delete option to delete the file system. Unmount all file systems from a Data Mover on page 78 provides

additional information on unmounting file systems permanently:

1. Back up all the data you want to keep.

2. Check the file system configuration to determine if the file system has an associated storage pool (you will need this information in a later step) by using this command

syntax:

$ nas_fs -info fs_name

–  –  –

If the pool output line displays a value, the file system has an associated storage pool.

If the file system does not have an associated storage pool, proceed to step 3. If the file system has an associated storage pool, proceed to step 4.

–  –  –

Note: The Volume field contains the metavolume name. The Disks field lists the disks providing storage to the file system.

4. If the file system has associated checkpoints, permanently unmount and then delete the checkpoints and their associated volumes.

5. If the file system has associated BCVs, break the connection between (unmirror) the file system and its BCVs.

–  –  –

Using TimeFinder/FS, NearCopy, and FarCopy on VNX provides information on how to unmirror a BCV.

6. If the file system is an NFS-exported file system, permanently disable client access to the

file system by using this command syntax:

$ server_export movername -Protocol nfs -unexport -perm pathname

–  –  –

7. If the file system is a CIFS-exported file system, permanently disable client access to the

file system by using this command syntax:

$ server_export movername -Protocol cifs -unexport sharename

–  –  –

Note: To delete an NMFS, permanently unmount all component file systems in the NMFS.

9. Delete the file system or NMFS from the VNX system by using this command syntax:

$ nas_fs -delete fs_name

–  –  –

If the file system has an associated storage pool, as part of the file system delete operation, AVM deletes all underlying volumes and frees the space for use by other file systems.

If the file system has no associated storage pool, proceed to step 10. The volumes underlying the file system were created manually and must be manually deleted.

10. Delete the metavolume on which the file system was created by using this command

syntax:

$ nas_volume -delete volume_name

–  –  –

11. If the metavolume included stripe volumes, delete all stripe volumes associated with the



Pages:     | 1 |   ...   | 3 | 4 || 6 |


Similar works:

«WRITTEN STATEMENT BY HONORABLE CHARLES S. ABELL PRINCIPAL DEPUTY UNDER SECRETARY OF DEFENSE (PERSONNEL & READINESS) BEFORE THE SUBCOMMITTEE ON MILITARY PERSONNEL OF THE COMMITTEE ON ARMED SERVICES HOUSE OF REPRESENTATIVES ON APRIL 7, 2005 Not for Publication until Released By Committee on Armed Services U.S. House of Representatives 1 of 24 Mr. Chairman and members of this distinguished Subcommittee, thank you for the opportunity to be here today. The Secretary of Defense is firmly committed to...»

«425 OECD/OCDE Adopted: 17th December 2001 OECD GUIDELINE FOR TESTING OF CHEMICALS Acute Oral Toxicity – Up-and-Down Procedure INTRODUCTION 1. OECD guidelines for the Testing of Chemicals are periodically reviewed in the light of scientific progress or changing assessment practices. The concept of the up-and-down testing approach was first described by Dixon and Mood (1)(2)(3)(4). In 1985, Bruce proposed to use an up-and-down procedure (UDP) for the determination of acute toxicity of chemicals...»

«White Lies and Whited Sepulchres in Conrad's Heart of Darkness Philip V. Allingham, Contributing Editor, Victorian Web; Faculty of Education, Lakehead University, Thunder Bay, Ontario In his novella Heart of Darkness (1899), Joseph Conrad through his principal narrator, Marlow, reflects upon the evils of the human condition as he has experienced it in Africa and Europe. Seen from the perspective of Conrad's nameless, objective persona, the evils that Marlow encountered on the expedition to the...»

«State of Illinois 2015-2019 Consolidated Plan – PENDING HUD APPROVAL Consolidated Plan ILLINOIS 1 OMB Control No: 2506-0117 (exp. 07/31/2015) State of Illinois 2015-2019 Consolidated Plan – PENDING HUD APPROVAL Executive Summary ES-05 Executive Summary 91.300(c), 91.320(b) 1. Introduction The U.S. Department of Housing and Urban Development (HUD) requires State and local grantees of the four formula grant programs, namely the Community Development Block Grant (CDBG) the HOME Program, the...»

«Engendered Penalties: Transgender and Transsexual People’s Experiences of Inequality and Discrimination Authors: Stephen Whittle, Lewis Turner and Maryam Al-Alami Contributors: Em Rundall and Ben Thom February 2007 A Research Project and Report Commissioned by the Equalities Review. The views expressed in this report are those of the authors, not necessarily those of the Equalities Review. © Crown Copyright 2007 Product Code 06 LD 04440/o This publication is one of a series of reports...»

«Model–Based Testing of Cryptographic Protocols Dean Rosenzweig1,2, Davor Runje2, and Wolfram Schulte1 Microsoft Research schulte@microsoft.com University of Zagreb dean@math.hr, davor.runje@fsb.hr Abstract. Modeling is a popular way of representing the behavior of a system. A very useful type of model in computing is an Abstract state machine which describes transitions over first order structures. The general purpose model-based testing tool SpecExplorer (used within Microsoft, also...»

«Zakład Chemii Analitycznej Wydziału Technologii Chemicznej Politechniki Poznańskiej Komisja Analizy Nieorganicznej Komitetu Chemii Analitycznej PAN NOWOCZESNE METODY PRZYGOTOWANIA PRÓBEK I OZNACZANIA ŚLADOWYCH ILOŚCI PIERWIASTKÓW Modern Methods of Sample Preparation and Determination of Trace Elements Materiały XV Poznańskiego Konwersatorium Analitycznego Poznań, 20-21 kwietnia 2006 r. Materiały Szkoły Naukowej MATERIAŁY ODNIESIENIA a WZORCE ANALITYCZNE WORKSHOP „REFERENCE...»

«CASE NO. 08-1037 IN THE UNITED STATES COURT OF APPEALS FOR THE FOURTH CIRCUIT UNITED STATES SECURITIES AND EXCHANGE COMMISSION, Plaintiffs-Appellees, v.PIRATE INVESTOR LLC AND FRANK PORTER STANSBERRY, Defendants. APPEAL FROM A FINAL JUDGMENT OF THE UNITED STATES DISTRICT COURT FOR THE DISTRICT OF MARYLAND BRIEF OF APPELLANTS-DEFENDANTS PIRATE INVESTOR LLC AND FRANK PORTER STANSBERRY FOR REVERSAL OF THE DISTRICT COURT’S DECISION Bruce W. Sanford Matthew J. Turner Lee T. Ellis, Jr. 14 West...»

«Statement of David S. Mao The Acting Librarian of Congress Before the Subcommittee on Legislative Branch Appropriations U.S. House of Representatives Fiscal 2017 Budget Request March 2, 2016 Mr. Chairman, Ranking Member Wasserman Schultz, and Members of the Subcommittee: Thank you for the privilege to provide testimony in support of the mission and fiscal 2017 budget request of the Library of Congress. The mission of the Library of Congress is to provide the Congress and the American people...»

«RESEARCH NOTE No Longer Unmeasurable? 10.1177/0899764004269146 Sowa et al. No Longer Unmeasurable? A Multidimensional Integrated Model of Nonprofit Organizational Effectiveness Jessica E. Sowa University of South Carolina Sally Coleman Selden Lynchburg College Jodi R. Sandfort University of Minnesota Few topics in nonprofit research and practice have received greater attention in recent years than organizational effectiveness. In spite of this intellectual interest, little consensus has...»

«Committee on Payments and Market Infrastructures Board of the International Organization of Securities Commissions Principles for financial market infrastructures: Assessment methodology for the oversight expectations applicable to critical service providers December 2014 This publication is available on the BIS website (www.bis.org) and the IOSCO website (www.iosco.org). © Bank for International Settlements and International Organization of Securities Commissions 2014. All rights reserved....»

«The Critic as Host Author(s): J. Hillis Miller Source: Critical Inquiry, Vol. 3, No. 3, (Spring, 1977), pp. 439-447 Published by: The University of Chicago Press Stable URL: http://www.jstor.org/stable/1342933 Accessed: 01/08/2008 08:58 Your use of the JSTOR archive indicates your acceptance of JSTOR's Terms and Conditions of Use, available at http://www.jstor.org/page/info/about/policies/terms.jsp. JSTOR's Terms and Conditions of Use provides, in part, that unless you have obtained prior...»





 
<<  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.