Appendix C - Kernel Configuration Utility
With this release, Banyan provides you with the ability to modify the configuration of the software on your Banyan server by adding or removing device drivers from the operating system's kernel. This allows you to add specific drivers that you need to configure new devices and to reduce the size of the kernel by removing drivers that you do not need.
You can also choose to save a copy of the current kernel to diskette. A complete system backup does not save the entire kernel, but only those files that represent modifications to the default configuration that exists on the Banyan release media. Thus, you no longer need to reload server software to restore the kernel.
You can back up and restore the kernel configuration information from the server console's Kernel Configuration Utility. When you save a kernel to diskette, the entire kernel, as built on the server, is saved to the diskette. When you restore this copy of the kernel, it overwrites whatever kernel is currently on the server's fixed disk.
Kernel Configuration Utility Main Menu
From the Kernel Configuration Main menu, you can perform the following actions:
To View the Kernel Configuration Main Menu
1. From the Operator Menu, choose, System Maintenance. The System Maintenance menu appears.
2. Choose Configure/Diagnose Server. The BANYAN Server Configuration menu appears.
3. Choose Configure Kernel. You are prompted to use the default kernel or specify a customized kernel.
4. Enter C to specify a customized kernel. The Kernel Configuration Main Menu appears. Refer to the other section in this appendix for information on each of the menu items.
Adding and Removing Device Drivers from the Kernel
When you first install the server software, the standard Banyan adapter drivers are built into the kernel. Depending on your needs, you may want to add new drivers or remove drivers from the kernel.
You can view a list of the server's available drivers and installed drivers.
Available drivers are drivers that are loaded onto your system. If you want to build third-party drivers into the kernel, you must load the third-party driver package onto the system. See "To Load a Driver Package" later in this appendix for instructions on loading third-party drivers.
Installed drivers are drivers that are configured into the kernel. Installed drivers are only included in the kernel and available for use after the kernel has been built. When you first install the server software, the Banyan adapter drivers are automatically installed. You may remove any of these drivers by configuring the kernel and removing the drivers. See "To Remove a Driver" later in this appendix for instructions. To include third-party drivers in the kernel, you must first load them onto the system, and then rebuild the kernel.
To View Available Drivers
1. From the Kernel Configuration Main menu, choose List available drivers. The List Available Drivers screen appears.
This screen contains a list of all the Banyan and third-party drivers loaded onto the system. The drivers that are already installed in the kernel are marked with an asterisk (*).
2. When you finish viewing the drivers, press ESC to return to the Kernel Configuration Main menu.
To View Installed Drivers
1. From the Kernel Configuration Main menu, choose List installed drivers. The List Installed Drivers screen appears.
This screen contains a list of all the Banyan and third-party drivers that are installed in the kernel.
2. When you are finished viewing the drivers, press ESC to return to the Kernel Configuration Main menu.
To build third-party drivers into your server's kernel, you must load the driver package provided by the device manufacturer. A driver package may contain more than one device driver.
1. From the Kernel Configuration Main menu, choose Load driver package. The following message appears:
Load package diskette. Press <Enter> when ready.
2. Insert a driver package diskette into drive A and press ENTER. The drivers are loaded onto the system and are automatically installed in the kernel. To use the new third-party drivers, you must rebuild the kernel.
Note: If a driver package with the same name and revision number is already installed, the system may ask if you want to overwrite the existing driver package. To load the new driver package, follow the on-screen instructions.
3. Press ESC to return to the Kernel Configuration Main menu.
To build a customized kernel, you must first install (add) the drivers you want built into the kernel; if you have an existing kernel, you may also want to remove some drivers that are currently in the kernel.
Any changes you make to the kernel, whether adding or removing drivers, are not final until you build the kernel. For example, to include a specific driver in your server's kernel, you must install the driver and then build the kernel - the installed drivers are not accessible to the system until they are built into the kernel.
Note: If you configure a customized kernel, make sure that you include the driver for your server's boot device in the configuration.
If you want to build a third-party driver into your server's kernel, you must load the driver from diskette. Refer to "To Load a Driver Package" earlier in this appendix for instructions on loading a third-party driver.
To Add a Driver
1. From the Kernel Configuration Main menu, choose Configure Kernel. The Configure Kernel menu appears.
2. Choose Add driver. The Add Drivers screen appears.
This screen shows all the drivers that are available but not installed in the kernel. You can view additional drivers by pressing PG-DN and PG-UP, or using the arrow keys.
3. Enter the number of the driver you want to add.
4. When you are done adding drivers, do one of the following:
- Press ESC to return to the Configure Kernel menu.
- Choose Discard changes to revert to the previous kernel configuration.
5. Choose Return to previous menu. The Kernel Configuration Main menu appears.
To access drivers that you have installed, you must rebuild the server's kernel. See "To Build the Kernel" later in this appendix.
1. From the Kernel Configuration Main menu, choose Configure Kernel. The Configure Kernel menu appears.
2. Choose Remove driver. The Remove Drivers screen appears.
This screen lists all the drivers currently installed in the kernel. You can view additional drivers by pressing PG-DN and PG-UP or using the arrow keys.
3. Enter the number of the driver you want to remove from the kernel.
Note: When you remove a driver, the driver is not deleted from the disk but deconfigured (it is still loaded on the system).
4. When you finish removing drivers, do one of the following:
- Press ESC to return to the Configure Kernel menu.
- Choose Discard changes to revert to the previous kernel configuration.
5. Choose Return to previous menu. The Kernel Configuration Main menu appears.
You must rebuild the server's kernel to actually remove drivers. See "To Build the Kernel," which follows.
Caution: Do not rebuild a kernel after restoring it from diskette. If you are re-installing software and have not yet restored a backup, the configuration files currently on the server may differ from those that you used to build the kernel on the diskette. Rebuilding the kernel from these configuration files causes the kernel you restored from diskette to be overwritten.
1. From the Kernel Configuration Main menu, choose Build kernel. The Build Kernel menu appears.
2. Choose the appropriate menu option:
- To build the kernel with the standard default configuration (includes all the Banyan drivers), choose Build Banyan default configuration.
- To build the kernel with any changes you made, choose Build current configuration. If you made changes to the fixed disk drivers in the kernel, you may need to choose a driver to control the boot device. Refer to the Server Installation Guide for more information on building a new kernel that contains third-party fixed-disk drivers.
Note: The boot adapter you choose must already be set to the system's primary I/O address (1F0 or 3510) or to the lowest or only BIOS address in the system. If the system and the Banyan software have different boot drive designations, there will be an error when the server reboots.
3. The system prepares to build the new kernel. You are prompted to save a copy of the existing kernel before the new kernel is built. Do one of the following:
- Enter Y to save the existing kernel. The existing kernel is saved as unix.orig. The existing unix.orig is overwritten.
- Enter N if you do not want to save the existing kernel. The kernel rebuilds.
Continue with step 4.
4. After the rebuild process completes, you are prompted to save the new kernel to diskette.
5. Enter N. The Build Kernel menu appears. Choose Return to previous menu.
Saving the Current Kernel Configuration
The kernel configuration changes whenever you add or remove a device driver. Save the kernel configuration each time you modify the kernel. Saving the kernel configuration can shorten the time required to reload server information, because you avoid having to manually enter server information.
To Save the Current Kernel Configuration to Diskette
1. From the Kernel Configuration Main Menu, choose Build Kernel. The Build Kernel menu appears.
2. Choose Build current configuration. Messages appear indicating that the kernel is being rebuilt. When the kernel build is complete, you are prompted to save the new kernel on diskette.
3. Enter Y. You are prompted to insert a diskette.
4. Insert a blank diskette into the drive.
5. Press ENTER. The following messages appear:
Compressing kernel file.
Copying kernel to diskette.
n blocks
Kernel has been copied successfully. Press <Enter> to continue.6. Remove the diskette from the drive and label it with the date, the name of the server, and the words "Kernel Configuration Backup." Store the backup in a safe place.
7. Press ENTER. The Build Kernel menu appears.
8. Choose Return to previous menu. The Kernel Configuration Main Menu appears.
9. Choose Exit. The BANYAN Server Configuration menu appears.
10. Choose Return to System Maintenance Menu.
Restoring the Kernel Configuration
If you customized the kernel by adding or removing drivers, and kernel files are modified or corrupted at a later time, you can restore a kernel configuration that you previously saved to diskette.
Caution: Do not rebuild a kernel after restoring it from diskette. Restoring the kernel from diskette overwrites the files on the server with the files on the diskette. The files on the server that are used for building the kernel may differ from those that you used to build the kernel on the diskette. Rebuilding the kernel from current files causes the kernel you restored from diskette to be overwritten.
To Restore the Kernel Configuration from Diskette
1. From the The Kernel Configuration Main Menu, choose Restore kernel from diskette. You are prompted to insert the kernel diskette.
2. Insert the diskette.
3. Press ENTER. The following message appears:
Loading kernel from diskette.
n blocks
Uncompressing kernel file.
Kernel has been loaded successfully. Please remove diskette
and press <Enter> to continue.4. Remove the diskette from the drive.
5. Press ENTER. The Kernel Configuration Main Menu appears.
6. Choose Exit.
Configure General Kernel Parameters
You can configure certain UNIX kernel parameters.
Caution: Do not configure these parameters unless you have considerable experience with VINES servers and are familiar with UNIX operating system parameters. You could impair the operation of your server and your network by making inappropriate changes to these kernel parameters.
You can configure the parameters described here. Table C-2 presents the minimum, maximum, and default values for each parameter.
NBUF - Specifies the number of 1 KB UNIX system buffers allocated at boot time. The buffers form a data cache that is a memory array containing disk file information. Cache hit rates increase with the number of system buffers.
Cache hits reduce the number of disk accesses and thus may improve overall performance. The number of hash table entries (NHBUF) should be increased along with the number of system buffers (NBUF) for optimal performance. Select NBUF so that NBUF divided by NHBUF is approximately equal to 4.
NHBUF - Specifies the number of hash table entries to allocate for system buffers. These entries are used to search for a buffer given a device number and a block number, rather than conducting a linear search through the entire list of buffers.
NHBUF must be a power of 2; therefore the only valid values of NHBUF are 256, 512, 1024, 2048, and 4096. If you use some other value, system performance may be degraded. Select NHBUF so that the NBUF divided by NHBUF is approximately equal to 4.
Table C-1 presents recommended values of NHBUF for ranges of values of NBUF.
NBUF Range |
|
512 - 1024 |
|
1025 - 2048 |
|
2049 - 4096 |
|
4097 - 8192 |
|
8193 - 12288 |
|
NINODE - Specifies the number of inode table entries to allocate. Each table entry represents an in-core inode that is an active file. For example, an active file might be a current directory, an open file, or a mount point. The file control structure is modified when you change NINODE. The number of entries used depends on the number of open files. NINODE relates directly to NFILE; NFILE must be equal to or greater than NINODE. When the inode table overflows, a message appears on the console.
NFILE - Specifies how many open file table entries to allocate. Each entry represents an open file. NFILE relates directly to NINODE; NFILE must be equal to or greater than NINODE. The NFILE control structure operates the same as the NINODE structure. When the file table overflows, a message appears on the console.
NPROC - Specifies how many process table entries to allocate. Each table entry represents an active process. The swapper is always the first entry and /etc/init is always the second entry. The number of entries depends on the number of terminal lines available and the number of services. The average number of processes per service is in the range of 1 to 5.
BDFLUSHR - Specifies the interval in seconds for checking the need to write file system buffers to disk. The range is from 15 to 300 and the default is 60 seconds.
GPGSLO - Specifies the number of free memory pages (freemem) at which point vhand (a paging daemon) starts stealing least-recently-used (LRU) pages from other processes. Must be an integer equal to or greater than 25 and less than GPGSHI. A memory page is 4 kilobytes.
GPGSHI - Specifies the number of free memory pages (freemem) at which point vhand stops stealing least-recently-used (LRU) pages from other processes. Must be an integer greater than 40, greater than GPGSLO, and less than 25 percent of the number of pages of available memory.
Table C-2 presents the minimum, maximum, and default values for each parameter.
Parameter | Description | Minimum | Maximum | Default |
NBUF | System Buffers | 512 | 12288 | 512 |
NHBUF | Hash table entries | 256 | 4096 | 256 |
NINODE | Inode table entries | 400 | 2500 | 400 |
NFILE | Open file table entries | 700 | 2500 | 700 |
NPROC | Process table entries | 50 | 500 | 200 |
BDFLUSHR | Frequency of flushing file system cache, in seconds | 15 | 300 | 60 |
GPGSLO |
Number of free memory pages when vhand steals
least-recently- used (LRU) pages |
25 | 200 | 50 |
GPGSHI | Number of free memory pages when vhand stops stealing least-recently-used (LRU) pages | 40 | 300 | 100 |
To Configure Kernel Parameters
1. From the Operator Menu, select System Maintenance.
2. From the System Maintenance Menu, select Configure/Diagnose Server.
3. From the Banyan Server Configuration menu, select Configure Kernel.
4. At the prompt, enter C to access the Kernel Configuration Main Menu.
5. Select Configure General Kernel Parameters.
6. Select the kernel parameter you want to change.
7. At the parameter screen, enter the new value of the parameter, keeping in mind the maximum and minimum values displayed, or press ENTER to retain the current value. After you have changed the parameters you wish to change, select Return to Previous Menu.
8. Select Build Kernel.
9. Select Build current or default configuration and answer the prompts appropriately.
10. Select Return to previous menu.
11. Select Exit and return to the Operator Menu.
12. Select Shutdown Server Software.
13. Select Shut down services and do AUTOMATIC REBOOT.
The new parameter values take effect after the kernel is rebuilt and the server is rebooted.
You can set thresholds on the number of clients for which the server provides a Z-drive and on the number of clients for which the server acts as the routing server. These thresholds allow you to balance the loads on servers.
Configuring the Z-drive Threshold
You can set a threshold on the number of clients for which the server provides a Z-drive. When the threshold is reached, the server delays before responding to additional Z-drive requests. This delay allows slower servers to respond and accept the client requests for a Z-drive, and ensures that the requests are answered if no other servers are available.
Valid Z-drive threshold values are zero (0) to unlimited (32766). Zero means that the server will not respond to client Z-drive requests even after a delay period. The default threshold is 32766, or unlimited.
When you change the threshold, recycle (stop and start) VINES Files or reboot the server for the new threshold to take effect.
To Configure the Z-drive Threshold
1. From the Operator Menu, select System Maintenance.
2. Select Configure/Diagnose Server.
3. Select Configure Thresholds.
4. At the Configure Thresholds screen, enter a value between 0 and 32766 for the new Z-drive threshold.
5. Press F10 to save the new threshold. You exit to the Server Configuration menu.
6. Select Return to System Maintenance Menu.
7. Select Return to Operator Mennu.
Configuring the Routing Threshold
You can set a threshold on the number of clients for which the server acts as the routing server. When the threshold is reached, the server delays before responding to additional routing requests. You can also configure the delay period.This delay allows slower servers to act as routing servers after the faster servers reach their thresholds. It also ensures that clients get a routing server even if all servers are at their thresholds.
Valid routing threshold values are zero (0) to unlimited (32766). Zero means that the server will not respond to client routing requests even after a delay period. The default threshold is 32766, or unlimited.
The delay period is in units of 200 millisecond ticks. Valid delay values are from 1 (200 ms) to 50 (10 seconds). The default delay period is 1.
When you change the threshold and the delay period, the change takes effect immediately. When the server is rebooted, the new threshold is still in effect.
To Configure the Routing Threshold
1. From the Operator Menu, select System Maintenance.
2. Select Configure/Diagnose Server.
3. Select Configure Thresholds.
4. At the Configure Thresholds screen, enter a value between 0 and 32766 for the new router threshold.
5. Enter a value for the new router threshold delay time between 1 and 50.
6. Press F10 to save the new threshold and delay time.You exit to the Server Configuration menu.
7. Select Return to System Maintenance Menu.
8. Select Return to Operator Menu.
Configuring File Service SPP Timeout Period
The File Service SPP timeout function allows you to disconnect idle File Service SPP connections after a configurable time period. When a client tries to access the disconnected SPP connection (file service) after timing out, the server re-establishes the SPP connection with the client. By default, there is no SPP timeout.
Use the Banyan Server Configuration Menu to enable and disable the SPP timeout function. Idle timeout periods have an uncertainty of approximately 25% which means that, if the timeout period is set for 12 minutes, the longest idle time that can elapse is approximately 15 minutes before the SPP connection disconnects. You can set the timeout period from 0 to 120 minutes in whole minutes; 0 minutes disables the timeout feature on the server. You must reboot the server for changes to the timeout period to take effect.
To Configure the SPP Timeout Period
1. Select System Maintenance from the Operator menu.
2. Select Configure/Diagnose server.
3. Select Configure File Service SPP Timeout Period.
The Banyan File Service SPP Timeout Configuration screen appears, showing the current timeout period and prompting you for a new timeout period.
4. Do one of the following:
- Enter a new timeout period in minutes.
Timeout periods range from 0 (zero) minutes (disabled) to 120 minutes, in whole minutes.
- Enter C to exit from the screen without changing the current timeout setting.
A message on the screen confirms your new timeout setting if any, and the Banyan Server Configuration menu appears.
5. Select Return to System Maintenance Menu.
Note: Servers do not reserve SPP connections that have been disconnected. If all SPP connections on a server are in use and a timeout occurs releasing one of the SPP connections, another user can connect to the newly released connection. The original user cannot reconnect to the file service because there are no SPP connections available.
Do not set both the server-side SPP timeout and the DOS client-side timeout functions. Disable the DOS client timeout period if you set the server-side SPP timeout.
To Disable the DOS Client Timeout Period
1. Use a text editor to open the AUTOEXEC.BAT file on the workstation.
2. Verify that BAN is loaded with the /NC switch.
3. Locate the line containing the REDIR command.
4. Remove the /T:nnn switch from the REDIR command line.
5. Save the change to the AUTOEXEC.BAT file and close the file.
6. Reboot the workstation.
The redirector change takes affect and your workstation does not disconnect idle drives.
For Example, if the AUTOEXEC.BAT file contains the following lines:
CD Banyan
Ban /nc
3c503ban
redir4 /t:10Change the REDIR command line as follows to disable the client-side file service disconnect function:
CD Banyan
Ban /nc
3c503ban
redir4
Configure File Service Code Pages
The European Latin 1 language clients that use Code Page 850--French, German, Spanish and others have problems backing up or accessing files with extended characters in the filenames of files that were created in VINES 6.x and subsequently restored to a VINES 7.x or 8.x file service. The problems occur because of the way VINES stores the files in the file system. Prior to VINES 7.x, VINES stored files in the file system with no code page associated with the file. When a pre-VINES 7.x file is restored from a backup, the system assigns Code Page 0 to the file because it does not know what client created the file. At VINES 7.x and greater, the code page of the client creating the file is assigned to the file.
Code Page 0 is essentially Code Page 437 with no casing rules assigned to the high bit characters, those characters at 0x80 and above. IFNTOOL reconstructs each filename in a file service so that the file is stored in the correct location. You apply IFNTOOL to one or more file services on a VINES 8.x server to update the names and code pages of files stored in each file service.
IFNTOOL converts all filenames in the target file service to the Code Page 850 equivalent, and recomputes the hash values. Running the utility enables customers who have upgraded to VINES 8.50 (1) or later and are experiencing international filename issues to remedy the situation.
Restrictions on Running IFNTOOL
Do not run IFNTOOL on a VINES file service that stores files created by Macintosh clients. Running IFNTOOL over files created by Macintosh clients causes Macintosh users to lose access to the files and there is no way to recover the files without restoring them from a backup. If you have Macintosh files on a file service, you can:
![]()
Put all the Macintosh files in one directory and exclude that directory when you run IFNTOOL from the console. ![]()
Move all Macintosh files to a directory on a file service that you will not run IFNTOOL on, for example, to the VINES Files file service. Although you can enter any code page, run IFNTOOL against files created by European clients only. IFNTOOL renames affected files to Code Page 850, the code page used by European clients, by default.
After restoring a VINES 6.x file service to a VINES 8.50 (1) or greater server and using the IFNTOOL utility, use VINES 8.x or greater file backup utilities to back up the file service. Do not restore the 6.x file service backup to the 8.50 (1) or greater server again; use the 8.x or greater backup. In addition, upgrade all 6.x clients that access the 8.50 (1) or greater server to the latest 8.x client revision so they will not create Code Page 0 files and cause the problem to continue.
IFNTOOL Log Files
When you run IFNTOOL against one or more file services, the tool automatically creates a log file ifntool.log for each file service that you process. After you run the tool you have the option to view the log file for each processed file service. In addition, IFNTOOL creates the logfile mcp.log in the root of the VINES Files service (or in /disk1/BFS/bfslogs if it cannot put it in VINES Files). mcp.log contains only starting and ending timestamps, and a list of all the file services that IFNTOOL processed. All log files are in UNIX format. You can use TODOS to display them or to convert them to DOS format. If mcp.log gets created in /disk1/BFS/bfslogs, you must use UNIX Access to see it.
Running IFNTOOL
To run IFNTOOL against selected file services on a server:
1. From the Operator Menu, select System Maintenance. The System Maintenance menu appears.
2. Select Configure/Diagnose Server. The Banyan Server Configuration menu appears.
3. Select Configure File Service Codepages. The Manage File Service Codepages menu appears providing four choices for setting up and running IFNTOOL:
![]()
Set File Service Arguments - Lets you mark file services for processing and set the IFNTOOL arguments for processing the files in the file service. ![]()
Examine Logfiles - Lets you view the file ifntool.log generated for each file service when you run IFNTOOL. ![]()
Start Ifntool - Starts IFNTOOL using the arguments you set for each selected file service. ![]()
Exit - Returns to the Banyan Server Configuration menu. 4. Use the arrow keys to select Set File Service Arguments and press Enter. The cursor moves down into the list of file services configured on the server.
5. Use the arrow keys to select a file service and press Enter. The Set File Service Arguments menu appears, listing the default argument settings for the selected file service.
6. Use the arrow keys, or press Enter, to step through the list of file service arguments. To change an arguments value, move the cursor to the argument, type the new value for the argument, and press Enter.
The arguments are:
![]()
Old codepage - The code page currently set. The default is * meaning all code pages. You can enter the current code page designation or 0 for none, representing a file from a pre-7.x file service. ![]()
New codepage - The default is 850, the code page for French, German, Spanish, and other European clients. ![]()
Pathname - The pathname for the directory to process. The default is / for the root of the file service to process all files and directories in the file service. ![]()
Do subdirectories - If set to Yes, process all subdirectories and their files below the pathname directory. If set to No, process only the directory specified in pathname. The default is Yes. ![]()
Directory only - If pathname is a directory, rename or list only the directory name, not the contents. The default is No. ![]()
List Only - Change the code page values of files to the new code page setting (the default No), or only list the files with their code page values and do not make any changes (Yes). ![]()
All names - Can be used with List Only to get a listing of the current code page values of the files. Setting this to Yes results in a display of all names for each file: the DOS, LONG, UNIX, and Macintosh names. The default is No. ![]()
Mark service - Set this to Yes to mark this file service to process when you start Ifntool. If set to No (the default), this file service is not processed. 7. After you set the arguments, press F10 to save your changes and return to the Manage File Service Codepages menu.
To return to the Manage File Service Codepages menu without saving your changes, press ESC.
8. Repeat steps 5 through 7 to set the file service arguments for each file service you want to run IFNTOOL against.
9. From the Manage File Service Codepages menu, select Start Ifntool and confirm that you want Ifntool to start.
10. When Ifntool completes processing, you see the Ifntool Finished screen. Press Esc to return to the Manage File Service Codepages menu and select Examine Logfiles to view the Ifntool logs.
11. Press Enter at the file service name to see the log file for that service and press Enter or Esc to quit the log file.
If there are any errors, see "Troubleshooting IFNTOOL Results," which follows.
Troubleshooting IFNTOOL Results
IFNTOOL works by renaming each file to a temporary directory (the name of which it displays) with the new code page. It then renames the file back to the original directory. Errors that IFNTOOL may encounter in the renaming operation and that it may display are described here.
ERROR: Rename to newcp in tmpdir returned error error.
Renaming the file to the new code page in the temporary directory failed and the file stays in the original directory without being changed. This may be caused by IFNTOOL being unable to access the file. You can manually rename the file.
ERROR: Rename to newcp in origdir returned error error.
Renaming the file to the new code page back to the original directory from the temporary directory failed and IFNTOOL returns the file to the original directory with the original code page. You can manually rename the file.
ERROR: Rename back to oldcp returned error error.
Renaming the file back to the original directory with the original code page failed and the file remains in the temporary directory with the name ___ifnxxx.tmp where xxx starts at 000 and continues numerically for each file where this error is encountered.
ERROR: Rename returned error error
IFNTOOL moved the file to the temporary directory and changed the code page but was unable to rename it so left it in the temporary directory. You can manually move it to the original directory.
ERROR: vgetattr of pathname returned error
IFNTOOL could not get the attributes of a file. The file may have been created in UNIX and does not have a valid DOS filename.
WARNING: No DOSNAME found - skipping.
IFNTOOL found a file that was apparently created in UNIX and does not have a valid DOS filename. IFNTOOL cannot rename this file.