:Hi,
:
:I hope this question has not been implicitly answered before, but how
:does Hammer handle quotas? Filesystems like XFS and ZFS maintain quota
:information internally so that a quotacheck after a system crash does
:not take ages. It seems to me that Hammer could manage quotas as a
:part of its cluster allocation strategy. Is this the case?
:
:TIA,
:RIggs
Theoretically a transaction id can be stored along with the quota state
and the quota state can be updated on the fly when a cluster gets
recovered. I wasn't planning on implementing quotas in HAMMER for 2.0
but it's definitely possible to do it without requiring a rescan.
-Matt
Matthew Dillon
<dillon@backplane.com>| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Linus Torvalds | Linux 2.6.27-rc8 |
| Christoph Lameter | Re: Major regression on hackbench with SLUB (more numbers) |
| Mike Travis | Re: [RFC 00/15] x86_64: Optimize percpu accesses |
git: | |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | [GIT]: Networking |
| Hugh Dickins | Re: [bug?] tg3: Failed to load firmware "tigon/tg3_tso.bin" |
