Port update hosed entire system

[Erich Dollansky]

Hi,

On Tue, 2 Oct 2012 06:20:45 -0400
Rod Person <rodperson at rodperson.com> wrote:

> On Mon, 1 Oct 2012 08:02:54 +0200
> Polytropon <freebsd at edvax.de> wrote:
> 
> > On Mon, 1 Oct 2012 20:08:29 -0400, Rod Person wrote:
> > > Hi All,
> > > 
> > > I was attempting to update ports that used libogg with the command
> > > 
> > > portmaster -d -y -r libogg
> > > 
> > > I went away and came back some hours later and some updates had
> > > failed. Now my shell segfaults on any command such as ls, clear or
> > > su I tried to login on another console as root and after giving
> > > the password it just goes back to login. I am at a loss as to
> > > what to do to fix this one.
> > 
> > That sounds like a really weird problem. FreeBSD and the
> > ports (which portmaster deals with) are separated systems,
> > so even if you totally hose your ports, the OS should not
> > be affected.
> 
> I'm well aware of this, and is also why I no clue what could have
> happened. It would never have occured to me that updating a port that
> has to do with audio and video containers would totally leave me
> unable to login into my system or issue and shell commands without
> getting a segmentation fault.

the ports did nothing of this sort.
> 
> I did discover that my / file system had run out of space -131MB.
> 
Ah, all red lights are on now.

> I'm still able to issue sudo, so using sudo rm -r I was able to free
> up 25GB...but still, /bin/sh, ls, clear all seg fault and su doesn't
> work and switching consoles doesn't let me log in.
> 
You ave now 25GB free on /?

More red lights are on now.

> I maybe be left with attempting a single user boot, but I'm still not
> that comfortable at attempting such as I don't want to have a totally
> useless box.

What partitioning schema do you have?

Could it be that you simply filled the file system and FreeBSD does not
find any space even just for a restart?

Erich