grarpamp a écrit :
Yep, the cp /dev/null <file> works to truncate. So I can deal with it.
Yep, everything is snapshotted.
Yep, this is a Sun issue not a FreeBSD one. FreeBSD should just stay
current with the versions and the minimum needed to port... fbsd dev
time is valuable elsewhere.
I do remember reading about copy on write, d-oh :)
ZFS should probably keep track of the largest extent needed to effect
any given operation and reserve that behind the scenes. If it took n
bytes to create something sans data, it'll probably take n bytes to
modify it.
Quotas and things might work though the user under quota might run
into the same problem. Who knows.
Thx CW, et al.
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Just tried it on a test pool. (on md devices). 7.2-RELEASE
[carenath] /testpool# zfs list -r -o name,used,avail,refer,quota testpool
NAME USED AVAIL REFER QUOTA
testpool 156M 0 156M 156M
testp...@test 22.6K - 153M -
[carenath] /testpool# ll -h
total 159295
-rw-r--r-- 1 root wheel 15M Jul 30 11:29 random
-rw-r--r-- 1 root wheel 61M Jul 30 11:35 random2
-rw-r--r-- 1 root wheel 77M Jul 30 11:37 zero
-rw-r--r-- 1 root wheel 2.6M Jul 30 11:44 zero2
[carenath] /testpool# rm zero
rm: zero: Disc quota exceeded
So quota workaround doesn't quite works.
It could possibly be an issue where quota limited users fill up their
allowed space : they can free space by themselves.
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
