- Table of Contents
-
- 01-Fundamentals Configuration Guide
- 00-Preface
- 01-CLI configuration
- 02-RBAC configuration
- 03-Login management configuration
- 04-License management
- 05-Device management configuration
- 06-FTP and TFTP configuration
- 07-File system management configuration
- 08-Configuration file management configuration
- 09-Software upgrade configuration
- 10-Tcl configuration
- 11-Python configuration
- 12-MAC learning through a Layer 3 device configuration
- Related Documents
-
Title | Size | Download |
---|---|---|
07-File system management configuration | 94.26 KB |
Contents
Storage media and file systems
Specifying a directory name or file name
Restrictions and guidelines: File system management
Managing storage media and file systems
Managing files and directories
Setting the operation mode for files and directories
Displaying file and directory information
Displaying the contents of a text file
Displaying the working directory
Changing the working directory
Archiving files and directories
Extracting files and directories
Displaying processes that are using a file system, directory, or file
Managing file systems
This chapter describes how to manage file systems.
About file system management
Storage media and file systems
The device supports only one storage medium, the flash memory. The flash memory has one file system.
Storage medium and file system naming conventions
The file system on the flash memory has the same name as the flash memory. The name has the following parts:
· Storage medium type flash.
· Colon (:).
IMPORTANT: File system names are case sensitive and must be entered in lower case. |
File system location
(In standalone mode.) To identify a file system on the active MPU, you do not need to specify the file system location. To identify a file system on the standby MPU, you must specify the file system location in the slotn# format. The n argument represents the slot number of a card. For example, the location is slot16# for a file system that resides on the card in slot 16.
(In IRF mode.) To identify a file system on the global active MPU, you do not need to specify the file system location. To identify a file system on a global standby MPU, you must specify the file system location in the chassism#slotn# format. The m argument represents the IRF member ID of the member device. The n argument represents the slot number of a card. For example, the location is chassis2#slot16# for a file system that resides on the MPU in slot 16 of member device 2.
IMPORTANT: The file system location string is case sensitive and must be entered in lower case. |
Default file system
You are working with the default file system by default after you log in. To specify a file or directory on the default file system, you do not need to specify the file system name. For example, you do not need to specify any location information if you want to save the running configuration to the root directory of the default file system.
To change the default file system, use the BootWare or Boot ROM menu. For more information, see the software release notes.
Directories
Directories in a file system are structured in a tree form.
Root directory
The root directory is represented by a forwarding slash (/). For example, flash:/ represents the root directory of the flash memory.
Working directory
The working directory is also called the current directory.
Directory naming conventions
When you specify a name for a directory, follow these conventions:
· A directory name can contain letters, digits, and special characters except for asterisks (*), vertical bars (|), forward slashes (/), backward slashes (\), question marks (?), left angle brackets (<), right angle brackets (>), quotation marks ("), and colons (:).
· A directory whose name starts with a dot character (.) is a hidden directory. To prevent the system from hiding a directory, make sure the directory name does not start with a dot character.
Commonly used directories
The device has some factory-default directories. The system automatically creates directories during operation. These directories include:
· diagfile—Stores diagnostic information files.
· license—Stores license files.
· logfile—Stores log files.
· seclog—Stores security log files.
· versionInfo—Stores software version information files.
Files
File naming conventions
When you specify a name for a file, follow these conventions:
· A file name can contain letters, digits, and special characters except for asterisks (*), vertical bars (|), forward slashes (/), backward slashes (\), question marks (?), left angle brackets (<), right angle brackets (>), quotation marks ("), and colons (:).
· A file whose name starts with a dot character (.) is a hidden file. To prevent the system from hiding a file, make sure the file name does not start with a dot character.
Common file types
The device has some factory-default files and might create some files automatically during operation. The types of these files include:
· .ipe file—Compressed software image package file.
· .bin file—Software image file.
· .cfg file—Configuration file.
· .mdb file—Binary configuration file.
· .log file—Log file.
Specifying a directory name or file name
Specifying a directory name
To specify a directory, you can use the absolute path or a relative path. For example, the working directory is flash:/. To specify the test2 directory in Figure 1, you can use the following methods:
· flash:/test/test1/test2 (absolute path)
· flash:/test/test1/test2/ (absolute path)
· test/test1/test2 (relative path)
· test/test1/test2/ (relative path)
Figure 1 Sample directory hierarchy
Specifying a file name
To specify a file, use the following methods:
· Enter the absolute path of the file and the file name in the format of filesystem/directory1/directory2/…/directoryn/filename, where directoryn is the directory in which the file resides.
· Enter the relative path of the file and the file name.
For example, the working directory is flash:/. The samplefile.cfg file is in the test2 directory shown in Figure 1. To specify the file, you can use the following methods:
· flash:/test/test1/test2/samplefile.cfg
· test/test1/test2/samplefile.cfg
Restrictions and guidelines: File system management
(In standalone mode.) To avoid file system corruption, do not perform the following tasks during file system management:
· Install or remove storage media.
· Install or remove cards.
· Perform an active/standby switchover.
(In IRF mode.) To avoid file system corruption, do not perform the following tasks during file system management:
· Install or remove storage media.
· Install or remove cards.
· Perform a switchover between the global active MPU and a global standby MPU.
You cannot access a file system that is being formatted or repaired.
Before managing file systems, directories, and files, make sure you know the possible impact.
Managing storage media and file systems
Formatting a file system
Restrictions and guidelines
You can format a file system only when no other users are accessing the file system.
Procedure
To format a file system, execute the following command in user view:
format filesystem [ ext4 | vfat ]
CAUTION: Formatting a file system permanently deletes all files and directories in the file system. You cannot restore the deleted files or directories. If a startup configuration file exists in the file system, back up the file if necessary. |
This command is supported only on the default context.
Repairing a file system
Restrictions and guidelines
If part of a file system is inaccessible, use this task to examine and repair the file system.
You can repair a file system only when no other users are accessing the file system.
Procedure
To repair a file system, execute the following command in user view:
fixdisk filesystem
This command is supported only on the default context.
Managing files and directories
Setting the operation mode for files and directories
About this task
The device supports the following operation modes:
· alert—The system prompts for confirmation when your operation might cause problems such as file corruption or data loss. This mode provides an opportunity for you to cancel a disruptive operation.
· quiet—The system does not prompt for confirmation when you perform a file or directory operation except the recycle bin emptying operation.
Procedure
1. Enter system view.
system-view
2. Set the operation mode for files and directories.
file prompt { alert | quiet }
The default mode is alert.
Displaying file and directory information
To display file and directory information, execute the following command in user view:
dir [ /all ] [ file | directory | /all-filesystems ]
If multiple users perform file operations (for example, creating or deleting files or directories) at the same time, the output from this command might be incorrect.
Displaying the contents of a text file
To display the contents of a text file, execute the following command in user view:
more file
Displaying the working directory
To display the working directory, execute the following command in user view:
pwd
Changing the working directory
About this task
(In standalone mode.) The default working directory is the root directory of the default file system on the active MPU.
(In IRF mode.) The default working directory is the root directory of the default file system on the global active MPU.
Procedure
To change the working directory, execute the following command in user view:
cd { directory | .. }
Creating a directory
To create a directory, execute the following command in user view:
mkdir directory
Renaming a file or directory
To rename a file or directory, execute the following command in user view:
rename { source-file | source-directory } { dest-file | dest-directory }
Copying a file
To copy a file, execute the command in user view.
copy source-file { dest-file | dest-directory } [ vpn-instance vpn-instance-name ] [ source interface interface-type interface-number ]
Moving a file
To move a file, execute the following command in user view:
move source-file { dest-file | dest-directory }
Deleting and restoring files
About this task
You can delete a file permanently or move it to the recycle bin of the file system. A file moved to the recycle bin can be restored, but a permanently deleted file cannot.
Restrictions and guidelines
Files in the recycle bin occupy storage space. To release the occupied storage space, delete files from the recycle bin.
To delete files from the recycle bin, use the reset recycle-bin command. If you use the delete command, the recycle bin might not be able to operate correctly.
To display files in a recycle bin, use one of the following methods:
· Access the root directory of the file system and execute the dir /all .trash command.
· Access the recycle bin directory of the file system and execute the dir command.
Deleting a file
To delete a file, execute one of the following commands in user view:
· Delete a file by moving it to the recycle bin.
delete file
CAUTION: Using the delete file command on the default context to delete a file on a non-default context permanently deletes that file instead of moving it to the recycle bin. |
· Delete a file permanently.
delete /unreserved file
CAUTION: The delete /unreserved file command deletes a file permanently. The file cannot be restored. |
· Delete files from the recycle bin.
reset recycle-bin [ /force ]
CAUTION: The files in a recycle bin can be restored by using the undelete command. If you delete a file from the recycle bin, that file cannot be restored. Before you delete files from a recycle bin, make sure the files are no longer in use. |
Restoring a file
To restore a file from the recycle bin, execute the following command in user view:
undelete file
Deleting a directory
To delete a directory, execute the following command in user view:
rmdir directory
CAUTION: To delete a directory, you must first delete all files and subdirectories in the directory permanently or move them to the recycle bin. If you move them to the recycle bin, executing the rmdir command to delete the directory will delete them permanently. Before you use the rmdir command to delete a directory, you must make sure the directory and its files and subdirectories are no longer in use. |
Archiving files and directories
About this task
You can archive files and directories to a single file for purposes such as file backup. The original files and directories still exist.
When you archive files and directories, you can choose to compress the archive files so the archive files use less storage space.
Procedure
To archive files and directories, execute the following command in user view:
tar create [ gz ] archive-file dest-file [ verbose ] source { source-file | source-directory }&<1-5>
Extracting files and directories
About this task
Use this feature to extract files and directories from archive files.
Restrictions and guidelines
To specify the screen keyword for the tar extract command, first use the tar list command to identify the types of the archived files. As a best practice, specify the keyword only if all archived files are text files. Displaying the content of an archived non-text file that contains terminal control characters might result in garbled characters and even cause the terminal unable to operate correctly. To use the terminal again, you must close the current connection and log in to the device again.
Procedure
To extract files and directories, execute the following commands in user view:
1. (Optional.) Display archived files and directories.
tar list archive-file file
2. Extract files and directories.
tar extract archive-file file [ verbose ] [ screen | to directory ]
Compressing a file
To compress a file, execute the following command in user view:
gzip file
Decompressing a file
To decompress a file, execute the following command in user view:
gunzip file
Calculating the file digest
About this task
File digests are used to verify file integrity.
Procedure
To calculate the digest of a file, execute one of the following commands in user view:
· Use the SHA-256 algorithm.
sha256sum file
· Use the MD5 algorithm.
md5sum file
Displaying processes that are using a file system, directory, or file
About this task
Execute this command if you fail to execute a command such as fixdisk, format, rmdir, rename, delete, or copy command for a file system, directory, or file. View the command output to identify whether a process is using the file system, directory, or file.
Procedure
To display processes that are using a file system, directory, or file, execute the following command in user view:
fuser { directory | file | filesystem }