> Tar does an alphabetical sort of the top level of the directory you're > tarring up. When it hits a directory, it descends down that tree and > repeats the process (alphabetical sort, descend directory, etc.) until > all files/directories are completed in that branch, then goes back up > and continues. It's not like find (which sorts on inode numbers by default). Is there a way to mimic it, with ls or du? =========================================================================== Patrick DUPRÉ | | email: pdupre@xxxxxxx Laboratoire de Physico-Chimie de l'Atmosphère | | Université du Littoral-Côte d'Opale | | Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44 189A, avenue Maurice Schumann | | 59140 Dunkerque, France =========================================================================== > Sent: Monday, July 17, 2017 at 7:55 PM > From: "Rick Stevens" <ricks@xxxxxxxxxxxxxx> > To: users@xxxxxxxxxxxxxxxxxxxxxxx > Subject: Re: tar failure > > On 07/16/2017 11:07 AM, Patrick Dupre wrote: > > Hello, > > > > Thank for the response. > > I do not know what is the previous error. > > I am checking the list, but is not going to tell what is the error. > > I cannot scroll back > > > > I was speaking about the logic of the order of the file > > are taken from the directory, > > Not alphabetic ordering > > not date ordering. > > > > Then, I cannot guess what is missing. > > It is an emergency archive, because the disk is failing. > > Tar does an alphabetical sort of the top level of the directory you're > tarring up. When it hits a directory, it descends down that tree and > repeats the process (alphabetical sort, descend directory, etc.) until > all files/directories are completed in that branch, then goes back up > and continues. It's not like find (which sorts on inode numbers by default). > > Without a log of the transaction, there is absolutely no way we can > offer help as to what the error was. This is precisely why you should > use the "v" flag to tar and save stdout/stderr to a logfile, something > like: > > tar cvf name-of-tar-file.tar * >/some/dir/tar.log 2>&1 > > It's the only way to ensure you capture errors. Same thing goes for > rsync, cpio, gzip, or virtually any stream-type archiver. Find the > "verbose" flag and redirect stdout/stderr to a log file. > > What was it Reagan said? "Trust, but verify!" > > >> Sent: Sunday, July 16, 2017 at 7:55 PM > >> From: "Samuel Sieb" <samuel@xxxxxxxx> > >> To: users@xxxxxxxxxxxxxxxxxxxxxxx > >> Subject: Re: tar failure > >> > >> On 07/16/2017 10:52 AM, Patrick Dupre wrote: > >>> I got: tar: Exiting with failure status due to previous errors > >>> How can I finish the process? > >>> I do not want to restart the tar, I only would like to tar the rest > >>> (directory). > >> > >> It usually doesn't stop at the error, that's why it says "previous > >> errors". It's just telling you that somewhere along the way there was > >> an error, but it finished anyway. > >> > >>> I do not see the logic that tar uses to create the archive > >>> Can I guess this logic? and only tar the missing ? > >> > >> I don't understand this question. If you wanted to know what happened, > >> you'll have to either scroll back or save the output while it is running. > >> _______________________________________________ > >> users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx > >> To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx > >> > > _______________________________________________ > > users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx > > To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx > > > > > -- > ---------------------------------------------------------------------- > - Rick Stevens, Systems Engineer, AllDigital ricks@xxxxxxxxxxxxxx - > - AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 - > - - > - "I'd explain it to you, but your brain might explode." - > ---------------------------------------------------------------------- > _______________________________________________ > users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx > _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
