I moved my Linux system from a 20gig HD to a 60gig (cp /dev/hda* /dev/hdb* to existing bigger partition then I switched HD) but some progs (like df) still see my old HD size... but some (like fdisk or parted) see the real size (or at least the real starting-ending cylinder).
Is that because the system haven't perform a check yet?
Or because the ext3 journal contains information about the old hd?

Sorry, I think the question is very lame but I feel tired of searching in man/how for tonight... and I don't want to do something stupid.

Maybe using df --sync option would return the correct size??? If you do get this figured out, or if it "auto" fixes itself, please let me/us know, I will probably be doing this soon.

Thanks

df works on file systems, not on partitions. You filesystem is the same size, your partition size has changed.

Regards

I think what you actually wanted to do here is plug in the new drive and create partitions and filesystems on it, then put the data on the old partition on it.

maybe use tar to copy it over

mkdir /tmphd
mount /dev/hd?? /tmphd

cd /

or the folder to copy

then
--------------------------------------------------
"suggested by mlp68"

tar c . | tar --same-owner -xpC /tmphd

--------------------------------------------------

or maybe

cp -dbR

or

cp -a

Herm ok... Is There a way to change the size of my file system (the device) without creating a new system? I tried cp -R / /(the new hd mounted somewhere) but linux can't do this, I have some bug copying the directory /proc and because the new hd is mounted, when I copy / it create an infinite loop until the hd is full... I don't really want to start a fresh install on the new hd, then move the data.

I dunno, there are no easy command to force linux to increase the size of a device?

trying to think of how I did it once a little while back

I booted from a root floppy, mounted both drives and did it that way

or just copy all folders in / except /proc



then just create a /proc folder on the new partition

if you use cp -R it will follow the links, are you sure that's what you want?

I resize mine all the time when working on my image that I am building, to make it smaller.


I just create a filesystem and fill it with zero's then mount the two images on a loop device and cp -dbR the files from the old one to the new one.



I can't remember ever making a filesystem on a partition with data before, not sure what will happen.

FINALLY!!!!
I have sucessfully resized my partition, it's a REAAAAL pain, I never tought it was to be so hard. Anyways... I created my new partition then I reinstall a new Slackware 8.0 system... I made this system operational then I copy all my old data in... the REAL problem was to copy data without corrupting the system (I killed Slack 4 time in trying), for example, in copying a new library over a "old" (giving by the installation) one. Anyways now it's working near good as it was before except few bugs.

Example:
-Kde losts all my custom font... I suppose this was not saved in the home directory.

-All Gtk Progs have a white background instead of a gray... I really dunno why... I will try updating my gtk library, I suppose all progs take the ones that come with Slack by default.

-All my users was lost so I will have to recreate them all. It's annoying but I just have a dozen of users (most of them are ftp users) so it's not a real problem 'til I have their home directory.

-Kde bugs often... I suppose I still have few old Kde 2.2.1 and QT libs somewhere... I will have to check about this... Did someone know exactly what happen to kde 2.2.1 files when I update to 2.2.2 ? Are these files replaced?

Hum, in conclusion, resizing a *nix partition is a real painful experience.
MasterC, if you don't REALLY need resizing, please don't try it!!!