Moving $HOME to a separate data partition?

[Bo Berglund]

On Fri, 15 Oct 2021 09:27:45 +0100, Colin Law <clanlaw at gmail.com> wrote:

>> I am done now, home is moved over to sda3 and it is working Ok.
>> It seems like a forgotten mount of another disk partition into ~/test was
>> what
>> screwed up rsync.
>>
>> I still have the original /home as /home_backup.
>>
>> But I will free space by removing /home_backup
>> and then shrinking the system
>> partition sda1 to be able to further expand the home partition sda3 using
>> GParted.
>
>
>If you remove it then it may reorder the partition numbers which can mess
>up mounts if you have used sda1/2 rather than uuids. If you don't want that
>then you can delete the contents and shrink it down to 10 MB or similar

First, the home_backup is the original /home folder renamed before mounting the
copy now in sda3.

So it is *inside* sda1 and therefore sda1 is 200 GiB in size from the first
shrink when I made space for a new partition sda3 to hold the home only.

What I will do is 
sudo rm -r /home_backup
This should bring available space up by about 150 GiB.

Next I will fire up the boot CD with GParted and shrink the system partition
down to some 30 GiB or so.

If I subtract the currently used space on home_backup from all used space on
sda1 I get 14 GiB, so that is what the system uses right now...
Shrink to 30 GiB will make it about 50% used, which I think is OK for a system
drive when all data resides elsewhere.

This will leave about 160 GiB of empty space in the drive but will simplify
future backups of the system drive considerably. It only uses 14 GiB now when I
subtract the space for /home_backup.

Except Apache SVN hosts its 6 GiB of repositories in /var/lib/svn, which is not
transfered to home.
So Ubuntu itself seems to use only 8 GiB...

And I *always* use the UUID in mount commands in fstab.


-- 
Bo Berglund
Developer in Sweden