Hi list,
I've did some tests and run into a very strange situation..
I created a zvol using "zfs create -V" and initialize an sam-filesystem
on this zvol.
After that I restored some testdata using a dump from another system.
So far so good.
After some big troubles I found out that releasing files in the
sam-filesystem doesn't create space on the underlying zvol.
So staging and releasing files just work until the "zfs list" shows me a
zvol with 100% usage although the sam-filesystem was only filled up to 20%.
I didn't create snapshots and a scrub did show any errors.
When the zvol was filled up even a sammkfs can't solve the problem. I
had to destroy the zvol ( not zpool ).
After that I was able recreate a new zvol with sam-fs on top.
Is that a known behaviour? .. or did I run into a bug?
System:
SAM-FS 4.6.85
Solaris 10 U7 X86
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
