[460] in athena10
Re: Login chroots and interaction with updates
daemon@ATHENA.MIT.EDU (Sam Hartman)
Wed Aug 20 14:14:02 2008
From: Sam Hartman <hartmans@MIT.EDU>
To: ghudson@mit.edu
Cc: athena10@mit.edu
Date: Wed, 20 Aug 2008 14:13:30 -0400
In-Reply-To: <200808201649.m7KGn6oH020764@outgoing.mit.edu> (ghudson@MIT.EDU's
message of "Wed, 20 Aug 2008 12:49:06 -0400 (EDT)")
Message-ID: <tslk5ebimgl.fsf@mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
>>>>> "ghudson" == ghudson <ghudson@MIT.EDU> writes:
>> * Force-unmount the login snapshot and destroy it.
ghudson> This turns out to be a snag. There is no "force-unmount"
ghudson> in Linux except as applied to unreachable NFS
ghudson> filesystems. There is a "lazy unmount" which removes the
ghudson> path references and completes the unmount when the
ghudson> filesystem is no longer busy, but that doesn't help if we
ghudson> want to destroy the backing filesystem.
ghudson> So to unmount the login snapshot we first have to kill
ghudson> any processes which reference it.
Why not replace the device mapper tables with tables that return
ioerror, freeing up the snapshot?
