Summary: | umount -f doesn't seem to work | ||
---|---|---|---|
Product: | Base System | Reporter: | David Muir Sharnoff <muir> |
Component: | kern | Assignee: | dfr |
Status: | Closed FIXED | ||
Severity: | Affects Only Me | ||
Priority: | Normal | ||
Version: | 2.2-STABLE | ||
Hardware: | Any | ||
OS: | Any |
Description
David Muir Sharnoff
1997-10-01 08:10:01 UTC
As muir@idiom.com wrote: > tmp:/ /net/tmp nfs ro,intr,bg,tcp,nfsv2,resvport,nosuid 0 0 > tmp:/usr /net/tmp/usr nfs ro,intr,bg,tcp,nfsv2,resvport,nosuid 0 0 > > >Description: > > # umount -f -h tmp > nfs server tmp:/: not responding This is what one would expect how umount -f is working, but not what is described for umount -f: forcibly unmounting is currently only defined as ``don't care about resources that are locally still in use, but revoke them''. Anyway, i think this is already in Doug Rabson's queue of ``nice to have'' things. If i'm not totally mistaken, there might already be another open PR for it. Did you check before filing? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) * As muir@idiom.com wrote: * * > tmp:/ /net/tmp nfs ro,intr,bg,tcp,nfsv2,resvport,nosuid 0 0 * > tmp:/usr /net/tmp/usr nfs ro,intr,bg,tcp,nfsv2,resvport,nosuid 0 0 * > * > >Description: * > * > # umount -f -h tmp * > nfs server tmp:/: not responding * * This is what one would expect how umount -f is working, but not what * is described for umount -f: forcibly unmounting is currently only * defined as ``don't care about resources that are locally still in use, * but revoke them''. * * Anyway, i think this is already in Doug Rabson's queue of ``nice to * have'' things. If i'm not totally mistaken, there might already be * another open PR for it. Did you check before filing? No. It seemed like a bug to me. -Dave Responsible Changed From-To: freebsd-bugs->dfr Doug is our Mr. NFS. State Changed From-To: open->closed Fixed in both -CURRENT and -STABLE. |