Description of problem: fuser -m <device> fails to detect open files on a filesystem that has been lazily unmounted. This is bad since a typical use case for "fuser -m" is to kill remaining users of a filesystem. How reproducible: always Steps to Reproduce: dd if=/dev/zero of=fs.img bs=1M count=100 losetup /dev/loop4 fs.img mkfs.ext2 /dev/loop4 mkdir mnt mount /dev/loop4 mnt touch mnt/testfile less mnt/testfile <CTRL>-Z # these will work and display PID of less fuser -m mnt fuser -m /dev/loop4 # lazy umount!! as there's open file it's actually still mounted and already open files can be accessed umount -l mnt fuser -m /dev/loop4 # doesn't find anything!! Actual results: two first fuser runs report the pid last does not Expected results: fuser reports the pid in all cases Additional info: Bug has been already reported to upstream including a patch: https://sourceforge.net/tracker/index.php?func=detail&aid=2545632&group_id=15273&atid=115273
This bugzilla has Keywords: Regression. Since no regressions are allowed between releases, it is also being proposed as a blocker for this release. Please resolve ASAP.
Created attachment 331413 [details] the patch from the upstream applies cleanly and I tested it works on rhel5
Daniel, could you (or Tomas) add a note to that affect to the upstream defect report then please? The upstream report was filed by the customer directly; having a public ack from your side is likely to increase the chances of it quickly being reviewed/accepted upstream.
OK, added a note to the upstream bug tracker
fixed in psmisc-22.2-7
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2009-0439.html