Re: [SLE] Suse 7.2 eating disk space
Thanks for all the help so far..
It might also be worth running a full fsck if you're willing to risk shutting the machine down. I'm not sure whether you can do this from the SuSE rescue disk; you might have to either play around with booting your machine in single-user mode and mounting the root FS read-only, or you could download a copy of something like tomsrtbt and boot and fsck from that.
From man fsck it seems I can just ruin it as root - what did you mean by shutting the machinge down, just that it'll take a week? So should I just run fsck without any options or should I run it: fsck -t /dev/hda ?
And I made the backup, thanks!
Of course, I could be talking total rubbish, and it could be something totally benign, but better to have a backup that's never needed than not to have a backup that you *do* need... :-)
-- David Smith Work Email: Dave.Smith@st.com STMicroelectronics Home Email: David.Smith@ds-electronics.co.uk Bristol, England
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com
On Wed, Apr 03, 2002 at 04:57:07PM +0200, php@nickselby.com wrote:
From man fsck it seems I can just ruin it as root - what did you mean by shutting the machinge down, just that it'll take a week?
So should I just run fsck without any options or should I run it:
fsck -t /dev/hda
1. You can only run fsck as root. 2. You can only run fsck (properly) on file-systems that are *not* mounted read-write. Since the normal state of your system is to have the root partition mounted read-write, you will have to reboot your machine and do something special. You can either boot from a dedicated boot disk (e.g. tomsrtbt or possibly the SuSE install disk in rescue mode), in which case you don't need to mount the root FS at all, you can just check it unmounted, or you can use some Linux magic to ensure that when it comes back up, it has the root FS read-only. I'm not exactly sure what you would need to do this, so I can either suggest you look around the HOWTOs on www.linuxdoc.org, or failing that, someone else here more knowledgeable than myself might be able to help. Of course, there is always the possibility that if your machine is sufficiently stuffed, it might not come back up at all. That's why I suggested that it might need a bit of bravery... HTH... -- David Smith Work Email: Dave.Smith@st.com STMicroelectronics Home Email: David.Smith@ds-electronics.co.uk Bristol, England
participants (2)
-
Dave Smith
-
Nick Selby