Start a Conversation

Unsolved

This post is more than 5 years old

408

November 29th, 2006 14:00

Post-Upgrade DiskXtender problem retrieving files

We recently upgraded from a very old version of DX to the most recent.

Now, about 80% of the tapes in the library take up to 20 minutes to retrieve a 385k file. The other 20% work fine.

The only common denominator between the 80% is that the system marked them all "full" during the upgrade. These tapes show free space and free clusters as "0", even though their should be more that that left over.

I have tried to remove the "Media Full" checkbox, but it goes back as full as soon as the tape is accessed.

For an example, tape 503 is marked full (light blue). It is an LTO1 tape with

Total bytes: 99,914,203,136
Written bytes: 99,914,203,136
Free bytes: 0

Tape 504 is not marked full, and is listed as:

Total bytes: 99,999,547,392
Written bytes: 99,989,430,272
Free bytes: 10,117,120


Tape 503 took 2 hours to retrieve 10 ~385k files.

Tape 504 can do the same in about a minute.

I tried to compact 503 over to LTO1, and after a quick calculation, found that it would take 180 days per tape. So, a brisk 30 years or so to compact my entire library over to LTO3 =)

I am wondering if the headers are bad on these tapes, or if some configuration is wrong in DX.

I am contemplating a low-level copy of 503 over to a brand new LTO3 tape and then promoting the LTO3 tape... does anyone see a problem with this?

Any help is GREATLY appreciated!!

56 Posts

December 4th, 2006 13:00

This one seems a bit odd. I'm wondering if the files on tape 503 aren't marked for Direct Read (which can take a very long time for tape media, due to the need to spin up, rewind, seek, etc...). You can right-click on a file on 503, and get the DiskXtender File Properties for the file, and look on the Settings Tab to see if Direct Read is enabled or disabled.

Other than that, I'd recommend opening a Service Request with DiskXtender Support, to see if someone on the team can troubleshoot this via a WebEx and try to find the cause for the performance issue.

Thanks!

-Mike
No Events found!

Top