Printable View
Wee problem when trying to uncompress a file.
tar xvzf <filename> gives me a 'Cannot open: no such file or directory' message.
The files are attempting to uncompress as they are scrolling down the screen but this message appears at the end of each one!
This is a legit file (original driver disc), so im stuffed!
Anyone any ideas?
Cheers
r3b007
What is the actual file name? Does it have a Z or a gz at the end? if so, type gunzip filename first then do a tar -xvf filename.
Anyway, this is all I can offer up without the exact filename.
Hope this helps.
Two things come to mind:
- Path
- location (write permissions)
An ls -l of the file(s) as well as exact command would be nifty. I've seen it once before with a student and it related to the fact that they had no write permissions as well as how they were attempting to download the file (using lynx)
Might be that you need to update your extracting program. Give that a try.
Backtrails
The files extension is tgz, so therefore tar xvzf should uncompress this.
MsMittens: Im in the directory where the file is located, so my PATH shouldnt really matter should it?
An ls -l of the file tells me it is executable by all.
Also ive tried uncompressing as root but i get the same thing.
I could be doing something real dumb here but im lost.
Any ideas?
r3b007
Try an absolute path. Maybe path issues?
Could do either
tar -xzvf ./filename.tgz
OR
tar -xzvf /path/to/filename.tgz
if tar is not working the command gunzip filename.tgz will extract it.
Yeah, you are right, the command *should* work, however, did you try the gunzip command anyway?
Ive tried both of those commands already MsMittens but no joy!
I have also tried gunzip too guys so no joy there either...
Hrmm.. disk space?? I dunno.. I'm at a loss at this point..
<WAGs - Wild Ass Guessing starts>
unless it's not finding the tar command and gunzip commands!?
Trojan'd commands maybe?
<WAGs stop>
LOL, im the same!
Disc space = 40GB
The tar and gunzip commands seem to be found as the individual files of the tarball are being displayed, its just telling me theres no such file or directory!
Bleh!
Cheers all for trying to help anyways ;)
r3b007
is it a long file extension r3b00+ ? i had simmilar problems with long filename's too
so say for example it was the opera tar ball i downloaded and the file was called opera-23-34-545-6justverylong.tgz
it would have problems extracting it so try this as useing opera as an example tar zxvf opera*tgz and if that doesent work try downloading the tar ball again something could have went wrong if you were on a proxy or something and the file wast fully downloaded
p.s what you been up to PM me
very strange if its origanal try surfing the net for the same file maybe?download and replace
there is possibly another error message before all the "no such file or directory". "No such file or directory" when untaring probably means it failed to create a directory somewhere down the line.
Try viewing the error messages with |less or something, like
Look for the *first* error message, it will be much more helpful.Code:tar -zxf blah.tgz 2>&1 |less
Possible causes:
- Permission denied
- Trying to create a directory when a file of the same name already exists
or something else
Check out the disk space.Because tar -xvzf creates a new directory.If u have enough disk space then do the unzip command and then tar-xvzf with absolute path.
By the way can I know thw exact filename
r3b00+,
When you in that directory, try to check if that file you've downloaded in there. Let's say your file is A.tgz
#cd /home/r3b00+ <<< I assuming your file in this directory
# ls | more or you can use ls | grep A.tgz
if not showing your A.tgz that's mean you cd to wrong directory and you cannot uncompressing your A.tgz file.
Just my opinion though
Cheerss
Annya
hrmm.. A few things come to mind.
1) First redownload it. Sometimes these things just happen.
2) Try finding the file from another ftp
3) Open it with vi and take a peek at it. Maybe its actually a source code. Funny things happen on day 10 of strait coding.. lots of coffee.. and no sleep. Maybe the coder just messed up the file type.
4) try rpm'n it. (see above for explanation)
5) try seeing if its a binary (see above)
6) like MsM said.. check to make sure your tar commands are not aliased or trojan'd somewhere.
7) Check permissions again... chmod 777 it again just for kicks
8) check the paths again...
9) try other compression utilities
10) try messin with it in windows.. scarier stuff has happened before
11) write the author :D
well, thats about it from me.. good luck.. ;)
xmaddness
One more thing that you could do is to check the contents of the file using the file command. It'll tell you what type of file it is. Try file <filename>.
Cheers,
cgkanchi
Another (lame) option..
If you have a filemanager (like konqueror or that gnome thing or even MidnightCommander (mc) ) you could try to open the file with that ( by clicking, double-clicking or pressing [Enter] on the file)
I have experienced that sometimes files that wouldn't open with tar xzvf or zjvf could be opened that way...
ark (kde archiver) works too sometimes.. ( ark /path/to/filename )
It's a lame workaround, but sometimes it works..
also, could the .tgz be a slackpack or some other kind of package) ( installpkg should work then)
Rename the file.tgz to file.tar.gz then try to decompress it using:
gzip -d file.tar.gz
If this doesn't work then it's not a gzip compressed file. Keep in mind that tar usually does the archiving and another program is usually used for (de)compressing the archive. If you've tarred and gzipped an archive on a 64 bit OS, you'll have problems running tar -xzf on a 32 bit OS. If you're still having trouble, send me the file, I'll have a look. :)
Thanks for all the replies guys, as always appreciated for trying to help!
One of our respected members has sorted this problem for me by renaming it to .tar.gz, for which im extremely grateful ;)
BTW, the original file name was pdq-Kyo-km-2.2.6.tgz
Cheers
r3b007