Re: determining what makes a filesystem busy
- To: firstname.lastname@example.org
- Subject: Re: determining what makes a filesystem busy
- From: Chris Baker <email@example.com>
- Date: 02 Jun 2000 12:40:02 -0700
- Message-id: <[🔎] firstname.lastname@example.org>
- In-reply-to: Joost Claessen's message of "Tue, 30 May 2000 08:30:55 +0200"
- References: <email@example.com> <firstname.lastname@example.org> <email@example.com> <3932E580.F6B7DAAE@lfs.one> <20000530083055.A4722@Smerfje>
Joost Claessen <firstname.lastname@example.org> writes:
> On Mon, May 29, 2000 at 09:47:44PM +0000, ktb wrote:
> > I don't know if it would work or even be recommended but have you tried
> > the -k option to kill all processes to that file system? The other
> > thought I had is boot into your system as a single user but I'm sure
> > that is what your trying to avoid, is a boot.
> > hth,
> > kent
> The only way to mount /usr ro is to put as a shell in your /etc/passwd one that doesn't
> need liberaries from /usr/lib. Bash can do it, when called upon correctly. I don't
This works for me just fine on a default install of bash in potato. I
have /usr mounted ro in fstab, and if I need to install anything I just
# mount -o rw,remount /usr
# mount -o ro,remount /usr
when I'm done, and I've never had any problems.
> know about oter shells. Then login and get the kill all remaining processes that use
> /usr. Usually that does the trick. By the way, init 1 does the work quick and I
> don't see it as a boot.