1. Stale replication state detected on standby file system from a previous instantiation.
2. An incorrect replication standby site was supplied.
3. An incorrect replication standby file system was supplied.
2. Verify the correct standby site is used.
3. Verify the correct standby file system is used.
1. If ACFS Security is desired on primary and standby file systems, follow the below mentioned steps in sequence: a. Terminate replication on standby file system by executing 'acfsutil repl terminate' command. b. Initialize ACFS Security on standby site by executing 'acfsutil sec init' command. c. Reinitialize replication on standby file system by executing 'acfsutil repl init' command. d. Retry 'acfsutil repl init' command on the primary file system.
2. If ACFS Security is not desired on primary and standby file systems, follow the below mentioned steps in sequence: a. Terminate replication on standby file system by executing 'acfsutil repl terminate' command. b. Remove ACFS Security on primary file system by using 'acfsutil sec prepare' command. c. Reinitialize replication on standby file system by executing 'acfsutil repl init' command. d. Retry 'acfsutil repl init' command on the primary file system.
1. If ACFS Security is desired on primary and standby file systems, follow the below mentioned steps in sequence: a. Terminate replication on standby file system by executing 'acfsutil repl terminate' command. b. Initialize ACFS Security on standby site by executing 'acfsutil sec init' command. c. Reinitialize replication on standby file system by executing 'acfsutil repl init' command. d. Retry 'acfsutil repl init' command on the primary file system.
2. If ACFS Security is not desired on primary and standby file systems, follow below mentioned steps in sequence: a. Terminate replication on standby file system by executing 'acfsutil repl terminate' command. b. Remove ACFS Security on primary file system by using 'acfsutil sec prepare' command. c. Reinitialize replication on standby file system by executing 'acfsutil repl init' command. d. Retry 'acfsutil repl init' command on the primary file system.
1. If ACFS Encryption is desired on primary and standby file systems a. Terminate replication on standby file system by executing 'acfsutil repl terminate' command. b. Convert the PKCS wallet to SSO wallet on standby by executing 'acfsutil keystore migrate' command. c. Reinitialize replication on standby file system by executing 'acfsutil repl init' command. d. Retry 'acfsutil repl init' command on the primary file system.
2. If ACFS Encryption is not desired on primary and standby file systems a. Terminate replication on stanby filesystem by executing 'acfsutil repl terminate' command. b. Remove ACFS Encryption on primary filesystem by using 'acfsutil encr set' command. c. Reinitialize replication on standby file system by executing 'acfsutil repl init' command. d. Retry 'acfsutil repl init' command on the primary file system.
1. If ACFS Encryption is desired on primary and standby file systems a. Terminate replication on standby file system by executing 'acfsutil repl terminate' command. b. Convert the PKCS wallet to SSO wallet on standby by executing 'acfsutil keystore migrate' command. c. Reinitialize replication on standby file system by executing 'acfsutil repl init' command. d. Retry 'acfsutil repl init' command on the primary file system.
2. If ACFS Encryption is not desired on primary and standby file systems a. Terminate replication on stanby filesystem by executing 'acfsutil repl terminate' command. b. Remove ACFS Encryption on primary filesystem by using 'acfsutil encr set' command. c. Reinitialize replication on standby file system by executing 'acfsutil repl init' command. d. Retry 'acfsutil repl init' command on the primary file system.
1. The extent _Length and/or _PhysicalDiskOffset property were incorrect.
2. The file system size value was incorrect.
1. The _UpHeaderNodePtr property did not match its parent.
2. The parent identifier property was incorrect.
1. The extent values were not reset to zero when the extent was freed.
2. The _NextFreeExtent property of the extent structure was incorrect.
1. The _LastExtentPointer property of the file was incorrect.
2. The structure identified by the _LastExtentPointer value was not a DATA extent structure.
1. The _LastExtentPointer property of the file was incorrect.
2. The structure identified by the _LastExtentPointer value was not a valid DATA extent structure.
3. The _NextDataExtent property of one or more DATA extent structures was incorrect.
1. One or more of the DATA extent structures did not have a valid structure header.
2. The _NextDataExtent property of one or more DATA extent structures was incorrect.
1. The _LastExtentPointer value was incorrect.
2. The last DATA extent structure was not found because the The _NextDataExtent property of one or more DATA extent structures was incorrect.
1. The _LastExtentPointer property of the file was incorrect.
2. One or more extent structures did not have a valid structure header.
3. The _LastExtentPointer property of one or more extent structures was incorrect.
1. One or more of the extent structures did not have a valid structure header.
2. The _LastExtentPointer property of one or more extent structures was incorrect.
1. The _LinkCount property was incorrect.
2. One or more directory entries for this file was invalid or was not found.
3. A Directory_Entry structure for this file had an incorrect file identifier.
4. The _LinkCount property of an ACFS Internal File was not equal to one.
1. The _ParentID value did not match the file's parent directory.
2. The _ParentID value did not match any valid directory.
1. The extent values were not reset to zero when the extent was freed.
2. The _NextFreeExtent property of the file was incorrect.
1. The _AllocationSize value was incorrect.
2. The _Length property of one or more of the file's extents was incorrect.
3. The _NextFreeExtent property of the file was incorrect.
1. The _Length property of one or more extents of the File_Entry_Table was incorrect.
2. The _FileSize property of the File_Entry_Table was incorrect.
1. The extent values were not reset to zero when the extent was freed.
2. The _NextFreeExtent property of the file was incorrect.
1. The _FileEntryType value was incorrect for this particular file.
2. The _FileEntryType value was not on the list of valid values.
1. The _AllocationSize value was incorrect.
2. The value used to indicate the number of bits needed to map file system storage was incorrect.
1. The _AllocationSize should have been zero.
2. The _NextFreeExtent value was incorrect.
1. The _security_data value was incorrect.
2. The Security_Metadata file had incorrect data at the corresponding offset.
3. The Security_Metadata file was not found.
1. The _local_dir_blk_disk_offset value was incorrect.
2. The structure at the _local_dir_blk_disk_offset was not a Local_Metadata_Directory structure.
1. The _next_locator_blk_disk_offset was incorrect.
2. The structure at the _next_locator_blk_disk_offset was not a _Locator structure.
1. Run the ACFS Fixer which will automatically process all valid Log_Files.
2. Run the ACFS Checker and respond yes to any question pertaining to Log_File processing.
1. The Map_File entry's _Length was equal to zero.
2. The Map_File entry's _Length was not a multiple of the volume's sector size as detailed in the message.
1. The version information in the Volume_Disk_Header structure was not correct.
2. The ACFS Checker/Fixer or ACFS debug utility was not the correct version for the file system.
1. If the file system version displayed in the message is valid then run a compatible version of the ACFS Checker/Fixer or ACFS debug utility.
2. If the file system version displayed in the message is not valid then restore the file system from backup.
1. One or more of the file's directory structures had an invalid structure header.
2. The _next_dirnode property of one or more of the file's directory structures was incorrect.
3. The _first_dirnode property of the _Private directory structure was incorrect.
1. One or more of the file's directory structures had an invalid structure header.
2. The _next_free_dirnode property of one or more of the file's directory structures was incorrect.
3. The _dir_entry_free_list_head property of the _Private directory structure was incorrect.
1. The _hash_blk_free_list property of the _Private directory structure referenced a block that exceeded the directory's size.
2. The _next_free_blk property of a directory free block referenced a block that exceeded the directory's size.
1. One or more of the file's directory structures had an invalid structure header.
2. The next_free_blk property of one or more of the file's directory structures was incorrect.
3. The hash_blk_free_list property of the _Private directory structure was incorrect.
1. The volume went offline while the snapshot was being created.
2. The process creating the snapshot was unexpectedly terminated do to a shutdown of the system.
1. The volume was unmounted before the asynchronous phase of snapshot deletion had completed.
2. The volume went offline while the snapshot was being deleted.
3. The process deleting the snapshot was unexpectedly terminated do to a shutdown of the system.
1. The volume went offline while the snapshot was being created.
2. The process creating the snapshot was unexpectedly terminated do to a shutdown of the system.
1. The volume was unmounted before the asynchronous phase of snapshot deletion had completed.
2. The volume went offline while the snapshot was being deleted.
3. The process deleting the snapshot was unexpectedly terminated do to a shutdown of the system.
1. The data at the disk offset was not an ACFS metadata structure.
2. The metadata structure at the disk offset was in an inconsistent state.
1. The command entered was not recognized by the acfsdbg utility.
2. A partial command name was entered and there was more than one command that matched the characters entered.
1. The file system on this volume was being checked on this system or another system in the cluster.
2. The ACFS Checker/Fixer was unexpectedly terminated leaving the file system state incorrectly set.
1. Respond Y(yes) when prompted to run the ACFS Checker/Fixer.
2. Run the ACFS Fixer with the [f] option to reset the file system state to allow the file system to be mounted. NOTE: Use caution with this option as file system repairs from a previous run of the ACFS Checker/Fixer may be incomplete.
1. The directory file had no corresponding parent directory entry.
2. The directory file had a parent directory entry, but there was a problem with corresponding parent directory file.
1. The file had no corresponding directory entry.
2. The file had a directory entry, but there was a problem with corresponding directory file.
1. Free up some storage by deleting some files.
2. Add available storage by increasing the size of the file system via the 'acfsutil size' command.
1. Free up some storage by deleting some files.
2. Add available storage by increasing the size of the file system via the 'acfsutil size' command.
1. The extended attribute container structure disk offset was incorrect.
2. The file system size value was incorrect.
* - acfsutil sec realm add r1 -m /mnt -l READ:rs1
* - acfsutil sec realm add r1 -m /mnt -l READ:rs1,MKDIR:rs2
* For example, '-t username alice'
* '-t application 'c:\programs\mozilla.exe'
* '-t application '/sbin/cat'
* '-t hostname myhost.domain.com'