Re: Umount a Persistent KNOPPIX Disk Image in use
Hi Jody,
On Sun, Jun 18, 2006 at 12:26:35PM +0200, Jody wrote:
> Hi,
>
> I'm using a PDI, in which I have already installed new packages and
> would like to install yakuake and gnump3d, but my PDI seems to have
> become to small.
>
> I wonder how I could increase size of PDI without rebooting.
>
> Could it be possible to have a mount PDI daemon which could mount/start
> or umount/stop with a script in /etc/init.d ?
Difficult, because you have to make sure that no process is using the
directory while mounting/umounting.
> Then we could increase size, change PDI, have a diff of working/not
> working config, package ...
It could be possible, if we use a DIFFERENT Image after a "remount", and let the "old" processes that still access the other image, just run.
> I have tried to umount it by switching to second runlevel but /UNIONFS
> is busy,
It is, because several processes are monitoring files on /UNIONFS, see
the output of "lsof".
> fuser -v /UNIONFS returns nothing
fuser is not very clever, unfortunately. IMHO, it only recognizes
open(), not stat() or mmap().
Also, the "fuser" you called, probably comes from /UNIONFS/bin...
> I've also tried to umount /KNOPPIX.IMG but think I have to umount
> UNIONFS before.
You can use the "lazy" option of umount, i.e. -l, to make the old
content "disappear". The filesystem will be physically umounted and put
into a clean state when all processes that are accessint it, ended (i.e.
init 0).
I like to use symlinks instead, because you can point a symlink to a new
location without unmounting anything. This is being done in
knoppix-image when the persistent image is joined with the rest.
Regards
-Klaus Knopper
Reply to: