Gill Agreed! HFS/zFS With DFDSS should be made to honor user allocation specifications for data set restore. Typical work around is to reallocate and manually copy the zFS. Last PMR with IBM on this topic just gave me the run around. So, that is why I am asking this brain trust the question.
Sent from my iPhone On Sep 1, 2012, at 19:29, Paul Gilmartin <paulgboul...@aim.com> wrote: > On Sat, 1 Sep 2012 12:20:19 -0400, Doug wrote: > >> Very large multi volume zFS has in the past, failed allocation trying to >> allocate the primary extent which was larger than the physical volume. >> Mainly curious what a good work-around would be. Does not happen often. >> > Is DFDSS quite so stupid that when copying a multi volume data set > it will invoke extent consolidation logic paying no heed to the maximum > capacity of the target volume, derive a primary extent size larger than > that capacity, then fail attempting to allocate that primary extent? > > Sounds like a serious design blunder that ought to be remedied. > >> On Aug 31, 2012, at 10:50, "Jousma, David" wrote: >> >>> Just saw this. Not sure why you would want to "prevent" extent >>> consolidation if you are copying your ZFS. > > -- gil > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
