LinuxQuestions.org
Support LQ: Use code LQ3 and save $3 on Domain Registration
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices

Reply
 
Search this Thread
Old 11-15-2005, 09:09 AM   #1
menator
LQ Newbie
 
Registered: Nov 2005
Posts: 11

Rep: Reputation: 0
tar: Error exit delayed from previous errors


I get the following message when trying to tar up a directory:

tar: Error exit delayed from previous errors

Is there a way to find out what this error means? I was using tar -cvf and the files being added to the tar are listed on the screen. I guess there are so many that the 'previous errors' being refered to have scrolled off the screen.
 
Old 11-15-2005, 10:49 AM   #2
TBC Cosmo
Member
 
Registered: Feb 2004
Location: NY
Distribution: Fedora 10, CentOS 5.4, Debian 5 Sparc64
Posts: 355

Rep: Reputation: 43
Knee jerk guess would be that you're running out of space when you create the archive. But to see what the error is in reality, try using nohup: nohup [command] nohup.out
 
Old 05-31-2007, 12:22 PM   #3
effennel
LQ Newbie
 
Registered: Jun 2005
Posts: 2

Rep: Reputation: 0
Run as root

I found myself in a similar situation when backing up a website. I think the problem came from temporary files that the user running the tar could not access. Running it from root avoided this problem.

Hope it helps.
F
 
Old 10-09-2008, 05:20 PM   #4
alpha01
Member
 
Registered: Jul 2008
Location: Orange County
Distribution: Ubuntu/Debian, CentOS, RHEL, FreeBSD, OS X
Posts: 75

Rep: Reputation: 19
Quote:
Originally Posted by effennel View Post
I found myself in a similar situation when backing up a website. I think the problem came from temporary files that the user running the tar could not access. Running it from root avoided this problem.

Hope it helps.
F
I'm running in with root access and I still seeing this error message every time I want to create some tar archives.
 
Old 10-09-2008, 06:22 PM   #5
jailbait
Guru
 
Registered: Feb 2003
Location: Blue Ridge Mountain
Distribution: Debian Wheezy, Debian Jessie
Posts: 7,472

Rep: Reputation: 154Reputation: 154
Quote:
Originally Posted by menator View Post

tar: Error exit delayed from previous errors

Is there a way to find out what this error means? I was using tar -cvf and the files being added to the tar are listed on the screen. I guess there are so many that the 'previous errors' being refered to have scrolled off the screen.
What this means is that tar hit errors which were not bad enough for tar to fail immediately on hitting the error. tar kept going. Then when tar ends it says that it had errors but managed to run to completion.

You should be able to read all of the tar messages by scrolling up the terminal screen. Use the vertical scrollbar on the terminal window or use the scroll wheel on your mouse.

---------------------
Steve Stites
 
Old 10-10-2008, 12:14 PM   #6
alpha01
Member
 
Registered: Jul 2008
Location: Orange County
Distribution: Ubuntu/Debian, CentOS, RHEL, FreeBSD, OS X
Posts: 75

Rep: Reputation: 19
Quote:
Originally Posted by jailbait View Post
What this means is that tar hit errors which were not bad enough for tar to fail immediately on hitting the error. tar kept going. Then when tar ends it says that it had errors but managed to run to completion.

You should be able to read all of the tar messages by scrolling up the terminal screen. Use the vertical scrollbar on the terminal window or use the scroll wheel on your mouse.

---------------------
Steve Stites
lol "You should be able to read all of the tar messages by scrolling up the terminal screen. Use the vertical scrollbar on the terminal window or use the scroll wheel on your mouse."

Is this a sarcastic way to say that everyone on this thread are much of noobs?
 
Old 10-10-2008, 02:29 PM   #7
jailbait
Guru
 
Registered: Feb 2003
Location: Blue Ridge Mountain
Distribution: Debian Wheezy, Debian Jessie
Posts: 7,472

Rep: Reputation: 154Reputation: 154
Quote:
Originally Posted by alpha01 View Post

Is this a sarcastic way to say that everyone on this thread are much of noobs?
I am never sarcastic. I try to pitch the level of my reply to the knowledge level of the question. If I misjudged and seem to be talking down to you I apologize.

------------------
Steve Stites
 
Old 10-30-2008, 09:21 AM   #8
TextBrowserAddict
LQ Newbie
 
Registered: Aug 2005
Location: NY USA
Distribution: Slackware (12), Ubuntu, Crux?
Posts: 8

Rep: Reputation: 0
My error was solved using sudo (or root access).

As for "Should be able to read the message," I am recursing through a deep directory structure to create backups. If you do not have a large enough terminal buffer to read for the error, try running the command like this:

"tar cvzf somefile.tar.gz somedirectory/ anotherdirectory/ ... | less"

alternatively, use " > somefile.out" instead of " | less" and you'll have a more permanent record of the error.

Good luck
--Dragonlotus
 
Old 05-26-2010, 09:05 AM   #9
karlhubner
LQ Newbie
 
Registered: May 2010
Location: Connecticut
Distribution: Fedora
Posts: 1

Rep: Reputation: 1
I had to redirect standard error to get my error (broken symbolic link) to show up in the output.

"tar cvzf somefile.tar.gz somedirectory/ anotherdirectory/ ... 2>&1 | tee /tmp/myFileToAnnalizeLater.txt"

Hope this helps someone.
 
1 members found this post helpful.
Old 07-25-2012, 06:36 PM   #10
kechild
LQ Newbie
 
Registered: Aug 2007
Posts: 1

Rep: Reputation: 0
Thumbs up Resolved my concerns-thanks

Quote:
Originally Posted by jailbait View Post
What this means is that tar hit errors which were not bad enough for tar to fail immediately on hitting the error. tar kept going. Then when tar ends it says that it had errors but managed to run to completion.

You should be able to read all of the tar messages by scrolling up the terminal screen. Use the vertical scrollbar on the terminal window or use the scroll wheel on your mouse.

---------------------
Steve Stites
This answer resolved my concerns, thanks-
 
Old 02-12-2013, 03:15 AM   #11
perkon
LQ Newbie
 
Registered: Feb 2013
Posts: 1

Rep: Reputation: Disabled
You can redirect only the error output (stderr) to a log file.

Code:
tar cvzf something.tar.gz something 2>/path/to/tar.error.log
You can read more on the topic here www[dot]gnu[dot]org/software/bash/manual/bash.html#Redirections
 
Old 07-03-2013, 10:55 AM   #12
shashaness
LQ Newbie
 
Registered: Oct 2012
Posts: 1

Rep: Reputation: Disabled
Same problem, had files in directory which user did not have permissions on.

Had same problem. Indeed this did resolve my issue. I had a sub directory which was created using a different user. Removed the offending directory and every thing works as it should now. Thanks Steve

Quote:
Originally Posted by jailbait View Post
What this means is that tar hit errors which were not bad enough for tar to fail immediately on hitting the error. tar kept going. Then when tar ends it says that it had errors but managed to run to completion.

You should be able to read all of the tar messages by scrolling up the terminal screen. Use the vertical scrollbar on the terminal window or use the scroll wheel on your mouse.

---------------------
Steve Stites
 
Old 12-19-2013, 01:08 PM   #13
Robirt55
LQ Newbie
 
Registered: Nov 2012
Posts: 1

Rep: Reputation: Disabled
Quote:
Originally Posted by jailbait

You should be able to read all of the tar messages by scrolling up the terminal screen. Use the vertical scrollbar on the terminal window or use the scroll wheel on your mouse.
Best advice ever! Thanks this did actually help.
 
Old 12-19-2013, 06:43 PM   #14
sleepy_11
LQ Newbie
 
Registered: Apr 2008
Posts: 6

Rep: Reputation: 0
Quote:
Originally Posted by TextBrowserAddict View Post
My error was solved using sudo (or root access).

As for "Should be able to read the message," I am recursing through a deep directory structure to create backups. If you do not have a large enough terminal buffer to read for the error, try running the command like this:

"tar cvzf somefile.tar.gz somedirectory/ anotherdirectory/ ... | less"

alternatively, use " > somefile.out" instead of " | less" and you'll have a more permanent record of the error.

Good luck
--Dragonlotus
You can also try "tar czf foo.tgz ...", then only the error message will be printed, instead of lost in the long file list.

Just in case you want to know.

Sleepy
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
kde3.4 exit errors davidsrsb Slackware 2 04-24-2005 02:43 AM
Errors and warnings when I exit X cragwolf Slackware 5 09-01-2004 01:52 AM
tar error "Error exit delayed from previous errors" skdevnath Linux - General 1 03-05-2004 01:06 PM
tar: Error exit delayed from previous errors madenan Linux - Software 0 08-06-2003 02:38 PM
tar: Error exit delayed from previous errors x2000koh Programming 3 05-09-2003 04:38 AM


All times are GMT -5. The time now is 08:46 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration