Configuration files must be edited from clients
Data ONTAP does not include an editor. You cannot edit files by using the system console or by establishing a Telnet session to the storage system. You must use an editor from an NFS client or a CIFS client to edit system configuration files.
Enabling an NFS client to edit configuration files
For an NFS client to edit configuration files, the client must be authorized to access the root file system.
If the NFS client was specified as the administration host during setup or added as an administration host after setup was completed, it is already authorized to access the root file system.
If the NFS client is not specified as an administration host, complete the following steps to authorize access to the root file system.
Step Action
1 Mount the storage system root volume on the administration host.
2 From the administration host, edit the /etc/exports file on the root volume to grant root permission to the client.
3 Use the storage system console, a Telnet client, or the rsh command to issue the following command to the system:
exportfs
4 Mount the storage system root volume on the client.
Editing configuration files from an NFS client
To edit configuration files from an NFS client, complete the following step.
Step Action
1 From the client, use a text editor to edit the files in the /etc directory.
Editing configuration files from a CIFS client
After setup finished, the default /etc/passwd and /etc/group files on the root volume were set up to enable you to share files on the storage system as Administrator. The system root directory was shared automatically as C$. The administrator has read, write, and execute rights to the share.
Note
The C$ share is a "hidden" share; you can get to it only by specifying the path manually (for example, as \\filer\C$), rather than accessing it through the Network Neighborhood icon.
To edit configuration files from a CIFS client, complete the following steps.
Step Action
1 Connect from a CIFS client to the storage system as Administrator.
2 Display the contents of the system's C$ share, and select a file to edit.
Configuration files that require a carriage return after the last entry
Data ONTAP requires that the following configuration files be terminated with a carriage return:
• /etc/passwd
• /etc/group
• /etc/netgroup
• /etc/shadow
When you edit these files, be sure to insert a carriage return after the last entry.
Configuration files that should not be edited
When you configure Data ONTAP, it creates some files that you should not edit. The following configuration files should not be edited.
• cifsconfig.cfg
• cifssec.cfg
• lclgroups.cfg
• filesid.cfg
• sysconfigtab
• registry.*
Accessing the default directories on the storage system
Accessing the /etc directory from an NFS client
To access the /etc directory from an NFS client, complete the following steps.
Step Action
1 Mount the following path:
filer:/vol/vol0
filer is the name of your storage system.
Result:
You have access to the system root directory.
2 Change directories to the /etc directory, using the following command:
cd etc
Accessing the /etc directory from a CIFS client
To access the root directory from a CIFS client, complete the following steps.
Step Action
1 Map a drive to the following path:
\\filer\C$
filer is the name of your system.
Result:
You have access to the system root directory.
2 Double-click the /etc folder.
Accessing the home directory from an NFS client
To access the home directory from an NFS client, complete the following step.
Step Action
1 Mount the following path:
filer:/vol/vol0/home
filer is the name of your system.
Accessing the home directory from a CIFS client
To access the home directory from a CIFS client, complete the following step.
Step Action
1 Map a drive to the following path:
\\filer\HOME
filer is the name of your system.
Note
You can also browse the Network Neighborhood to locate the system and the HOME directory.
Accessing log files using HTTP
To access your log files using HTTP, complete the following step.
Step Action
1 Point your browser to the following location:
http://
system_name is the name of your system.
CopyrigHow to move or rename the root volume on a filer
KB ID: 1010097 Version: 3.0 Published date: 11/19/2010
Description
• Change, rename or move the root volume
• Error message: servlet not initialized
• Switching the root volume from a SCSI shelf to a volume in FCAL
• Move the system files to another volume
• Decrease the RAID size of an existing root volume
Procedure
Moving the root volume
To move the root volume by creating a new volume, follow these steps:
1. Create a new volume for the new root volume (see the vol Manual Page for more options).
Traditional Volumes
1. Enter the following command to create a new traditional volume:
vol create new_volname number_of_disks
2. After the new volume is created, this message will be displayed - Bootblock update complete.
Do not run the download command afterwards, as it is unnecessary.
FlexVols
1. For flexible volumes, the following command creates a new volume:
vol create flex_volname aggrname size
2. To create a new 5GB FlexVol, inside of an aggregate called "aggr1," enter the following command:
vol create new_root aggr1 5g
Creating a FlexVol results in a message similar to the following:
Creation of volume 'new_root' with size 5g on containing aggregate 'aggr1' has completed.
Note:
Please refer to the following document for recommended root volume sizes:
Root volume size and space guarantee requirements
As minimum root size requirements may differ across versions of Data ONTAP. Refer to your documentation for the correct requirements.
2. Copy the entire /etc directory from the current root volume to the new root volume. If other data exists on the old root volume, also copy that data to the new root volume. If necessary, increase the size of the new root volume by adding disks to the new volume using the vol add command.
Note: Other data migration utilities such as SCOPY, vol copy, ndmpcopy, and so on, may be used to migrate large amounts of data to the new root volume. Additionally, snapvaults should be disabled during the migration process (See Bug 268338)
3. If desired, the vol rename command may be used to rename the old and new root volumes.
4. Flag the new root volume as the root volume with the following command:
vol options new_root root
For clusters, see the section Notes on clustered storage systems.
5. Verify that the shares and exports are updated accordingly, by running the following commands:
cifs shares
exportfs
6. Reboot the filer
To move the root volume without creating a new volume, follow these steps:
1. Validate the current root volume (usually vol0) and the new root volume:
vol status
2. Ensure that the ndmpd daemon is turned on using the ndmpd on command on the filer.
3. Copy the entire /etc directory from the current root volume to the new root volume
ndmpcopy /etc /vol/new_rootvol/etc
4. Flag the new root volume as the root volume:
vol options new_rootvol root
For clusters, see the section Notes on clustered storage systems.
5. If desired, rename the old and new root volume. The following command renames the volume :
vol rename
6. Verify that the shares and exports are updated accordingly, by running the following commands:
cifs shares
exportfs
7. Reboot the filer
8. Verify the new root volume settings:
vol status
An example output is shown below. For this example, the root is vol0. The new root volume will be vol2.
filer> vol status
Volume State Status Options
vol1 online raid_dp create_ucode=on
vol0 online raid4 root, create_ucode=on <<<<=== vol2 online raid4 raidsize=4, create_ucode=on filer> ndmpcopy /etc /vol/vol2/etc
Ndmpcopy: Starting copy [ 2 ] ...
Ndmpcopy: filer: Notify: Connection established
Ndmpcopy: filer: Notify: Connection established
Ndmpcopy: filer: Connect: Authentication successful
Ndmpcopy: filer: Connect: Authentication successful
Ndmpcopy: filer: Log: DUMP: creating "/vol/vol0/../snapshot_for_backup.4" snapshot.
Ndmpcopy: filer: Log: DUMP: Using subtree dump
Ndmpcopy: filer: Log: DUMP: Date of this level 0 dump: Mon Mar 7 10:18:18 2005.
Ndmpcopy: filer: Log: DUMP: Date of last level 0 dump: the epoch.
Ndmpcopy: filer: Log: DUMP: Dumping /etc to NDMP connection
Ndmpcopy: filer: Log: DUMP: mapping (Pass I)[regular files]
Ndmpcopy: filer: Log: DUMP: mapping (Pass II)[directories]
Ndmpcopy: filer: Log: DUMP: estimated 365193 KB.
Ndmpcopy: filer: Log: DUMP: dumping (Pass III) [directories]
Ndmpcopy: filer: Log: RESTORE: Mon Mar 7 10:18:25 2005: Begin level 0 restore
Ndmpcopy: filer: Log: RESTORE: Mon Mar 7 10:18:25 2005: Reading directories from the backup
Ndmpcopy: filer: Log: DUMP: dumping (Pass IV) [regular files]
Ndmpcopy: filer: Log: RESTORE: Mon Mar 7 10:18:28 2005: Creating files and directories.
Ndmpcopy: filer: Log: RESTORE: Mon Mar 7 10:18:32 2005: Writing data to files.
Ndmpcopy: filer: Log: DUMP: dumping (Pass V) [ACLs]
Ndmpcopy: filer: Log: RESTORE: Mon Mar 7 10:19:06 2005: Restoring NT ACLs.
Ndmpcopy: filer: Log: RESTORE: RESTORE IS DONE
Ndmpcopy: filer: Notify: restore successful
Ndmpcopy: filer: Log: DUMP: 365298 KB
Ndmpcopy: filer: Log: DUMP: DUMP IS DONE
Ndmpcopy: filer: Log: DUMP: Deleting "/vol/vol0/../snapshot_for_backup.4" snapshot.
Ndmpcopy: filer: Notify: dump successful
Ndmpcopy: Transfer successful [ 49 seconds ]
Ndmpcopy: Done
filer> vol options vol2 root
Mon Mar 7 10:21:24 PST [filer: fmmbx_instanceWorke:info]: Disk 8a.37 removed
from primary mailbox set
Mon Mar 7 10:21:24 PST [filer: fmmbx_instanceWorke:info]: Disk 8a.36 removed
from primary mailbox set
Mon Mar 7 10:21:24 PST [filer: fmmbx_instanceWorke:info]: Disk 8a.35 is a pr
imary mailbox disk
volume vol2 will become root volume at the next boot.
filer> reboot
After rebooting, type the following:
filer> vol status
Volume State Status Options
vol1 online raid_dp create_ucode=on
vol0 online raid4 create_ucode=on
vol2 online raid4 root, raidsize=4, create_ucode=on
This shows vol2 as the new root volume.
Renaming the root volume
To rename the root volume, use the following syntax:
vol rename
When renaming the root volume, the CIFS shares and the /etc/exports file are automatically updated. Run the cifs shares and exportfs commands to verify that the rename changes have been accepted by the storage system.
Notes on clustered storage systems
With clustered storage, it is possible to issue a takeover in place of a reboot when setting a new root volume. As with all cluster takeovers, this may be disruptive depending on the protocols your storage system is serving (i.e. CIFS, FCP, iSCSI, and so on.) and associated settings.
To perform a takeover and giveback to change your root volume, complete the following steps:
1. Filer1> cf takeover
2. Filer1(takeover)> partner
3. Filer2/Filer1*> vol options new_root root
Necessary system files are not present on the volume 'newroot'. It is recommended that you copy system files from the current root volume to the new root volume using the steps outlined in System Administration Guide, chapter 'Understanding Root Volumes', section 'Changing Root Volume'. If you do not, after reboot, the appliance will enter setup and service will be disrupted until all the setup steps (including a reinstall of system software) have been completed.
Continue with set root operation (y/n)? y Volume 'new_root' will become root at the next boot.
4. Filer2/Filer1*> partner
5. Filer1(takeover)> cf giveback
Related links
1010130: How to remove disks from the root volume
Data ONTAP System Administration Guide > Understanding the Root Volume
________________________________________
If you need further assistance, post a question in the NetApp Support Community.
Obsolete when printed.
Search Knowledgebase
English
Search
My Recent Searches
how to reduce datastore of vmware
operation manager
simulator
sim
325.8g
how to decrease size of a lun ?
how to move lun
snapmirror break
how to resize lun
how to do switch zoning
Welcome senthilkumar kumar
• Logout
• ________________________________________
• My Profile
• ________________________________________
• My Subscriptions
• My Recommendations
Contact Us | How To Buy | Feedback | Careers | Subscriptions | Privacy Policy | © 2010 NetApp
ht © 1994-2006, Network Appliance, Inc. All rights reserved.
Part No. 210-01284_A0
File: 4defvol5.htm
No comments:
Post a Comment