Okay... Deep breath...
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
Okay, I've booted with the rescue disk and am logged in. As root. I checked the man pages and Suse's man how to's. I get this: You can try to fix the filesystem with e2fsck (Here we are taking the ext-2-Filesystem. It is the standard one.) e2fsck is able to seek your disk for bad sectors, and to mark them so that they will never we written again. Attention: You have to be aware, that e2fsck can't cause any wonder. In some cases (specially if there are hardware problems or severe damaged filesystems) the use of e2fsck may lead to an aggravation of your problem. The user handbook contains the complete manual-page of e2fsck. Please read it, and execute the program from the rescue system (boot from CD or from SuSE installation disk and start the rescue system. Don't mount the concerned disk, see manual). The command to repair the filesystem is (here we will take: /dev/sda5 as the damaged one): e2fsck -f -c -y /dev/sda5 Would anyone here be able to tell me whether this is the proper procedure for me? I'm concerned about the e2fsck and not fsck. Thanks in advance, An increasingly desperate Nick
, 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
-- 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
1. You can only run fsck as root. 2. You can only run fsck (properly) on file-systems that are *not* mounted read-write.
The command to repair the filesystem is (here we will take: /dev/sda5 as the damaged one): e2fsck -f -c -y /dev/sda5
Would anyone here be able to tell me whether this is the proper procedure for me?
I would do: e2fsck -f -c -v /dev/hda8 If that fails, badblocks not found, try e2fsck -f -v /dev/hda8 Remove -v if you dont want it to be verbose (show lots of info). If it works you should make a backup and perhaps invest in a new disk. Also I recommend you to split the disk into more paritions. I would suggest you to make the following separate parttitions: / /usr /usr/local /tmp /var /opt /home /boot /Stefan
Stefan: What advantage does it have to partition the disk that way instead of: / /boot swap Regards, Julian -----Original Message----- From: Stefan Nilsen [mailto:stefan.nilsen@telia.com] Sent: Wednesday, April 03, 2002 11:36 AM To: suse-linux-e@suse.com Subject: Re: Fwd: Re: [SLE] Suse 7.2 eating disk space
1. You can only run fsck as root. 2. You can only run fsck (properly) on file-systems that are *not* mounted read-write.
The command to repair the filesystem is (here we will take: /dev/sda5 as the damaged one): e2fsck -f -c -y /dev/sda5
Would anyone here be able to tell me whether this is the proper procedure for me?
I would do: e2fsck -f -c -v /dev/hda8 If that fails, badblocks not found, try e2fsck -f -v /dev/hda8 Remove -v if you dont want it to be verbose (show lots of info). If it works you should make a backup and perhaps invest in a new disk. Also I recommend you to split the disk into more paritions. I would suggest you to make the following separate parttitions: / /usr /usr/local /tmp /var /opt /home /boot /Stefan -- 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 _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
On Tue, Apr 02, 2002 at 12:29:51PM -0400, cheo7811@yahoo.com wrote:
Stefan:
What advantage does it have to partition the disk that way instead of:
/ /boot swap
1. If one partition gets badly corrupted, you haven't lost the whole FS. 2. If one partition fills up completely (as it has in this case), it doesn't fill up the whole disk - /var, /home, /tmp are likely to grow with less control; if something goes nuts and starts writing loads of logs to /var/log, you don't end up with the system dying because there's no disk space anywhere. 3. It's easier to move bits of the filesystem around onto other (new, larger) disks. -- David Smith Work Email: Dave.Smith@st.com STMicroelectronics Home Email: David.Smith@ds-electronics.co.uk Bristol, England
On Wed, Apr 03, 2002 at 05:23:03PM +0200, php@nickselby.com wrote: [snip]
The command to repair the filesystem is (here we will take: /dev/sda5 as the damaged one): e2fsck -f -c -y /dev/sda5
Would anyone here be able to tell me whether this is the proper procedure for me?
It looks about right. Personally, I'd use the fsck option which is 'do nothing, but tell me about any problems' first. Once you've done that, you can decide whether to try to fix the problems. As to whether the general consensus is that your disk is fried - possibly not. I'm just guessing based on the evidence. Lots of FAT errors and trying to read beyond the end of the device seem to be a bit suspect. I'm not an expert, but if I were in your situation, I'd be fscking furiously by now. If there's nothing wrong, then fsck will tell you that, and you'll have come away with the knowledge of what to do when you think that your disk has been corrupted. I'd still suggest printing and looking at your partititon table. -- David Smith Work Email: Dave.Smith@st.com STMicroelectronics Home Email: David.Smith@ds-electronics.co.uk Bristol, England
Thanks everyone! I've run it and it modified the filesystem. Now my only problem is trying to discover why after losing those HUGE log files, my HD is still 96% full. Thanks, nick At 05:44 PM 4/3/2002 +0100, you wrote:
On Wed, Apr 03, 2002 at 05:23:03PM +0200, php@nickselby.com wrote: [snip]
The command to repair the filesystem is (here we will take: /dev/sda5 as the damaged one): e2fsck -f -c -y /dev/sda5
Would anyone here be able to tell me whether this is the proper procedure for me?
It looks about right. Personally, I'd use the fsck option which is 'do nothing, but tell me about any problems' first. Once you've done that, you can decide whether to try to fix the problems.
As to whether the general consensus is that your disk is fried - possibly not. I'm just guessing based on the evidence. Lots of FAT errors and trying to read beyond the end of the device seem to be a bit suspect. I'm not an expert, but if I were in your situation, I'd be fscking furiously by now. If there's nothing wrong, then fsck will tell you that, and you'll have come away with the knowledge of what to do when you think that your disk has been corrupted.
I'd still suggest printing and looking at your partititon table.
-- 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 07:17:03PM +0200, php@nickselby.com wrote:
Thanks everyone!
I've run it and it modified the filesystem.
Did you do a bad blocks check as well? Did fsck find anything?
Now my only problem is trying to discover why after losing those HUGE log files, my HD is still 96% full.
How did you delete the files? Did you just rm them or use cat? If you used rm, they may not actually be gone yet. Don't forget that 'du' will give you a listing of disk usage per directory. -- David Smith Work Email: Dave.Smith@st.com STMicroelectronics Home Email: David.Smith@ds-electronics.co.uk Bristol, England
participants (4)
-
Dave Smith -
Julian Sanchez M. -
Nick Selby -
Stefan Nilsen