Re: Read-only /usr
Bernd Eckenfels <email@example.com> writes:
> On Sun, Nov 04, 2001 at 07:14:18PM +1000, Anthony Towns wrote:
>> However this doesn't work quite frequently, since the umount fails
>> if there's any file in /usr that's been deleted (ie, was in a package
>> which has been updated), but is still being used (a /usr/lib/lib* that's
>> referenced by a long running program, or a /usr/bin/* program that's still
>> running, like apt-get or dselect). This is because the filesystem will
>> be modified when the file is closed, because the inode will be freed,
>> so it's obviously not read-only.
> Yepp. The recent lsof has a modification to detect those files.
How recent? For me, "lsof +L1" only sometimes is able to tell me
which files are the problem. Other times, it shows no output, but
mount still tells me that the filesystem is busy.
AJ, thanks for the scripts. I'll give them a try.