On 9/11/06, Matthew Ahrens <[EMAIL PROTECTED]> wrote:
> would the user be held acountable for the space used by the extra
> copies?
Doh! Sorry I forgot to address that. I'll amend the proposal and
manpage to include this information...
Yes, the space used by the extra copies will be accounted for, eg. in
stat(2), ls -s, df(1m), du(1), zfs list, and count against their quota.
> so if a user has a 1GB quota and stores one 512MB file with
> two copies activated, all his space will be used?
Yes, and as mentioned this will be reflected in all the space accounting
tools.
Yuck. This would be terribly confusing for typical end-users. I
would say that statvfs() should munge the numbers such that f_bfree
and f_bavail are divided by ncopies. Else, applications that need
this information will need to know *way* too much about the file
system. For example, consider the checks performed by
setup_install_server that comes with the Solaris media. That script
does a du on the media that it came from followed by a df on the
target. Should that script really need to be modified for the case
where the source and/or target are on zfs with ncopies != 1?
This part of the feature would keep me from using it anywhere that
there is any chance of being space constrained and I have 1 or more
users that can't read the man page for zfs then explain how it is
different than at least one competing file system.
Mike
--
Mike Gerdts
http://mgerdts.blogspot.com/
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
