Recently I had a system with an incomplete snapshot. The
destination system hung in the middle of a zfs recv. It ended up
taking about 75 GB of kernel memory to destroy that incomplete
snapshot. Yet destroying another copy of that same snapshot took less
than 6 GB of memory.
Does a destroy of a snapshot take a different path through the
code than destroying an incomplete snapshot (as part of a zpool
import) ?
Disclaimer: I am a sysadmin and NOT a developer. I _could_ look at the
source, but I'm not sure it would tell me what I am looking for.
--
{--------1---------2---------3---------4---------5---------6---------7---------}
Paul Kraus
-> Senior Systems Architect, Garnet River ( http://www.garnetriver.com/ )
-> Sound Coordinator, Schenectady Light Opera Company (
http://www.sloctheater.org/ )
-> Technical Advisor, Troy Civic Theatre Company
-> Technical Advisor, RPI Players
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
