Richard Elling wrote:
On Aug 28, 2009, at 12:15 AM, Dave wrote:
Thanks, Trevor. I understand the RFE/CR distinction. What I don't
understand is how this is not a bug that should be fixed in all
solaris versions.
In a former life, I worked at Sun to identify things like this that
affect availability
and lobbied to get them fixed. There are opposing forces at work: the
functionality
is correct as designed versus availability folks think it should go
faster. It is difficult
to build the case that code changes should be made for availability when
other
workarounds exist. It will be more fruitful for you to examine the
implementation and
see if there is a better way to improve the efficiencies of your
snapshot processes.
For example, the case can be made for a secondary data store containing
long-term
snapshots which can allow you to further optimize the primary data store
for
performance and availability.
-- richard
This is unfortunate, but it seems this may be the only option if I want
to import a pool within a reasonable amount of time. It's very
frustrating to know that it can be fixed (evidenced by the S10U6 fix),
but won't be fixed in Nevada/OpenSolaris - or so it seems.
It may be filed as an RFE, but in my opinion it is most definitely a bug.
--
Dave
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
