Re: [hosers-talk] ext3 filesystem is funky

[Jeff Schroeder <jeffs@xxxxxxxxxxx>]

At 06:27 PM 3/2/2003, Joel Uckelman wrote:
> Thus spake Jeff Schroeder:
> > I just found this weird problem in my /tmp filesystem and I can't figure
> > out how to fix it short of recreating it.  Basically it says that it is
> > full, but it isn't.
> >
> > Linux Phantasm 2.4.16 #4 Sun Dec 2 23:31:20 EST 2001 i686 unknown
> >
> > [root@Phantasm tmp]# df
> > Filesystem           1k-blocks      Used Available Use% Mounted on
> > /dev/hda3               194449     67787    116622  37% /
> > /dev/hda2                23333      6920     15209  32% /boot
> > /dev/hda10             2806664    423520   2240572  16% /home
> > none                    192376         0    192376   0% /dev/shm
> > /dev/hda8               497829    461982     10145  98% /tmp
> > /dev/hda5              2522048   1364476   1029456  57% /usr
> > /dev/hda7               497829     39462    432665   9% /var
> > /dev/hda6               497829     15912    456215   4% /var/spool
> >
> > [root@Phantasm tmp]# df -i
> > Filesystem            Inodes   IUsed   IFree IUse% Mounted on
> > /dev/hda3              50400   18166   32234   37% /
> > /dev/hda2               6024      34    5990    1% /boot
> > /dev/hda10            356928    1320  355608    1% /home
> > none                   48094       1   48093    1% /dev/shm
> > /dev/hda8             128520      16  128504    1% /tmp
> > /dev/hda5             320640   84497  236143   27% /usr
> > /dev/hda7             128520    1207  127313    1% /var
> > /dev/hda6             128520      88  128432    1% /var/spool
> >
> >
> > As you can see, the inodes are fine on /tmp, but it shows as 98% full. but
> > only 15k is being used.
> >
> > [root@Phantasm tmp]# du -h /tmp
> > 12k     /tmp/lost+found
> > 1.0k    /tmp/.font-unix
> > 1.0k    /tmp/.X11-unix
> > 15k     /tmp
> >
> > Argh, can anyone help?
> >
> > jeff
>
> I'm guessing that you've already fscked it?
>
> That's weird. Since it's /tmp, it won't be hard to nix it an recreate it, 
> though it would be nice to know how that came about.


Nope, didn't fsck it yet because I need to unmount it.  Can't unmount it 
unless I reboot (because the kernel uses it).  Didn't want to reboot unless 
it was the only way.  I guess I'll do that and see.  Worst case, I'll have 
to remake it.  What's the command to create an ext3 fs again?  I'm used to 
'mke2fs'.

BTW, do you know the mailing list for ext3, so I can find out if this is a bug?

jeff

_______________________________________________
hosers-talk mailing list
hosers-talk@xxxxxxxxxxx
http://lists.ellipsis.cx/mailman/listinfo/hosers-talk