i increased the size of my /usr partition (using System Commander) from 2.3 Gb to 2.8 and my Mandrake Partitioning software sees this but...

when i run DF it still shows 2.3 Gb....

is there any way to tell whatever DF looks at, that it's really dealing with 2.8 ?

thanks

- perry

thanks for getting back to me on the partition descrepancy error...

jesus christ, i'm some glad it wasn't the gawd damned jehovah witnesses i was asking you about, i'd be up shit creek then...

i mean it's not like we are on a linux community board or anything where somebody somewhere should know about this stuff...

in the meantime, does anybody know whether or not fsck is to be used on ext3 type partitions....

thanks anyway, it's been good talking to myself.

- perry

Perry, if you know how to use Google, you know that your question has been asked before and the answer is not explicit. If you know how to do the LQ search, you also know that your question has been asked several times here, without a good answer. There is a reason for that. You would see that Redhat has a way of resizing, and that GNU Parted is the only recommended tool for resizing EXT partitions. Most likely, system commander has not written the size changes properly to the superblock, and your size difference is not recognized because of that. It can't hurt to fsck it, but I don't think that'll do anything to help your size problem. Do it anyways. Its an EXT tool. EXT3 is EXT2 with a journal (when you make one you just add the "-j" switch and its EXT3).

There's your answer.

You didn't have to make a religious slur to get an answer. You should consider yourself luck that after only a day, somebody bothered to answer you at all, since the term "resize linux partition "df"" returned over 200 hits with the LQ search button and I couldn't find anything resembling a solution in 15 minutes of reading (of course you did this before asking your question, right?). You've got over 300 posts under your belt, so you've been here awhile. You know how this works. Try not to be so impatient, discriminatory, or rude. Pehaps your next tough question will actually get an answer.

If I were you, I'd try to back up the partition and reformat the space. Then, copy the directory back. Good luck.

I will second vectordrake's comments. Additionally, keep in mind that simply posting a question here at LQ does not guarantee or entitle you to an answer -- you should know that. I think most LQ'ers go out of their way to be helpful, but the fact is that not every single post gets resolved. That's just life, man. If I didn't know any better it sounds like you think the LQ community is conspiring to deliberately withholding information from you, which is absurd. Just in case it hasn't occurred to you before, nobody owes you an answer just because you post a question. Sorry. Good luck with the project. -- J.W.

sorry about the none-sense, i was just having one of those days

i appreciate the help!

- perry

turns out my /usr had some damaged inodes which might explain why it could not detect the new partition size. in trying to run fsck i had to go reboot using a maintenance disk...

once there i did the following:

e2fsck -f /dev/hda9

and then a

resize2fs /dev/hda9

that seemed to nail it.

as mentioned the first command detected a number of missing inodes, i was suprised and a bit concerned but the utility seemed to know just what to do....

i'm wondering now if i should set something up where e2fsck can run a -f regularly on startup... i do notice on boot up it does perform a check, but not necessarily go into fix mode....

oh well, at least it's looking good at the moment - thanks again all for your help *and patience)

cheers

- perry

Congrats on getting it all figured out perry. And I'll say sorry too if my post came across as scolding, it's just that sometimes you'll see a post and just scratch your head thinking "Sheesh - what's the deal with this guy?"

Anyway, like I said I'm glad it all worked out in your favor.

As for running fsck on a scheduled basis, I'd say that's debatable; I'm pretty much of the "if it ain't broke" line of thinking. Just my 2 cents. -- J.W.