[SGVLUG] File system corruption

[Emerson, Tom (*IC)]

> -----Original Message-----
> 
> Fortunately I've not had to create such a subject line often ...
> But I do have one that seems to be giving me troubles.
> 
> I had a 60gb drive that two partitions created.  it's on an older RH 
> distro, with a 2.4 kernal.
> 
> /dev/sdh1                     59.8    50.7     6.1        90%     
> /mnt/h1    
> /dev/sdh2                      9.1     0.0     8.6         1% 
>     /mnt/h2
> 
...
> After remounting (and later, rebooting), note below the final 
> directory 
> listing on the drive - instead of seeing a ton of .tif images, I'm 
> seeing those  'OS Boot' type files  !!
...
[moved from below]
> > [root at asdfzxcv rpinder]# cd /mnt/h1
> > [root at asdfzxcv h1]# ls
> > config-2.4.21-15.EL      initrd-2.4.21-15.ELsmp.img  
> > message.ja                  vmlinux-2.4.21-15.EL
> > config-2.4.21-15.ELsmp   kernel.h                    
> > System.map                  vmlinux-2.4.21-15.Elsmp
[etc...]

Well, according to the fsck output you posted, /mnt/h1 IS your "/boot"
partition, and therefore would have these so-called "OS boot" type
files:
 
> > [root at asdfzxcv sbin]# ./fsck -t ext2 /dev/sdh1
> > fsck 1.32 (09-Nov-2002)
> > e2fsck 1.32 (09-Nov-2002)
> > /boot: clean, 40/26104 files, 18352/104391 blocks 

----^^^^^-----

Besides...

> > [root at asdfzxcv sbin]# ./fsck -t ext2 /dev/sdh2 
> > e2fsck 1.32 (09-Nov-2002)
> > /dev/sdh2 is mounted.  
> >
> > WARNING!!!  Running e2fsck on a mounted filesystem may cause SEVERE 
> > filesystem damage.
> >
> > Do you really want to continue (y/n)? yes

Back up to the word SEVERE there and tell me again that you really said
YES...

> >
> > /: recovering journal
> >
> > Clearing orphaned inode 213208 (uid=500, gid=0, 
> mode=0140600, size=0) 
> > Clearing orphaned inode 213207 (uid=500, gid=0, 
> mode=0140600, size=0) 
> > Clearing orphaned inode 213206 (uid=500, gid=0, 
> mode=0140600, size=0)
> > /: clean, 136539/4341760 files, 775290/8673091 blocks
>