Aurelien Degremont - Stagiaire wrote:
Dean Roehrich a écrit :
These are often blocked, but interruptible. Otherwise they're stuck
until the
HSM application is restarted so it can continue processing events.
Yes, i saw this, no other solutions ?
There's an issue with the DM_EVENT_UNMOUNT event.
If the HSM application is unavailable, you try to unmount a managed
filesystem, the filesystem will start to be unmount, the event msg
will be sent, but not received, so the unmount call will be blocked.
Unfortunately, the HSM application will never be able to re-register
for the UNMOUNT event for this filesystem, because this filesystem is
no longer available as a "loaded and dmapi-compliant" filesystem (we
cannot get the filesystem handle anymore), but it's also not unloaded.
The system is quite broken for this FS and i see no solution to solve
the situation...
Am i clear ? :)
Aurelien
Hi -
If your goal is just to clear out the pending unmount event so that
umount completes, you can write a utility that gets the sessions, gets
the tokens, and then responds continue. The filesystem should unmount
and then you can go back to debugging why the HSM app. went away.
-Damian
|