* problem: SMB_VFS_KERNEL_FLOCK immer ausgeführt ohne option!

* update write time : ins cookie. TESTS

* step 10: durable v2: checks, create guid etc
  - ==> pass more down to vfs durable ops

* resilient and persistent ...
=> later

* scavenger timer

* document (manpage)

* conditions for durable:
  - no posix locks
  - no kernel oplocks
  - no kernel share modes
  - checks at disconnect/reconnect, not at generating cookie
  - reconnect only if cookie came from disconnect!
  - durable for streams? => no

* more info into cookie:
  - stat info of file?!

* tests:
  - initial_allocation_size
    - value in reconnect create response the same as initial create response
    - or current value?
  - reconnect to a read only file writing
    (while creating a read only file)
  - rename: open, rename, check getinfo(path), disconnect, reconnect, check getinfo(path)

--------

* test: dh2q / dh2c vs. persistent on/off matrix
  implement correct semantics
  (e.g. persistent granted, but dh2c w/o persistent)
* test/fix: combination of create blobs
* reconnect: check file name

DONE:

* clean up serverid and implement disconnected state
* cookie/reconnect: as VFS op? or as FSCTL?