hammer2 - Initial synchronization thread
authorMatthew Dillon <dillon@apollo.backplane.com>
Sun, 29 Mar 2015 07:19:15 +0000 (00:19 -0700)
committerMatthew Dillon <dillon@apollo.backplane.com>
Sun, 29 Mar 2015 07:25:40 +0000 (00:25 -0700)
commit5ceaaa82d9b0c583bcf1980d314831ca60e51ee8
tree8d2c49f1a2aae7a89e79613029c779f9c0c4330f
parent72b78560f664235e0eb1be2fb5d750bd0baff568
hammer2 - Initial synchronization thread

* Add infrastructure for a per-PFS synchronization thread.  This primary
  thread will be responsible for background synchronization out-of-sync
  masters, slaves, and other elements of a PFS.  There will also be another
  thread for background bulkfree and dedup operations.

  In this commit, basic thread creation, destruction, freeze, and unfreeze.
  (Freezing and remastering is required when new nodes are added to a PFS
  or existing nodes are deleted).

* Define new cluster flags indicating the synchronization state.

* pfs-create and snapshot were not properly flagging the inode as being
  a PFS, which confused the on-mount recovery scan code.

* Update TODO.
sys/vfs/hammer2/Makefile
sys/vfs/hammer2/TODO
sys/vfs/hammer2/hammer2.h
sys/vfs/hammer2/hammer2_cluster.c
sys/vfs/hammer2/hammer2_ioctl.c
sys/vfs/hammer2/hammer2_syncthr.c [new file with mode: 0644]
sys/vfs/hammer2/hammer2_vfsops.c