The salvage command is used to direct the Salvager to recover, verify, or salvage the structure of an aggregate. Combine the command's -recoveronly, -verifyonly, and -salvageonly options as follows to specify the operations the Salvager is to perform on the specified aggregate:
Specify the -recoveronly option
To run recovery on the aggregate without attempting to determine or repair any inconsistencies found on it. Use this option to quickly return
consistency to an aggregate that does not need to be salvaged. This represents the normal production use of the Salvager.
Specify the -verifyonly option
To determine whether the structure of the aggregate contains any inconsistencies without running recovery or attempting to repair any
inconsistencies found on the aggregate. Use this option to assess the extent of the damage to an aggregate. The Salvager makes no modifications to an aggregate during verification. Note again that
it is normal for the Salvager to find errors when it verifies an aggregate that has not been recovered.
Specify the -recoveronly and -verifyonly options
To run recovery on the aggregate and then analyze its structure without attempting to repair any inconsistencies found
on it. Use these options if you believe that replaying the log can return consistency to the aggregate, but you want to verify the consistency of the aggregate after recovery is run. This approach
is more cautious than recovering the aggregate without verification.
Specify the -salvageonly option
To attempt to repair any inconsistencies found in the structure of the aggregate without first running recovery on it. Use this option if you
believe that the log is damaged or that replaying the log will not return consistency to the aggregate and may in fact further damage it. Under normal circumstances, do not salvage an aggregate
without first recovering it.
Omit the -recoveronly, -verifyonly, and -salvageonly options
To run recovery on the aggregate and then attempt to repair any inconsistencies found in the
structure of the aggregate. Omit these three options if you believe the log should be replayed before attempts are made to repair any inconsistencies found on the aggregate.
You cannot use the Salvager to recover or salvage an aggregate that is currently exported to the DCE namespace. If asked to perform either of these operations on an exported aggregate, the Salvager exits without performing the operation. If necessary, use the dfsexport command to detach an aggregate from the global namespace before recovering or salvaging it. Note that the Salvager also exits if it is run on an aggregate that houses a locally mounted fileset.
The Salvager prompts for direction only if one of the following is true:
· The aggregate on which it is run contains a non-LFS superblock whose creation time is more recent than that of its DCE LFS superblock.
· The size of the aggregate that is recorded in its DCE LFS superblock exceeds the capacity of the partition on which the aggregate resides.
At the prompt, you can choose to cancel or continue the operation. If you continue the operation in either of these situations and the aggregate proves to be invalid, the operation can produce unpredictable results. The best response in either case is to cancel the operation and attempt to determine the cause of the problem. Note that the command's -force option can be used to direct the Salvager to proceed rather than prompt for confirmation in these cases.
Internal structures maintained by the Salvager require a minimum of 1 megabyte of swap space. However, the total amount of swap space required by the Salvager depends largely on the size of the aggregate being salvaged and the extent of the damage to the aggregate.