X
PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 26 Nov 2015 03:21 AM by  anon
File_UNTAR writting error
 2 Replies
Sort:
You are not authorized to post a reply.
Author Messages

anon



New Member


Posts:
New Member


--
26 Nov 2015 03:21 AM
    Hi, I'm having problems with the FILE_UNTAR from IDL (8.4). I'm working with the Cluster Science Archive (CAS) and the data there is compressed in .tar.gz format. As I try to untar the data the following message appears in the console: % Uncompress c:\Users\jromero\IDLworkspace84\TDAS\spedas_1_00\idl\Jose\CSA_data\jromerol1245913.tar.gz 125839360 bytes % CSA_Download_20151126_1112/C2_CP_FGM_FULL/C2_CP_FGM_FULL__20011001_000000_20011002_000000_V140306.cdf, 62815401 bytes % FILE_UNTAR: Error writing file c:\Users\jromero\IDLworkspace84\TDAS\spedas_1_00\idl\Jose\CSA_data\CSA_Download_20151126_1112\C2_CP_FGM_FULL\C2_CP_FGM_FULL__20011001_000000_20011002_000000_V140306.cdf, skipping... % CSA_Download_20151126_1112/C1_CP_FGM_FULL/C1_CP_FGM_FULL__20011001_000000_20011002_000000_V140306.cdf, 63015272 bytes % FILE_UNTAR: Error writing file c:\Users\jromero\IDLworkspace84\TDAS\spedas_1_00\idl\Jose\CSA_data\CSA_Download_20151126_1112\C1_CP_FGM_FULL\C1_CP_FGM_FULL__20011001_000000_20011002_000000_V140306.cdf, skipping... % Total 0 files, 125830673 bytes % Time elapsed: 0.61500001 seconds. Which is actually weird, because the gzip decompression is done as can be seen in the first line, and even the contents are read, however the files cannot be extracted and written, so in the end it doesn't work at all. I''ve tried almost everything, changing the output directory (figuring there could maybe be administrator problems) but always the same problem. Moreover, I've tried to untar another .tar.gz file created with the IDL procedure FILE_TAR, and actually, the FILE_UNTAR worked for such a file, so I figured, there were any admin problems for writting at all. I hope someone can give me a solution, thanks in advance.

    Zachary Norman



    Basic Member


    Posts:173
    Basic Member


    --
    29 Nov 2015 08:58 PM
    Hi Jose, What do you see if you include the verbose keyword in your call to FILE_UNTAR? Here is an example of how you would do that: FILE_UNTAR, 'file.tar', /VERBOSE Also, if you specify the directory that the file gets written out to, do you still have an error? To do that you would specify a second argument like this: FILE_UNTAR, 'file.tar', 'C:\Users\your_user_name\Desktop', /VERBOSE -Zach (VIS)

    Deleted User



    New Member


    Posts:
    New Member


    --
    30 Nov 2015 01:45 AM
    Hi Zachary, First of all, thank you for your reply! Actually, the information there is the info already using the /VERBOSE keyword. If I don't put the keyword, then obviously less information is shown in the console but the result is the same, the files are not written in the output directory. Moreover, I also used the /LIST keyword, which basically simulates the decompression without writting the files in the output directory (in this case I can even get the file paths in a string using the corresponding keyword), so apparently there's a problem while writting the files, not while reading. I've also tried to change the output directory (as you suggested in your reply) and even an output folder is properly created if necessary, but the data cannot be written (same error). As I said in my post. I tried with another .tar.gz files and it works perfectly, so I know there are no admin problem issues to write on the output directory (That was the first thing that came to my mind). Just to make everything even a bit weirder, I tried in the last days to do the same one time and another getting the same error one time after another, but one time it miraculously extracted the data in the directory, but afterwards it went back to the same error and never did it again (without making any change at all). Thanks for your response, if someone has any idea what the problem can be, please let me know.
    You are not authorized to post a reply.

    Forums Products IDL