Hi guys,

My linux just lost about a gig of memory .... I have a 40GB partition using fedora core1, but I can only see 38.7GB out of that and it keeps shrinking every time I reboot. I know what caused that - I had a power outage and a lot of files got messed up, had to run fsck several times to fix all problems and it found tons of dup bad blocks and inodes...

Does anyone know any other way to repair that?

Try e2fsck

Ok ... I tried it I'll post the output at the end but it did not change anything. I rebooted now it says journal is clean .. but still missing 1.5GB???


Thanks for the help though!


[root@unix up2date_client]# e2fsck /dev/hda6
e2fsck 1.34 (25-Jul-2003)
/dev/hda6 is mounted.

WARNING!!! Running e2fsck on a mounted filesystem may cause
SEVERE filesystem damage.

Do you really want to continue (y/n)? yes

/: recovering journal
Clearing orphaned inode 1229134 (uid=0, gid=0, mode=0100755, size=1012308)
Clearing orphaned inode 1655285 (uid=0, gid=0, mode=0100755, size=855388)
Clearing orphaned inode 1655284 (uid=0, gid=0, mode=0100755, size=44456)
Clearing orphaned inode 1148557 (uid=0, gid=0, mode=0100755, size=417012)
Clearing orphaned inode 1229266 (uid=0, gid=0, mode=0100755, size=7540)
Clearing orphaned inode 2098023 (uid=0, gid=0, mode=0100755, size=8324)
Clearing orphaned inode 2098022 (uid=0, gid=0, mode=0100755, size=19728)
Clearing orphaned inode 2098021 (uid=0, gid=0, mode=0100755, size=32352)
Clearing orphaned inode 2098020 (uid=0, gid=0, mode=0100755, size=5204)
Clearing orphaned inode 2098019 (uid=0, gid=0, mode=0100755, size=4516)
Clearing orphaned inode 2098018 (uid=0, gid=0, mode=0100755, size=7360)
Clearing orphaned inode 2098017 (uid=0, gid=0, mode=0100755, size=3824)
Clearing orphaned inode 2098016 (uid=0, gid=0, mode=0100755, size=18280)
Clearing orphaned inode 2098015 (uid=0, gid=0, mode=0100755, size=6392)
Clearing orphaned inode 2098014 (uid=0, gid=0, mode=0100755, size=34820)
Clearing orphaned inode 2098013 (uid=0, gid=0, mode=0100755, size=16976)
Clearing orphaned inode 2098012 (uid=0, gid=0, mode=0100755, size=55968)
Clearing orphaned inode 2098011 (uid=0, gid=0, mode=0100755, size=68096)
Clearing orphaned inode 2098010 (uid=0, gid=0, mode=0100755, size=30748)
Clearing orphaned inode 2098009 (uid=0, gid=0, mode=0100755, size=251072)
Clearing orphaned inode 2098008 (uid=0, gid=0, mode=0100755, size=14652)
Clearing orphaned inode 2098007 (uid=0, gid=0, mode=0100755, size=134108)
Clearing orphaned inode 2098006 (uid=0, gid=0, mode=0100755, size=85408)
Clearing orphaned inode 2098005 (uid=0, gid=0, mode=0100755, size=48220)
Clearing orphaned inode 2098004 (uid=0, gid=0, mode=0100755, size=43196)
Clearing orphaned inode 2098003 (uid=0, gid=0, mode=0100755, size=7380)
Clearing orphaned inode 2098002 (uid=0, gid=0, mode=0100755, size=4956)
Clearing orphaned inode 2098001 (uid=0, gid=0, mode=0100755, size=5640)
Clearing orphaned inode 2098000 (uid=0, gid=0, mode=0100755, size=15888)
Clearing orphaned inode 2097999 (uid=0, gid=0, mode=0100755, size=14056)
Clearing orphaned inode 2097998 (uid=0, gid=0, mode=0100755, size=25304)
Clearing orphaned inode 2097997 (uid=0, gid=0, mode=0100755, size=6140)
Clearing orphaned inode 1147054 (uid=0, gid=0, mode=0100755, size=783552)
Clearing orphaned inode 1081697 (uid=0, gid=0, mode=0104711, size=1947178)
Clearing orphaned inode 1081674 (uid=0, gid=0, mode=0100755, size=80156)
Clearing orphaned inode 524684 (uid=0, gid=0, mode=0100444, size=72496)
Clearing orphaned inode 524682 (uid=0, gid=0, mode=0100444, size=70121)
Clearing orphaned inode 524674 (uid=0, gid=0, mode=0100444, size=77488)
Clearing orphaned inode 672381 (uid=0, gid=0, mode=0100755, size=19356)
Clearing orphaned inode 672353 (uid=0, gid=0, mode=0100755, size=334356)
Clearing orphaned inode 672359 (uid=0, gid=0, mode=0100755, size=28692)
Clearing orphaned inode 672361 (uid=0, gid=0, mode=0100755, size=11260)
Clearing orphaned inode 672481 (uid=0, gid=0, mode=0100755, size=29412)
Clearing orphaned inode 672357 (uid=0, gid=0, mode=0100755, size=90836)
Clearing orphaned inode 672355 (uid=0, gid=0, mode=0100755, size=29144)
Clearing orphaned inode 672363 (uid=0, gid=0, mode=0100755, size=72004)
Clearing orphaned inode 672379 (uid=0, gid=0, mode=0100755, size=640244)
Clearing orphaned inode 672347 (uid=0, gid=0, mode=0100755, size=54520)
Clearing orphaned inode 672485 (uid=0, gid=0, mode=0100755, size=33920)
Clearing orphaned inode 672345 (uid=0, gid=0, mode=0100755, size=908376)
Clearing orphaned inode 672349 (uid=0, gid=0, mode=0100755, size=32576)
Clearing orphaned inode 672341 (uid=0, gid=0, mode=0100755, size=83160)
Clearing orphaned inode 196816 (uid=0, gid=0, mode=0100644, size=36648)
Clearing orphaned inode 196813 (uid=0, gid=0, mode=0100644, size=3692)
Clearing orphaned inode 196811 (uid=0, gid=0, mode=0100644, size=119152)
Clearing orphaned inode 590037 (uid=0, gid=0, mode=0100755, size=158432)
Clearing orphaned inode 819950 (uid=0, gid=0, mode=0100555, size=3380065)
Clearing orphaned inode 2032713 (uid=500, gid=500, mode=0100664, size=0)
Clearing orphaned inode 1802262 (uid=0, gid=0, mode=0100644, size=0)
/: clean, 175395/2146304 files, 3450996/4289347 blocks

hmmm... the only thing I can think about is... e2fsdk is nothing being optimized because the partition you are running is mounted. Besides being dangerous to do , some files/sectors may not be correctly allocated while the file system is mounted. What you could do is to get a LiveCD as knoppix, boot with it and then run e2fsck with the partition unmounted...

That's what I would try to do, but I never had so much lost of space with Linux file system to try it out myself

Good luck!

Ok ... I saw that too so I unmounted my linux partition and did another e2fsck but the results were tragic .. it did clean up a lot of inodes only now I cant boot the linux. It says Kernel Panic .. Try passing the correct init option ...
I've seen that before and u can easily fix it in rescue mode BUT rescue mode could not find/mount my linux partition: Error Mounting file system on hda6. Invalid argument.
Any help would be GREATLY appreciated!!

Are you missing 1.5 GB out of a 40 gigabyte drive? Are you aware that some people measure drive space in base 10 when unformatted and base 2 when unformatted?

Example:
40 gigabyte drive.....
40 x 10 (to the) 9 = 40,000,000,000
37.2529 x 2 (to the) 30 = ~40,000,000,000

So our numbers don't match up exactly, but could this be the source of you problem or were you aware of that fact and it is something else?

Nasty . Well, when it comes down to kernel panics, I hope two things:

1 - You don't hate me for being the responsible for it (maybe hate me a little bit)

2 - That you've backup-ed your data before playing with partitions .

Here is a thread with similar problems. I've searched google after your error message and everybody with that problem tried to compile a new kernel. Anyway, take a look:

http://www.linuxquestions.org/questi...03/11/3/115715

Best luck!

Oh no - I am not mad at u .. I mean it always gets worse before it gets better ... at least with linux . But thankfully all the files are still there checked that with explore2fs, and that rescue mode is not very smart I did a simple mount command and it mounted the partition just fine, ran e2fsck everything is clean .. now I have no idea y it gives that kernel panic. As far as kernel recompile I've done that before and its not a pleasant experience ..

And Benji I am well aware of that and I did have a true memory leak ... now that is solved I just cant get back in