> If I understand you right it is as you said.
> Here's an example and you can see what happened.
> The sam-fs is filled to only 6% and the zvol ist full.

I'm afraid I was not clear with my question, so I'd elaborate, then.

It remains standing as: during this situation, can you write new data into 
SAMFS?
That is, can you fill it up from these 6% used? Or does the system complain 
that it 
can't write more data?

The way I see this discussion (and maybe I'm wrong), it's thus: 
* Your zvol starts sparse (not using much space from the pool, but with a 
"quota"
of 405Gb). That is, you don't have a "reservation" for these 405Gb to grab them
as soon as you create the zvol and not let any other datasets use this space.
* Your zvol allocates blocks from the pool to keep the data written by SAMFS, 
and
the disk space consumed from the pool grows until the zvol hits the quota (405Gb
of allocated blocks = 100% of quota).
* SAMFS writes data to the zvol and never tells the zvol that you deleted some 
files so these blocks can be unallocated.
* The zvol could release unused blocks - if it ever knew they are unused.

If this is all true, then your zvol now consumes 405Gb from the pool, and your 
SAMFS thinks it uses 6% of the block device with its 25Gb of saved files.

However, (and this is the salt of my question) the situation does not prevent 
you from writing the other 380Gb into the SAMFS without errors and complaints, 
and probably not changing the amount of space "used" in the ZFS pool and in the 
zvol dataset either. Is this assumption correct?

If it is, then I'd see the situation as a big inconvenience and a way to improve
interaction between SAMFS and ZFS as its storage (and/or fix a regression if
this worked better in previous releases). But it's not a bug per se.

However, if you can't write much data into the SAMFS now, it is definitely a 
bad 
bug.
-- 
This message posted from opensolaris.org
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Reply via email to