William, No clue. I'd be interested in seeing the output from both of the df commands (with no options) before and after, with the non-root file system mounted on /mnt in both cases.
Mark Post -----Original Message----- From: Scully, William [mailto:[EMAIL PROTECTED]] Sent: Saturday, August 24, 2002 9:43 PM To: [EMAIL PROTECTED] Subject: Enlarging Root File Space This is interesting. We have a SuSE 2.4 server and the root file space is 98% full. So I allocated a new 1000 cyl disk (the old one was 650 cyls) and copied all the materials to it using tar. (I based my work on the very helpful how-to found at: http://www.linuxvm.org/Info/HOWTOs/movefs.html ) I checked my work by doing a df and I see that the disk, mounted at /mnt, is 63% full. (I also ran zipl with a newly created config file to make the new disk bootable.) So far so good. So I shutdown normally. But when I swap the two disks (that is, I change the minidisk address is the directory entry 201->20E, 20E->201) and reboot, the new root surprisingly is THE SAME SIZE AS THE OLD! I'm sure I swapped the disks, because /proc/dasd/devices and #CP Q V DASD show the new minidisk in place and the new size. But when one does a df I see the new, larger disk is still 98% full. So I back off. I swap 20E->201 and 201->20E and reboot. I mount the new disk at /mnt and df again. The disk is now magically 63% full again. How can this be?
