T.R | Title | User | Personal Name | Date | Lines |
---|
2034.1 | | COMICS::CORNEJ | What's an Architect? | Wed Apr 30 1997 12:52 | 6 |
| Does lsof report anything if a user is "cd"'d to the filesystem?
(I don't know - I've never looked)
Jc
|
2034.2 | Yes, lsof reports cd's | NNTPD::"hoveys@zko.dec.com" | Shari Hovey | Thu May 01 1997 01:31 | 9 |
| Hi,
Yes, lsof will report a process id if someone is cd'd to the disk.
Any other suggestions?
Thanks,
Shari
[Posted by WWW Notes gateway]
|
2034.3 | ??? | BRSDVP::DEVOS | Manu Devos NSIS Brussels 856-7539 | Thu May 01 1997 10:12 | 10 |
| If DECsafe is telling the device is busy, then lsof should show you
which process.
Did you try to place lsof IN YOUR STOP script (at the end) to display
to the console its output?
Maybe you started asemgr from a shell whose current directory is in the
/ase1 directory.
Manu.
|
2034.4 | lsof does not detect all reasons | SMURF::MYRDAL | | Thu May 01 1997 15:11 | 21 |
| Hi,
I asked this question of one of the filesystem engineers here. This
was part of his reponse:
"I'm not convinced lsof is capable of detecting all references. I know
that lsof cannot detect mmap references, which will prevent a
filesystem from being unmounted.
There is/will be a patch to detect mmap references via the fuser
syscall. Our fuser utility will detect all references. You may need to
build a steel version fuser (statically-linked) to provide to the customer.
I would recommend they investigate for ref-holders either by using fuser
(preferably with the patch to detect mmap references), or via the good
old-fashioned approach of killing processes until they find the guilty
party."
Just passing on the info ......
-- Greg
|