Harry Putnam writes:
> [Note: This is a repost of question posted about 1.5 days ago that
> has never appeared on the group.. at least not on my server (gmane).
> Sorry if it ends up being a double whammy]
Apparently I missed two informative answers by:
Henrik J. Bob F.
Thanks for the input...
[Note: This is a repost of question posted about 1.5 days ago that
has never appeared on the group.. at least not on my server (gmane).
Sorry if it ends up being a double whammy]
Working from a remote linux machine on a zfs fs that is an nfs mounted
share (set for nfs availability on zfs server, m
On Mon, 22 Feb 2010, Henrik Johansson wrote:
You will not see the on disk size of the file with du before the transaction
group have been committed
which can take up to 30 seconds. ZFS does not even know how much space it will
consume before writing out
the data to disks since compression might
On Feb 21, 2010, at 7:47 PM, Harry Putnam wrote:
>
> Working from a remote linux machine on a zfs fs that is an nfs mounted
> share (set for nfs availability on zfs server, mounted nfs on linux);
> I've been noticing a certain kind of sloth when messing with files.
>
> What I see: After writin
Working from a remote linux machine on a zfs fs that is an nfs mounted
share (set for nfs availability on zfs server, mounted nfs on linux);
I've been noticing a certain kind of sloth when messing with files.
What I see: After writing a file it seems to take the fs too long to
be able to display
