No,
just did "zfs create -V".
and I didn't change the size of the zpool or zvol at any time..
regards,
Tobias
Jim Klimov schrieb:
Concerning the reservations, here's a snip from "man zfs":
The reservation is kept equal to the volume's logical
size to prevent unex
Concerning the reservations, here's a snip from "man zfs":
The reservation is kept equal to the volume's logical
size to prevent unexpected behavior for consumers.
Without the reservation, the volume could run out of
space, resulting in undefined
> 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 int
Hi Jim,
first of all I'm sure this behaviour is a bug or has been changed
sometime in the past, because I've used this configuration a lot of times.
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
Hello tobex,
While the original question may have been answered by posts above, I'm
interested:
when you say "according to zfs list the zvol is 100% full", does it only mean
that it
uses all 20Gb on the pool (like a non-sparse uncompressed file), or does it
also imply
that you can't write int
Hi Dean,
may you provide more infos about that?
Are you able to send me a bug description for a better understanding?
Is there a patch available, or do I have to use a previous patch of sam-qfs?
Thanks in advance...
Tobias
Dean Roehrich schrieb:
On Mon, Jul 27, 2009 at 02:14:24PM +0200,
On Mon, Jul 27, 2009 at 02:14:24PM +0200, Tobias Exner wrote:
> 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
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
