On Feb 15, 2007, at 6:08 AM, Robert Milkowski wrote:
Hello eric,
Wednesday, February 14, 2007, 5:04:01 PM, you wrote:
ek> I'm wondering if we can just lower the amount of space we're
trying
ek> to alloc as the pool becomes more fragmented - we'll lose a
little I/
ek> O performance, but it should limit this bug.
Do you think that zfs send|recv for such file systems could help for a
while? (would it defragment data?)
If you were able to send over your complete pool, destroy the
existing one and re-create a new one using recv, then that should
help with fragmentation. That said, that's a very poor man's
defragger. The defragmentation should happen automatically or at
least while the pool is online.
In the absence of a built-in defragger and without a fix for 6495013,
i think the best thing you could do is either add more storage or
remove some data (such as removing some old snapshots or move some
unneeded storage to another system/backup). Not sure if either of
those are applicable to you.
Should note, ZFS isn't the only COW filesystem that hits this
problem. In WAFL's case, i believe they hit this same problem around
90% capacity but are very nice about detecting it and reporting back
to the admin.
eric
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
