Maintenance of mirrored filesystem
John R. Shannon
john at johnrshannon.com
Fri Dec 15 07:24:40 PST 2017
I setup hammer filesystems on identical disk drives. I created a number
of PFS that are mirrored. Over time, the storage allocation on the
MASTER has remained constant while it continues to grow on the SLAVE as
shown in the following:
MASTER 5588G 1456G 4132G 26% /master
SLAVE 5588G 2775G 2813G 50% /slave
/master/pfs/@@-1:00002 5588G 1456G 4132G 26% /master/backups/dns
/master/pfs/@@-1:00001 5588G 1456G 4132G 26%
/master/backups/colleen
/master/pfs/@@-1:00003 5588G 1456G 4132G 26%
/master/backups/domain0
/master/pfs/@@-1:00004 5588G 1456G 4132G 26% /master/backups/imap
/master/pfs/@@-1:00005 5588G 1456G 4132G 26% /master
...
Am I missing a maintenance step that needs to be performed on the slave?
My daily run output shows:
HAMMER maintenance:
cleanup / - handle PFS#0 using /var/hammer/root
snapshots - run
prune - run
rebalance - run..
reblock - run....
recopy - skip
cleanup /build - handle PFS#0 using /var/hammer/build
snapshots - run
prune - run
rebalance - run..
reblock - run....
recopy - skip
cleanup /master - handle PFS#0 using /var/hammer/master
snapshots - run
prune - run
rebalance - run..
reblock - run....
recopy - skip
cleanup /slave - handle PFS#0 using /var/hammer/slave
snapshots - run
prune - run
rebalance - run..
reblock - run....
recopy - skip
cleanup /master/backups/dns - handle PFS#2 using
/var/hammer/master/backups/dns
snapshots - run
prune - run
rebalance - run..
reblock - run....
recopy - skip
... (for each PFS)
The mounts all represent the master PFS as the slave PFS are not mounted.
--
John R. Shannon
john at johnrshannon.com
More information about the Hammer
mailing list