zpool list doesn't reflect pool usage stats instantly. Why?
This is no different to how UFS behaves.
If you rm a file, this uses the system call unlink(2) to do the work which is
asynchronous.
In other words, unlink(2) almost immediately returns a successful return code to
rm (which can then exit, and return the user to a shell prompt), while leaving a
kernel thread running to actually finish off freeing up the used space. Normally
you don't see this because it happens very quickly, but once in a while you blow
a 100GB file away which may well have a significant amount of metadata
associated with it that needs clearing down.
I guess if you wanted to force this to be synchronous you could do something
like this:
rm /tank/myfs/bigfile && lockfs /tank/myfs
Which would not return until the whole filesystem was flushed back to disk. I
don't think you can force a flush at a finer granularity than that. Anyone?
regards,
--justin
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
