Right now there is one concern: If we are sending kill -9 to all application accessing file ('fuser -k' sends kill -9), can we by some chance to send it to nova-compute or libvirtd?
Some scenarios:
1) Concurrent calls 'create snapshot' and 'delete' from user
2) libvirtd performing scheduled tasks on image
May be we should not call fuser, but do the same (search in /proc/PID/fd) and try to narrow application list to 'scp' and 'rsync'?
I know it sounds paranoid, but I don't want to see random kill -9 on production on unspecified process list.
I opened question on stackoverflow: http:// stackoverflow. com/questions/ 29494852/ force-applicati on-to-close- fd-or-cause- eio-linux
Right now there is one concern: If we are sending kill -9 to all application accessing file ('fuser -k' sends kill -9), can we by some chance to send it to nova-compute or libvirtd?
Some scenarios:
1) Concurrent calls 'create snapshot' and 'delete' from user
2) libvirtd performing scheduled tasks on image
May be we should not call fuser, but do the same (search in /proc/PID/fd) and try to narrow application list to 'scp' and 'rsync'?
I know it sounds paranoid, but I don't want to see random kill -9 on production on unspecified process list.