Symptom
Possible Cause
LifeKeeper fail over operation fails with umount busy error. The file system kit used to build NAS hierarchies cannot detect and remove processes not protected by LifeKeeper that are using the mounted file system in a fail over condition. Therefore, it is highly recommended that only LifeKeeper protected processes use the NAS protected file system. In the event of this failure, you must identify the processes using the file system and kill them. The fuser -m command can be used to determine the processes currently accessing the file system. Please see the fuser man pages for details on its use.
LifeKeeper does local recovery of file system mounted via server name.

If a file system protected by the NAS Recovery Kit was mounted via host name rather than IP address, then after creating the NAS resource, LifeKeeper logs a message similar to the following:

. . . WARNING: Mon Aug 26 11:27:01 2002:

LifeKeeper protected filesystem resource “tmp/mnt-on-tom.brown.com” (/tmp/mnt) is in service but not mounted

. . . Attempting Local Recovery of resource

LifeKeeper will re-mount the file system using the IP address at this point. However, if it encounters a problem, LifeKeeper will failover the NAS resource to the backup server (if it has been extended), or take the resource out of service (if the resource has not been extended).

Suggested Action: If the local recovery is successful, no further action is needed. However, if the local recovery fails, you should:

  1. Delete the NAS resource in LifeKeeper.

  2. Re-mount the file system via IP address rather than host name.

  3. Re-create the NAS resource.

フィードバック

お役に立ちましたか?

はい いいえ
お役に立ちましたか
理由をお聞かせください
フィードバックありがとうございました

このトピックへフィードバック

送信