From: Herbert Poetzl (herbert_at_13thfloor.at)
Date: Wed 26 Jan 2005 - 16:00:25 GMT
On Wed, Jan 26, 2005 at 04:50:28PM +0100, Nicolas Costes wrote:
> Le mercredi 26 Janvier 2005 16:01, Herbert Poetzl a écrit :
> > /proc is a _virtual_ filesystem, it doesn't use up
> > _any_ disk space at all, and you should not consider
> > it if you are interested in the space a vserver
> > uses up (on disk, that is), so your original command
> > should look like this:
> > du -sxb /vservers/*
> > -x File system mount points are not traversed.
> Ah, I didn't know this option, thanks. But I know that /proc takes no
> space regardless of what is in it... the thing that made ma look twice is
> the size difference between this vserver and the others. For exaple, i've
> just built another Cups vserver (To replace this one that is now
> broken ;) and everything here is as usual. The size "used" by /proc is 6
> bytes, like the other vservers...
> So, only one of my vserver suddenly decided to show /proc/kcore, and not
> the others.
> Ok, i've got more information: It seems that the various vservers' /proc
> directories are unvisible from the host server. When entering a given
> vserver, the contents of its proc dir appears... And has got a "size".
> So why the hell this particular's proc dir is visible from the host
> server, while it is _not apparently mounted_ ???
well, because it's not so apparently that it is not mounted ...
most likely the mount happened in the same namespace where
your host server resides ... no idea why just for that one
vserver, maybe Enrico has some ideas ...
> > of course, you can not remove the /proc filesystem
> > by deleting files inside, you should _unmount_ it
> > (either from withing the vserver or the same namespace)
> > umount /vserver/vs4/proc or
> > umount /proc (inside the vserver)
> Anyway, i tried blindly "umount /vservers/vs4/proc", and it worked...
> Still I cannot delete /vservers/vs4/proc, but it's empty, at least.
hmm, did you check from inside and outside? if so, maybe
it's some kind of namespace bug/issue ...
> > > What happens ?
> > nothing unexpected, really ;)
> Well, what I meant, is why this difference from one vserver to others ?
> First, why was it the only one to have proc mounted visible from the
> host, and second why this didn't appear with a "mount" command on the
> host ? (For the second, I have an idea... Maybe this is du to contexts,
> no ?)
no, it's due to the fact that mount doesn't care about
the filesystems mounted or not mounted, it stupidly
displays the contents of /etc/mtab ... you can check that
by adding/changing something there ...
/proc/mounts (on the host) should know the facts ...
> (°> Nicolas Costes
> /|\ IUT de La Roche / Yon
> ( ^ ) Clé publique: http://www.keyserver.net/
> ^ ^ Musique libre: http://www.magnatune.com/
> Vserver mailing list
Vserver mailing list