Hi,

I started playing around with HAMMER a bit and noticed some bugs.  I
know HAMMER is currently in alpha state, but I assume the report could
be helpful :)

pc12909!root:/mnt # mount | grep hammer
hammertest on /mnt (hammer, local)
pc12909!root:/mnt # df -h | grep hammer
hammertest     498M    50M   448M    10%    /mnt

If I create a file on a HAMMER fs it isn't displayed by "ls".
If I run "ls <filename>" I can see the file:

pc12909!root:/mnt # ls -l
total 0
pc12909!root:/mnt # ls -l kernel
-r-xr-xr-x  2 root  wheel    18M Apr  9 17:47 kernel*
pc12909!root:/mnt # touch foobar
pc12909!root:/mnt # ls -l
total 0
pc12909!root:/mnt # ls -l foobar
-rw-r--r--  1 root  wheel     0B Apr  9 17:54 foobar

Doing operations like move/remove fails with an unknown error:

pc12909!root:/mnt # mv kernel kernel.2
mv: rename kernel to kernel.2: Unknown error: -557872388
pc12909!root:/mnt # rm kernel
rm: kernel: Unknown error: -557872292

Accessing the content of the file works:

pc12909!root:/mnt # cat kernel > kernel.2
pc12909!root:/mnt # md5 kernel kernel.2
MD5 (kernel) = 6eb537b59a0f049e6979c48354d6f377
MD5 (kernel.2) = 6eb537b59a0f049e6979c48354d6f377

The following messages appeared in dmesg during the tests:
hammer_freemap_alloc 2000000006800000
hammer_freemap_alloc 2000000007000000
hammer_freemap_alloc 2000000007800000
hammer_freemap_alloc 2000000008000000
hammer_freemap_alloc 2000000008800000
hammer_freemap_alloc 2000000009000000

Extracting a big tarball failed with the following messages in dmesg
repeating over and over.  The extracted tarball is smaller than the
overall size of the volume, so I don't filled it up.

[...]
hammer_freemap_alloc 2000000011000000
undo zone's next_offset wrapped
undo zone's next_offset wrapped
undo zone's next_offset wrapped
undo zone's next_offset wrapped
hammer_freemap_alloc 2000000011800000
[...]

Regards

	Matthias