× 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.


  1.  Home
  2. MIDRANGE-L
  3. February 2013

Re: Migrating a file to SSD...

@Dan,
<snip>

Next time you modify a sector of that file paged in from it's old location, it'll page back out to SSD. In other words, 92% of that file hasn't been used since you changed the UNIT.

</snip>
So if this file is only added to the existing HDD allocation would never
decrease?
And the SSD would be increased only for the newly added records?
If I wrote a program (I'm not saying I'll do this) to update every record
in the file it would then be 100% on the SSD?

Thanks,

Rob
On 2013-02-28 11:08 AM, Dan Kimmel wrote:

Next time you modify a sector of that file paged in from it's old location, it'll page back out to SSD. In other words, 92% of that file hasn't been used since you changed the UNIT.

-----Original Message-----
From: [1]midrange-l-bounces@xxxxxxxxxxxx [[2]mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Robert Rogerson
Sent: Thursday, February 28, 2013 9:55 AM
To: [3]midrange-l@xxxxxxxxxxxx
Subject: Migrating a file to SSD...

Hi All,

Yesterday we attempted to migrate a large file (37 Gig) to the SSD using
CHGPF. When I check the file (DSPFD) it confirms that UNIT(*SSD) is now
changed.
This morning when I ran a query on syspartitiondisk it told my that 8% (33
Gig on HDD and 4 Gig on SDD) had been migrated. I was expecting this
percentage to be higher if not at 100%.

Am I misunderstanding? If I specify the UNIT on a file to be SSD does
that not mean that the entire file will be migrated to the SSD?

Thanks,

Rob
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: [4]MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: [5]http://lists.midrange.com/mailman/listinfo/midrange-l
or email: [6]MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at [7]http://archive.midrange.com/midrange-l.

References

Visible links
1. mailto:midrange-l-bounces@xxxxxxxxxxxx
2. mailto:midrange-l-bounces@xxxxxxxxxxxx
3. mailto:midrange-l@xxxxxxxxxxxx
4. mailto:MIDRANGE-L@xxxxxxxxxxxx
5. http://lists.midrange.com/mailman/listinfo/midrange-l
6. mailto:MIDRANGE-L-request@xxxxxxxxxxxx
7. http://archive.midrange.com/midrange-l

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
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.