The biggest concern for any organization using a server is data integrity. The various solutions like Network Attached Storage, Storage Area Networks, high availability servers, online data backup and disaster recovery solutions are among the available solutions.
Apart from the third party available solutions for protecting Physical Volumes. The native data protection solutions provided by AIX are:
- Bad Block Relocation.
- Quorum Checking.
Here in the article we’ll be discussing Bad Block Relocation.
Bad Block Relocation
Â Hard Data Relocation
Data Relocation Within The Disk
This is least complicated operation for data relocation. If the system fails to carry out data I/O requests, then it anticipates data corruption. So data protection is carried out by moving data automatically within disk. No notifications are generated.
This is slightly more complex way of data relocation. The operation is initiated and instructed by Physical Volume. In this case data is moved from one Physical Partition to another reserved physical partition. So, data location changes from one PP A to another PP B. After the completion of data relocation, the device driver continues to refer to old location, PP A, butÂ the LVM device driver. Bad block directory is maintained by LVMÂ device driver. Also it maintains the translation table which maps the bad block PP A to good block PP B. Let’s say PP A location was bad block. So, it will be in the bad block directory of LVMÂ device driver. Whenever some request comes for some I/O operation for any block, the device driver will look its bad block directory. If the block is listed in that, it translates the location requested to corresponding good location, say PP B, where the actual data is residing. Hence data protection is ensured in most cases.
Hard Data Relocation
1 thought on “How Does AIX Deal With Bad Blocks”