My common method of filling / is to think that I've got a remote volume
mounted a mount point and it isn't. For example, I mount my backup volume
on /mnt/backups. Obviously the directory is there, but if for reason the
volume fails to mount (eg, the server wasn't available when the mount
happened), I'd throw my backups into /mnt/backups anyway and fill the
sucker.
Since you've got a SCSI disk, you more than likely don't have a trivial
configuration so perhaps you could share some more info on what your fstab
normally looks like.
If you ever fail to start X, you could run level 3 - that will leave you in
full character mode with networking enabled and make it much easier to
troubleshoot than run level 1.
.../Ed
Ed Wilts
Mounds View, MN, USA
mailto:[EMAIL PROTECTED]
From: <[EMAIL PROTECTED]>
> After a string of errors this afternoon, I decided to reboot. The reboot
failed to startx. I restarted in "linux 1" mode, then a memory of past
experience with a full "/" started creeping back. I rebooted from the 7.1 CD
into rescue mode, and ran e2fsck on the affected partition (sda9), after
freeing up some space by moving files off it, and yes, I'm sure I put them
on a different partition. The system still won't startx, but my big worry
now is that df is reporting incorrectly. This is what it says:
>
> 1M Blocks Used Available Use mounted on
> /dev/sda9 3238 3075 0 100% /
>
> Obviously there is a problem somewhere. I would much rather not nuke it
and start over. The filesystem on sda9 is readable, but when I move files
off it, it doesn't report any free space as a result.
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
