A Really Weird File System Problem

atheist · 07-02-2004, 05:27 PM

Doing a "df -hT" the other day I recieved this output:

Code:

Filesystem    Type    Size  Used Avail Use% Mounted on
/dev/hda3  unknown    2,9G   63M  2,7G   3% /
tmpfs        tmpfs    507M     0  507M   0% /dev/shm
/dev/hda1     ext2     61M  3,2M   55M   6% /boot
/dev/hda5     ext3    2,9G  1,4G  1,4G  50% /usr
/dev/hda6     ext3    1,9G  201M  1,6G  12% /var
/dev/hda7     ext3    1,9G   33M  1,8G   2% /opt
/dev/hda8     ext3    9,4G  5,0G  4,0G  56% /home
/dev/hda9     ext3    9,4G  467M  8,5G   6% /www
/dev/hda10    ext3    1,9G   33M  1,8G   2% /tmp
/dev/hda11     xfs    4,8G  1,5G  3,4G  30% /downloads
/dev/hdc1      xfs    233G  196G   38G  84% /ichi
/dev/hdb1      xfs    111G   33G   79G  29% /rei

Now as you've probably noticed, the root partition is not doing too good... I remember doing a "df -hT" some time ago and it reported the Used part to be around 630M. The filetype is ext3... or was. I don't know what's happening really. I also did a du -csh on all the stuff that's not on a specific partition and got about 600M usage. Does anyone have any idea of what's going on here?

I thought maybe a file system check would fix this but I'm not sure how to perform one. It's done automatically after some mounts but it's got to be checked upon booting since it's the root partition and I'm not sure how to do that... Would that solve anything? And how would I schedule a fsck to be done on the next boot?

Thanks.

p-static · 07-02-2004, 07:43 PM

You could boot into tomsrtbt(i forgot the link, but you can google it), and run e2fsck on it. Try running e2fsck -c, to check for bad blocks on the filesystem. Of course, before any of this, make sure you didn't do something dumb like rm -rf a bunch of stuff accidentally. (It happens to the best of us

Fiddling with partitions might also do that.

mritch · 07-02-2004, 09:19 PM

if your root filesystem is still writeable just cd / and "touch forcefsck", reboot and it will perform a fsck on reboot.

sl mritch.

atheist · 07-02-2004, 10:48 PM

Thanks for your replies.

I meant to say this earlier... but here goes. Nothing seems to be wrong at all and everything is working pretty well. I even rebooted to make sure it wasn't something that I did or deleted that harmed the system.
mritch, thanks, that's exactly what I was looking for.

tvn · 07-03-2004, 08:46 AM

Quote:

Originally posted by mritch
if your root filesystem is still writeable just cd / and "touch forcefsck", reboot and it will perform a fsck on reboot.

sl mritch.

can I do this with the reiserfs filesystem ?

mritch · 07-03-2004, 08:55 AM

maybe.. i don't know - but you can dry - it won't cause any problems.

please report if you've success.

ls mritch.

atheist · 07-03-2004, 03:59 PM

It did run fsck on my root partition and reported some errors that were fixed but it still gives me the same unknown file system and 63M usage... If it matters, here's my /etc/fstab:

Code:

# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>               <dump>  <pass>
/dev/hda3       /               ext3    errors=remount-ro       0       1
/dev/hda2       none            swap    sw                      0       0
proc            /proc           proc    defaults                0       0
/dev/fd0        /floppy         auto    user,noauto             0       0
/dev/cdrom      /cdrom          iso9660 ro,user,noauto          0       0
/dev/hda1       /boot           ext2    defaults                0       2
/dev/hda5       /usr            ext3    defaults                0       2
/dev/hda6       /var            ext3    defaults                0       2
/dev/hda7       /opt            ext3    defaults                0       2
/dev/hda8       /home           ext3    defaults                0       2
/dev/hda9       /www            ext3    defaults                0       2
/dev/hda10      /tmp            ext3    defaults                0       2
/dev/hda11      /downloads      xfs     defaults                0       2
/dev/hdc1       /ichi           xfs     defaults                0       2
/dev/hdb1       /rei            xfs     defaults                0       0
/dev/hdb2       none            swap    sw                      0       0

I have NO IDEA what's going on here, so any help at all will be greatly appreciated.

Thanks.

mritch · 07-03-2004, 05:34 PM

have you updated lately? there is quite a similar post at distros/debian tvn posted (same case). it looks like it's debian specific, but i can't tell what it is either.

sl mritch.

atheist · 07-03-2004, 09:21 PM

Thanks, I'll check out that post. And, yes, I try to be up to date. "apt-get update && apt-get -uy dist-upgrade" once a week.

tvn · 07-04-2004, 02:01 AM

http://www.linuxquestions.org/questi...24#post1026824 < try what I did , it works for me .

amosf · 07-04-2004, 02:12 AM

Is the filesystem just set wrong? Check it with fdisk and see if it's set to type 83. If it's right there then it might be something with the journal that it's not knowing whether it's ext2 or ext3?

atheist · 07-04-2004, 11:45 AM

"rm /etc/mtab && ln -s /proc/mount /etc/mtab" seemed to fix this for me... kinda...

Code:

[16:43 root@rakka etc]# df -hT
Filesystem    Type    Size  Used Avail Use% Mounted on
rootfs      rootfs    2,9G   65M  2,7G   3% /
/dev/root     ext3    2,9G   65M  2,7G   3% /
tmpfs        tmpfs    507M     0  507M   0% /dev/shm
/dev/hda1     ext2     61M  3,2M   55M   6% /boot
/dev/hda5     ext3    2,9G  1,4G  1,4G  50% /usr
/dev/hda6     ext3    1,9G  106M  1,7G   6% /var
/dev/hda7     ext3    1,9G   33M  1,8G   2% /opt
/dev/hda8     ext3    9,4G  3,9G  5,1G  44% /home
/dev/hda9     ext3    9,4G  467M  8,5G   6% /www
/dev/hda10    ext3    1,9G   33M  1,8G   2% /tmp
/dev/hda11     xfs    4,8G  1,2G  3,7G  25% /downloads
/dev/hdc1      xfs    233G  208G   25G  90% /ichi
/dev/hdb1      xfs    111G   35G   77G  32% /rei

I now have two entries for /...

kingka · 07-08-2004, 03:26 AM

hello,

I'm having the same problem, using all ext3 partitions (for /home /shares and /boot) and only the root partition is giving problems. Tell me if I'm wrong but does it really matter to change /etc/mtab ? If /proc/mount is fine than there should be no performance loss, also since nobody is having any real troubles. The only issue is that df -hT or mount gives the wrong information? Please correct me if I'm wrong.

kingka · 07-08-2004, 03:36 AM

http://linux.derkeiler.com/Mailing-L...4-07/0012.html

This messageboard told me a debian bug report has been issued on the 1st of july. I also read a few things about /etc/mtab . Making a symbolic link to /proc/mount should be no problem, only that "some extra information" (I found no specifications) in /etc/mtab is lost. The problem is, as I guess, that at boot-time /etc/mtab doesn't get the information from /proc/mount and the file isn't up-to-date.