|
|
Post by pharrisire on Jan 2, 2012 12:59:46 GMT -5
The last three backups have failed to extract - no indication of any problem while
making the backups.
I copied the errors in case they'll help:
31DEC11
An error occured .....
Command Line output
/usr/local/bin/gtar: Archive value -549755813856 is out of time_t range -2147483648..2147483647
/usr/local/bin/gtar: Ignoring unknown extended header keyword `SCHILY.dev'
/usr/local/bin/gtar: Ignoring unknown extended header keyword `SCHILY.ino'
/usr/local/bin/gtar: Ignoring unknown extended header keyword `SCHILY.nlink'
/usr/local/bin/gtar: Exiting with failure status due to previous errors
27DEC11
/usr/local/bin/gtar: Archive value -549755813856 is out of time_t range -2147483648..2147483647
/usr/local/bin/gtar: Ignoring unknown extended header keyword `SCHILY.dev'
/usr/local/bin/gtar: Ignoring unknown extended header keyword `SCHILY.ino'
/usr/local/bin/gtar: Ignoring unknown extended header keyword `SCHILY.nlink'
/usr/local/bin/gtar: Exiting with failure status due to previous errors
17DEC11
/usr/local/bin/gtar: Archive value -549755813856 is out of time_t range -2147483648..2147483647
/usr/local/bin/gtar: Ignoring unknown extended header keyword `SCHILY.dev'
/usr/local/bin/gtar: Ignoring unknown extended header keyword `SCHILY.ino'
/usr/local/bin/gtar: Ignoring unknown extended header keyword `SCHILY.nlink'
/usr/local/bin/gtar: Exiting with failure status due to previous errors
|
|
|
|
Post by Kevin McAleavey on Jan 2, 2012 20:56:22 GMT -5
The last three backups have failed to extract - no indication of any problem while making the backups. I copied the errors in case they'll help: 31DEC11 An error occured ..... Command Line output /usr/local/bin/gtar: Archive value -549755813856 is out of time_t range <----- snipped -----> To be honest, don't know for sure but in the back of my mind, I suspect either of two things. First is that the file is too big and it's whacking the wall on extraction because there isn't enough room left or more likely the problem is that there's some straggler files in there and it's setting off the security tripwire. So just for laughs and giggles, open up that 31DEC11 archive file. When it opens up, go into the "." directory by doubleclicking it, and then go all the way down to the bottom of the listings below the "folders" ... You'll see 5 or 6 files down there that start with a dot (.) including .ICEauthority, .esd_auth, .pulse-cookie and most importantly, .xsession-errors ... I'm suspecting that they might be out of date and KNOS' security is saying "nuh-uh" to unpacking them. You can highlight one of the files, then hold down the ctrl key while clicking on the others. Once you've got them all highlighted, right click on one of the highlighteds and select "delete" ... you'll be asked to confirm, choose "selected files" and it should remove them. Try it again after the archive has been repacked. We're going to do something entirely else in 9 where the restoration will be handled automatically during the boot cycle to avoid such things inside a whole new wrapper for it. The files I mention above belong to root and extracting them as an ordinary KNOS user can fail I've come to learn. The new way for 9 will avoid that since this wasn't an intended feature in our 8 release. |
|
|
|
Post by pharrisire on Jan 7, 2012 7:40:37 GMT -5
"" So just for laughs and giggles, open up that 31DEC11 archive file. When it opens up,
go into the "." directory by doubleclicking it, and then go all the way down to the bottom
of the listings below the "folders" ... ""
Well, I'd be glad to, but..... the Archive Manager can't open it, neither can the File browser,
not gedit. The only thing that doesn't freeze up is GHex, but that doesn't get me
anywhere.
|
|
|
|
Post by Kevin McAleavey on Jan 7, 2012 20:12:24 GMT -5
"" So just for laughs and giggles, open up that 31DEC11 archive file. When it opens up, go into the "." directory by doubleclicking it, and then go all the way down to the bottom of the listings below the "folders" ... "" Well, I'd be glad to, but..... the Archive Manager can't open it, neither can the File browser, not gedit. The only thing that doesn't freeze up is GHex, but that doesn't get me anywhere. Interesting ... if the file manager can't open it, then for reasons unknown, those files would have to be corrupted. Any chance of sending me one in an email to support so I can see what went wrong there? |
|
|
|
Post by pharrisire on Jan 10, 2012 16:37:57 GMT -5
""Interesting ... if the file manager can't open it, then for reasons unknown,
those files would have to be corrupted. Any chance of sending me one in
an email to support so I can see what went wrong there?""
You bet! You can have several if'n ya want!
Oops. The file is ~30meg and yahoo doesn't want to send anything
over 25, am trying it through google now.....
|
|
|
|
Post by pharrisire on Jan 10, 2012 16:42:01 GMT -5
Well that's strike two. google gave this reason for not sending it through:
"" 07JAN.tar.gz contains an executable file. For security reasons, Gmail does not allow you to send this type of file. ""
I know I sent you one before, what did I do different then?
|
|
|
|
Post by Kevin McAleavey on Jan 10, 2012 19:14:58 GMT -5
Well that's strike two. google gave this reason for not sending it through: "" 07JAN.tar.gz contains an executable file. For security reasons, Gmail does not allow you to send this type of file. "" I know I sent you one before, what did I do different then? Heh. Well, no executables in there at all, that'd be a really bad idea from our security standpoint. Sounds like whatever they've done for an antivirus scanner on their end has come up with a new and novel way to generate false positives.  Perhaps you can drag it into a Winders box and zip it there with a password. AV engines can't figure out what's inside a password-protected archive, so that should hopefully get it here. Gotta love those antiviruses. :-\ |
|
|
|
Post by pharrisire on Jan 14, 2012 9:03:44 GMT -5
"" Perhaps you can drag it into a Winders box and zip it there with
a password. AV engines can't figure out what's inside a
password-protected archive, so that should hopefully get it here. ""
As soon as I can get KNOS to see my wireless NAS it will be done, ......
|
|
|
|
Post by pharrisire on Jan 14, 2012 12:38:58 GMT -5
Giving up on getting wireless working on Lenovo KNOS -
you should be getting
4 parts from yahoo via desktop.
|
|
|
|
Post by Kevin McAleavey on Jan 14, 2012 18:20:13 GMT -5
Giving up on getting wireless working on Lenovo KNOS - you should be getting 4 parts from yahoo via desktop. See if you can squirt me a copy of diagnostics from that Lenovo - want to see if we've got that wifi radio covered for 9 ... Edit, update: Looked over the file and sent you back the visual results by email. Since that file contains your personal stuff and it's valid, won't go into it over here under our privacy policies. |
|
|
|
Post by pharrisire on Jan 16, 2012 13:52:52 GMT -5
Fresh Lenovo diags is on its way .....
|
|
|
|
Post by pharrisire on Jan 16, 2012 14:04:13 GMT -5
Don't know if its connected, but there is a .xsession-errors from the same time frame
that you pointed out in your last email, so I'll send it after the diags just in case....
|
|
|
|
Post by Kevin McAleavey on Jan 16, 2012 17:29:03 GMT -5
Diagnostics normally include that as well since occasionally there's something interesting to note in there. In your case though, completely normal. Mysterious indeed as to what went wrong there. I have to guess that you'd just accumulated too much stuff and not enough memory available. The way we're going to handle that in 9 though should work out a lot saner for you once we get it out the door.
|
|
