hammer2 - Bug fixes in allocator and chain_next, rename
authorMatthew Dillon <dillon@apollo.backplane.com>
Thu, 22 Mar 2012 07:12:43 +0000 (00:12 -0700)
committerMatthew Dillon <dillon@apollo.backplane.com>
Thu, 22 Mar 2012 07:12:43 +0000 (00:12 -0700)
commit8e12e3c905580716a7a87e739f4a364678ad2e83
tree1f9371e44765d00e15d6a6d286918a2ba6e50d7a
parent01eabad4d93a8dc8f0f01a6209b384b1e010bb8c
hammer2 - Bug fixes in allocator and chain_next, rename

* The addition of a larger segment to allocate blocks out of caused
  the allocator to mishandle 64K requests, resulting in non-optimal
  I/O performance.

* Fix a bug in hammer2_chain_next() which was causing truncations to
  crash.

* Rename operations would sometimes not recursively mark the chain
  MODIFIED1 or would not mark the updated inode MOVED, causing
  data loss.

* Replace HAMMER2_CHAIN_WAS_MODIFIED with a local variable.
sys/vfs/hammer2/hammer2.h
sys/vfs/hammer2/hammer2_chain.c
sys/vfs/hammer2/hammer2_freemap.c
sys/vfs/hammer2/hammer2_vnops.c