Re: [BackupPC-devel] V3 vs V4 migration (size and inodes)

[Craig B. <cba...@us...>]

Bill,

That's interesting data.

I'm not sure why the inode use goes up.  Has it stayed at the higher level
after BackupPC_nightly has run?  Is the old V3 pool now empty?

Craig

On Mon, Mar 27, 2017 at 3:24 AM, Bill Broadley <bi...@br...> wrote:

>
> I had a 2.7TB pool for 38 hosts, actual size after deduplication and
> compression.
>
> I just upgraded to 4.0.1 and did a V3 to V4 pool migration.
>
> The storage penalty was pretty small, about 2% or 52GB.
>
> The inode overhead was substantial, just over a factor of 2.  In my case
> it was
> 25348763 inodes (around 11% of the ext4 default) to 51809068 (around 22%
> of the
> default).
>
> If you are upgrading you might want to ensure that your V3 inode usage is
> less
> than 50% of what the filesystem is capable of.
>
> The above migration tool 52 hours or so on a RAID 5 of 4 disks on a server
> that's a few years old.
>
> To watch I graphed it over time:
>   http://broadley.org/bill/backuppc.png
>
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> BackupPC-devel mailing list
> Bac...@li...
> List:    https://lists.sourceforge.net/lists/listinfo/backuppc-devel
> Wiki:    http://backuppc.wiki.sourceforge.net
> Project: http://backuppc.sourceforge.net/
>