Thanks - your fix has worked perfectly for my until now. But now I've wanted to improve my scripts to be able to un/mount my encrypted partition even if chroot is mounted (ie by also doing un/mounting the bind mount to $CHROOT/media/xxx). But if I now run closechroot after unmounting the encrypted partition, there is nothing in /dev/mapper/... so your fix doesn't detect the problem and once again the phone crashes.

I can't say I understand why the '-m' option go g/fuser would ever be necessary but if you've done it there must a good reason. Just that for me the -m option causes nothing but grief.

So can I suggest a brute-force workaround mechanism where the user can specify in ~/.chroot whether fuser/gfuser with or without '-m' should be used. Happy to do it myself if you don't have the time.