<Solved>df -h

[gezza]

Hi to all,
I have 2012.08 running on an ASUS M5A97 UEFI motherboad.
It appears to be working well!!
BUT!!!!!!
df -h on the system shows 12GB used in '/' with 30GB available.
the /home folder shows 9.8 GB used and 27GB available.
This sound reasonable
Now --use mylivecd to create a squashfs since 20+GB to to big for the iso, the squashfs generated is 5.4 Gb in size.
This sounds reasonable, also.
Now create a usb booting system on a 8GB mem stick.
Having done this, I then boot that mem stick on a second machine having the following partition sizes:
root---49GB /home 29GB.
Do the install all goes well.
Now booting the new system:--df -h shows 6GB in root and 9.4GB in /home.
This is not reasonable.
The system still works the same, but something must be missing?
What has happened. I   have tried this 2 or 3 times and the results are the same each time.
Gezza
Addition:--
On locking further into the reinstalled system I notice the the root partition is 48.1GB the free space is 39.1GB.
The difference between these is NOT 6GB. So, again, what is going on?
Gezza

[Just17]

After rebooting the newly installed system, what does  df  show?

[gezza]

Hi Just17,
Now booting the new system:--df -h shows 6GB in root and 9.4GB in /home.
This is not reasonable.
Nothing new this morning, the system still says the same thing.
Gezza

[Just17]

Are the files from the remaster in   /   of the original from which the remaster was made?

The difference would appear to be similar to the size of the files to create the LiveUSB.

[muungwana]

i dont understand what is not reasonable.

root on original install says 12GB used, root on remaster says 6GB used.
reasonable explanation: remastering does not take all files and root.

home on the original install says 9.8GB used,home on remaster says 9.4GB in home
reasonable explanation: remastering does not take all files in in home partition.

What would have been odd is if remastered partitions where larger than their original and this is not the case.

[Just17]

root on original install says 12GB used, root on remaster says 6GB used.
reasonable explanation: remastering does not take all files and root.

keep remastering and reduce it to near nothing and still have a working install 

 there has to be an explanation for a reduction of nearly 6GB ......  and the most like, IMO, is the files for the creation of the LiveUSB.

  edit ........  unless there is about 6GBs of logs etc? ......

[gezza]

hi to all,
I have saved the markings from the 1St machine and imported them to the second machine.
There is apparently no difference in the 'synaptic' file system,  there were no updates to do.
No 'green tick'
I am now about to create another  (try) iso on the second machine.
Will keep you informed.
Gezza

[muungwana]

Its been forever since i did a remaster but i remember the remastering tool has a set of folders it excludes by default.

You can look at space usage of these folders as a potential clue of why the remastered image is much smaller that the original system.

[TheGhost]

Geeza, let's see if I get this correctly.

You have an installation in which "/" is using 12 Gb, and "/home" is using 9.8 GB; both partitions with extra spare space.

You then made a remaster of this installation using MyLiveCD.

Then you installed this remaster in a new system.
In this new system, "/" is showing only 6 GB used, and "/home" is showing 9.4 GB used.

Is this correct?

Then, nothing is wrong.
When you make the remaster, the script intentionally leaves out several folders, like "/var/cache", "/tmp", "/root/tmp", to mention a few. These folders have data that is temporal or relevant only to the particular installation, and you don't want them transported to a new, fresh installation.
In some cases, this data can be pretty large. For example, under some conditions you can have a lot of downloaded packages in "/var/cache/apt". Also, the thumbnail cache can be pretty big very easily.

So don't worry, if you used the MyLiveCD as usual, nothing is missing; all that was left out were temporal data that you don't need in a new install.

Hope this clarifies your doubt.

[wedgetail]

I was looking through some threads and accidentally came here.  I know the feeling when bytes don't seem to tally up.

Further to what TheGhost has written, you may be interested in some numbers for the main directories.

du -smh /* | sort -nr | head -150

or perhaps this one as it sorts in real high to low values, it is just above line minus human readable option -h

du -sm /* | sort -nr | head -150

A few lines from my system

[root@KDE-mini gert]# du -sm /* | sort -nr | head -10
du: cannot access `/proc/13666/task/13666/fd/3': No such file or directory
du: cannot access `/proc/13666/task/13666/fdinfo/3': No such file or directory
du: cannot access `/proc/13666/fd/3': No such file or directory
du: cannot access `/proc/13666/fdinfo/3': No such file or directory
12267   /home
4866    /media
3858    /usr
920     /opt
200     /var
158     /tmp
158     /lib
137     /root
38      /etc
20      /boot
[root@KDE-mini gert]#

It is a quick way of getting an idea of where the bulk of storage space is found.   

[Just17]

....  wondering if there could possibly be a huge space taken up by logs that are not remastered?

I have never had logs take much space here, but have seen posts about it causing problems ...

[gezza]

Hi Guy's,
Thank you all for you inputs.
I have just creates a new squashfs on the second system (6Gb used) and it has a size of 5.8GB using gzip.
The only program I installed was the installer.
I think the answer must be that there are a lot on files in tmp,var etc, that are not used by mylivecd.
muungwana , you must be correct, go to the top of the class.
Gezza