- run an iostat -x on each block device during each test
- reformat a bit to make room for the iostat reports

    . NOT bump the module refcount when a new peer is found

    . Clean up all open connections and autoconnect route table entries on
      module unload.

- more carefully cleanup to avoid error messages in early cleanup

  moving to the right side
- ext3_ext_find_goal() takes into account offset of a block to be allocated
  (thanks to Andreas for smart idea)

  cache-aliasing problems
- ext3_forget() should be used in conjuction with ext3_free_blocks()

NOTE: 2.4.24 + extents + batching block allocation passes data-consistency
      tests now (at least I haven't seen problems for many hours of testing)

r=shaver

rewrite new_uuid function for lmc

up for it.
r=coop

- they back-ported PDE from 2.6, which broke our compat macro
- they changed direct_IO method to pass struct file instead of struct inode

Both are now checked in portals/archdep.m4 directly instead of as a version
number check so we don't need to worry about other releases doing the same.

  lots of tweaking to be done yet

    work-around for missing #defines that are now in the QSW release).

  possible deadlock
- locking in extent's ioctl added
- ext3_ext_walk_space() drops bh's references in path before finding
  next extent

NOTE: dbench and syntetic tests work OK in vmware for many hours

tests by itself and give detailed results.

b=2516

b=2578

b=2591
r=zab,shaver

  - fixed goal selection
  - more bits of batching allocation

r=shaver

Deal with the double-quote,single-quote, and backslash in batchfile of "lmc --batch batchfile".

b=2370
r=zab

b=2503
r=zab,shaver

b=2464