× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



You could probably get it to work in a fashion. When you create your
network storage spaces "mount" them so they use particular disk. Of
course, you would have multiple storage spaces for each guest. Then on
your guests you could use unit preference for storing the data on the
SSD's. The only things you couldn't be using on the guest is the actual
*SSD option for unit preference - you'd have to specify a particular
number(s). And none of the other imbedded things to help balance between
SSD and HDD.

For more information read up on how to put stream file data (aka ifs data
outside of /qsys.lib and certain other directories) on to SSD's.

However, is unit preference, outside of the *SSD option, respected
anymore? Or has that been deprecated? Meaning you can put a number in
there for compatibility reasons but it's ignored? So if I had a 10k HDD
as unit 1 and a 15k HDD as unit 2 if I put UNIT(2) on my CRTPF would it
really put it on unit 2 or would it say, "thanks for telling me that but
I don't give a rip"? The online help for UNIT says:
integer
A value ranging from 1 through 254 is equivalent to specifying
*ANY. A value of 255 is equivalent to specifying *SSD.
I guess that clarifies it. It is deprecated. So I don't think this
"trick" would work to get certain guest partition data on to SSD's. Ignore
my first paragraph - it's BS.


Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.