I have done some more tests, it seems that if I create a large file
with mkfile and interrupt the creation, the space that was allocated
is still occupied after I remove the file.
I'm gonna file this as a bug if no one has anything to add to this.
First I create a new pool, on that pool I cre
The "deferred free" indicates that these blocks are supposed to be freed at a
future time. A quick glance at the code would seem to indicate that this is
supposed to happen when the next transaction group is pushed. Apparently it's
not happening on your system ... presumably a bug.
--
This mess
On Nov 11, 2008, at 1:56 AM, Victor Latushkin wrote:
> Henrik Johansson wrote:
>> Hello,
>> I have a snv101 machine with a three disk raidz pool which
>> allocation of about 1TB with for no obvious reason, no snapshot,
>> no files, nothing. I tried to run zdb on the pool to see if I got
>
Henrik Johansson wrote:
> Hello,
>
> I have a snv101 machine with a three disk raidz pool which allocation
> of about 1TB with for no obvious reason, no snapshot, no files,
> nothing. I tried to run zdb on the pool to see if I got any useful
> info, but it has been working for over two hours
Hello,
I have a snv101 machine with a three disk raidz pool which allocation
of about 1TB with for no obvious reason, no snapshot, no files,
nothing. I tried to run zdb on the pool to see if I got any useful
info, but it has been working for over two hours without any more
output.
I know
