RE: help! Problems with TAR archives?
-Original Message- From: Greg 'groggy' Lehey [mailto:[EMAIL PROTECTED]] [Format recovered--see http://www.lemis.com/email/email-format.html] X-Mailer: Microsoft Outlook, Build 10.0.3416 Incorrect wrapping in quoted text. Argh! I thought I had fixed that... I've set the wrap to 132, what else can I do? Perhaps I'll try one of these third-party programs? Or switch to ??? at the office for email? On Monday, 6 January 2003 at 8:45:25 -0500, Phillip Smith wrote: On Saturday, 4 January 2003 at 20:30:52 -0500, Phillip Smith wrote: on 1/4/03 6:50 PM, Stephen Hovey at [EMAIL PROTECTED] wrote: On Sat, 4 Jan 2003, Phillip Smith wrote: Wondering what (if anything) can be done about this? freedom# tar -xf www.tar tar: Skipping to next file header... tar: Unknown file type '' for çÓîïæ8ËÜ«»ß[+î¯n·Ñ_}ûíÒMÂ2žð±çÕV´2¬£8(UvjÛu¾ßש¦ ä, extracted as normal file tar: Skipping to next file header... I don't understand what's happened to this archive (and serveral others that represent my entire system backup)? I'm having the same problem with a whole set of archives that I ftp to a remote Windows machine... the ones I stored on my other FreeBSD machine are fine. Did something happen during the transfer? windows ftp defaults to ascii more, not binary, so its adds a \r to each \n - you might save your tar files if you upload ascii to get them stripped out again. Would it be possible to use a script to achieve the same outcome? No, you don't know which \rs have been added. I've tried re-uploading/downlaoding the files in multiple modes, to no avail. It should work with binary transfer. Tried several times/ways to no avail. Hmm. OK, when you've transferred the file, transfer it back to your FreeBSD box under a different name. Then compare the two files with cmp(1). That will tell you whether you're really suffering from data corruption. Okay, I'll give that a try. Also, I ftp'd these files TO a Windows box FROM my BSD box, so I believe that the default mode for that would be binary? What does ftp say? FTP is set to binary by default, so I'm quite confused. Not on Microsoft. True. Are there any other reasons this may have happened? Any way to test? I can't think of any other. It's a traditional problem. You can test by comparing the size of the archives on each side. Archives appear to be the same size on both sides. Hmm, that's not the \r syndrome, then. I'm starting to think that the archives got corrupted somehow? What does tar t tell you on the FreeBSD side? tar: Hmm, this doesn't look like a tar archive. tar: Skipping to next file header... tar: only read 521 bytes from archive etc.rein.tar Also, I tried re-creating the problem. Exact same scenario. Created a new TAR archive, ftp'd from FreeBSD to Window (not specifying a setting), then used 'get' to bring them back to FreeBSD and the archives are fine. So, I'm thinking that the original archives are corrupt... The archive starts to unpack (I see a few directories and files) then hits a snag and spews garbage or quits. Here's a question then... suppose I want to re-mount a drive that had the data on it, but the drive was one of two drives mirrored with vinum. I've subsequently changed my drive set-up and now this drive is just sitting there as a 'hot spare', I haven't newfs'd it or anything... so I presume the data is still on it. If I were to re-connect the drive, and re-load vinum, could I access the data? How easy/difficult would this be? That depends a lot on the Vinum configuration and whether you're running any other Vinum volumes. It could work. But first I'd like to establish whether your archive is really corrupt. There's a possibility that the tar you're using on the Microsoft side simply doesn't understand the archive. I'm using TAR on the FreeBSD side, not the Microsoft side. Don't have an archiver installed on the Windows box. I don't have any Vinum volumes set up at the moment, no. But, I was thinking I could plug in the 'hot spare' drive and start vinum and see what config it pulls from the drive; then alter the config so that there's only one subdisk (the hot spare) for the 'mirror' and mount that and move the data off? What do you think? Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
RE: help! Problems with TAR archives?
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Phillip Smith Sent: January 9, 2003 10:23 AM To: 'Greg 'groggy' Lehey' Cc: [EMAIL PROTECTED] Subject: RE: help! Problems with TAR archives? [snip] What does tar t tell you on the FreeBSD side? tar: Hmm, this doesn't look like a tar archive. tar: Skipping to next file header... tar: only read 521 bytes from archive etc.rein.tar Also, I tried re-creating the problem. Exact same scenario. Created a new TAR archive, ftp'd from FreeBSD to Window (not specifying a setting), then used 'get' to bring them back to FreeBSD and the archives are fine. So, I'm thinking that the original archives are corrupt... I've tried a few other scenarios and this is what I've discovered... - I'm using tar -zcpvf filename.tar.gz targetdir to create the archive - using any variation of tar -zxpvf gets the messages I've outlined above - same if I gunzip the archive first, then try tar -xpvf So I tried on some new tar files, only transfering from BSD to BSD and found that, for some reason, I'm getting the same error (e.g. tar with zcpvf and ftp/binary from BSD to BSD). Now I'm confused. So, I repeat the same process without the gzip (tar cpvf and ftp/binary from BSD to BSD), and presto the archives are fine. I would assume from this, that I'm doing something wrong with the gzip? Or that gzip is doing something funny. Any thoughts? p. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: help! Problems with TAR archives?
On Thursday, 9 January 2003 at 12:08:29 -0500, Phillip Smith wrote: On January 9, 2003 10:23 AM, Phillip Smith wrote: What does tar t tell you on the FreeBSD side? tar: Hmm, this doesn't look like a tar archive. tar: Skipping to next file header... tar: only read 521 bytes from archive etc.rein.tar Also, I tried re-creating the problem. Exact same scenario. Created a new TAR archive, ftp'd from FreeBSD to Window (not specifying a setting), then used 'get' to bring them back to FreeBSD and the archives are fine. So, I'm thinking that the original archives are corrupt... I've tried a few other scenarios and this is what I've discovered... - I'm using tar -zcpvf filename.tar.gz targetdir to create the archive - using any variation of tar -zxpvf gets the messages I've outlined above - same if I gunzip the archive first, then try tar -xpvf z compresses the archive. No wonder you're not having any success without z on the extract. So I tried on some new tar files, only transfering from BSD to BSD and found that, for some reason, I'm getting the same error (e.g. tar with zcpvf and ftp/binary from BSD to BSD). Now I'm confused. So, I repeat the same process without the gzip (tar cpvf and ftp/binary from BSD to BSD), and presto the archives are fine. I would assume from this, that I'm doing something wrong with the gzip? Or that gzip is doing something funny. Possibly. I'm having difficulty getting details here, but if you've found a workaround, great. You can use gzip -t to test the integrity of compressed files. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
RE: help! Problems with TAR archives?
On Saturday, 4 January 2003 at 20:30:52 -0500, Phillip Smith wrote: on 1/4/03 6:50 PM, Stephen Hovey at [EMAIL PROTECTED] wrote: On Sat, 4 Jan 2003, Phillip Smith wrote: Wondering what (if anything) can be done about this? freedom# tar -xf www.tar tar: Skipping to next file header... tar: Unknown file type '' for çÓîïæ8ËÜ«»ß[+î¯n·Ñ_}ûíÒMÂ2žð±çÕV´2¬£8(UvjÛu¾ßש¦ ä, extracted as normal file tar: Skipping to next file header... I don't understand what's happened to this archive (and serveral others that represent my entire system backup)? I'm having the same problem with a whole set of archives that I ftp to a remote Windows machine... the ones I stored on my other FreeBSD machine are fine. Did something happen during the transfer? Also, for each archive, the first few items are extracted properly and then there all this junk... any thought _really_ appreciated. If these are corrupt, I've lost a pile of data. Many thanks in advance, windows ftp defaults to ascii more, not binary, so its adds a \r to each \n - you might save your tar files if you upload ascii to get them stripped out again. Would it be possible to use a script to achieve the same outcome? No, you don't know which \rs have been added. I've tried re-uploading/downlaoding the files in multiple modes, to no avail. It should work with binary transfer. Tried several times/ways to no avail. Also, I ftp'd these files TO a Windows box FROM my BSD box, so I believe that the default mode for that would be binary? What does ftp say? FTP is set to binary by default, so I'm quite confused. Are there any other reasons this may have happened? Any way to test? I can't think of any other. It's a traditional problem. You can test by comparing the size of the archives on each side. Archives appear to be the same size on both sides. I'm starting to think that the archives got corrupted somehow? The archive starts to unpack (I see a few directories and files) then hits a snag and spews garbage or quits. Here's a question then... suppose I want to re-mount a drive that had the data on it, but the drive was one of two drives mirrored with vinum. I've subsequently changed my drive set-up and now this drive is just sitting there as a 'hot spare', I haven't newfs'd it or anything... so I presume the data is still on it. If I were to re-connect the drive, and re-load vinum, could I access the data? How easy/difficult would this be? Thanks again! p. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: help! Problems with TAR archives?
[Format recovered--see http://www.lemis.com/email/email-format.html] X-Mailer: Microsoft Outlook, Build 10.0.3416 Incorrect wrapping in quoted text. On Monday, 6 January 2003 at 8:45:25 -0500, Phillip Smith wrote: On Saturday, 4 January 2003 at 20:30:52 -0500, Phillip Smith wrote: on 1/4/03 6:50 PM, Stephen Hovey at [EMAIL PROTECTED] wrote: On Sat, 4 Jan 2003, Phillip Smith wrote: Wondering what (if anything) can be done about this? freedom# tar -xf www.tar tar: Skipping to next file header... tar: Unknown file type '' for çÓîïæ8ËÜ«»ß[+î¯n·Ñ_}ûíÒMÂ2žð±çÕV´2¬£8(UvjÛu¾ßש¦ ä, extracted as normal file tar: Skipping to next file header... I don't understand what's happened to this archive (and serveral others that represent my entire system backup)? I'm having the same problem with a whole set of archives that I ftp to a remote Windows machine... the ones I stored on my other FreeBSD machine are fine. Did something happen during the transfer? windows ftp defaults to ascii more, not binary, so its adds a \r to each \n - you might save your tar files if you upload ascii to get them stripped out again. Would it be possible to use a script to achieve the same outcome? No, you don't know which \rs have been added. I've tried re-uploading/downlaoding the files in multiple modes, to no avail. It should work with binary transfer. Tried several times/ways to no avail. Hmm. OK, when you've transferred the file, transfer it back to your FreeBSD box under a different name. Then compare the two files with cmp(1). That will tell you whether you're really suffering from data corruption. Also, I ftp'd these files TO a Windows box FROM my BSD box, so I believe that the default mode for that would be binary? What does ftp say? FTP is set to binary by default, so I'm quite confused. Not on Microsoft. Are there any other reasons this may have happened? Any way to test? I can't think of any other. It's a traditional problem. You can test by comparing the size of the archives on each side. Archives appear to be the same size on both sides. Hmm, that's not the \r syndrome, then. I'm starting to think that the archives got corrupted somehow? What does tar t tell you on the FreeBSD side? The archive starts to unpack (I see a few directories and files) then hits a snag and spews garbage or quits. Here's a question then... suppose I want to re-mount a drive that had the data on it, but the drive was one of two drives mirrored with vinum. I've subsequently changed my drive set-up and now this drive is just sitting there as a 'hot spare', I haven't newfs'd it or anything... so I presume the data is still on it. If I were to re-connect the drive, and re-load vinum, could I access the data? How easy/difficult would this be? That depends a lot on the Vinum configuration and whether you're running any other Vinum volumes. It could work. But first I'd like to establish whether your archive is really corrupt. There's a possibility that the tar you're using on the Microsoft side simply doesn't understand the archive. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: help! Problems with TAR archives?
On Saturday, 4 January 2003 at 20:30:52 -0500, Phillip Smith wrote: on 1/4/03 6:50 PM, Stephen Hovey at [EMAIL PROTECTED] wrote: On Sat, 4 Jan 2003, Phillip Smith wrote: Wondering what (if anything) can be done about this? freedom# tar -xf www.tar tar: Skipping to next file header... tar: Unknown file type '' for çÓîïæ8ËÜ«»ß[+î¯n·Ñ_}ûíÒMÂ2žð±çÕV´2¬£8(UvjÛu¾ßש¦ ä, extracted as normal file tar: Skipping to next file header... I don't understand what's happened to this archive (and serveral others that represent my entire system backup)? I'm having the same problem with a whole set of archives that I ftp to a remote Windows machine... the ones I stored on my other FreeBSD machine are fine. Did something happen during the transfer? Also, for each archive, the first few items are extracted properly and then there all this junk... any thought _really_ appreciated. If these are corrupt, I've lost a pile of data. Many thanks in advance, windows ftp defaults to ascii more, not binary, so its adds a \r to each \n - you might save your tar files if you upload ascii to get them stripped out again. Would it be possible to use a script to achieve the same outcome? No, you don't know which \rs have been added. I've tried re-uploading/downlaoding the files in multiple modes, to no avail. It should work with binary transfer. Also, I ftp'd these files TO a Windows box FROM my BSD box, so I believe that the default mode for that would be binary? What does ftp say? Are there any other reasons this may have happened? Any way to test? I can't think of any other. It's a traditional problem. You can test by comparing the size of the archives on each side. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: help! Problems with TAR archives?
windows ftp defaults to ascii more, not binary, so its adds a \r to each \n - you might save your tar files if you upload ascii to get them stripped out again. On Sat, 4 Jan 2003, Phillip Smith wrote: Hi, Wondering what (if anything) can be done about this? freedom# tar -xf www.tar tar: Skipping to next file header... tar: Unknown file type '' for çÓîïæ8ËÜ«»ß[+î¯n·Ñ_}ûíÒMÂ2žð±çÕV´2¬£8(UvjÛu¾ßש¦ ä, extracted as normal file tar: Skipping to next file header... I don't understand what's happened to this archive (and serveral others that represent my entire system backup)? I'm having the same problem with a whole set of archives that I ftp to a remote Windows machine... the ones I stored on my other FreeBSD machine are fine. Did something happen during the transfer? Also, for each archive, the first few items are extracted properly and then there all this junk... any thought _really_ appreciated. If these are corrupt, I've lost a pile of data. Many thanks in advance, phillip. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: help! Problems with TAR archives?
Would it be possible to use a script to achieve the same outcome? I've tried re-uploading/downlaoding the files in multiple modes, to no avail. Also, I ftp'd these files TO a Windows box FROM my BSD box, so I believe that the default mode for that would be binary? Are there any other reasons this may have happened? Any way to test? p. on 1/4/03 6:50 PM, Stephen Hovey at [EMAIL PROTECTED] wrote: windows ftp defaults to ascii more, not binary, so its adds a \r to each \n - you might save your tar files if you upload ascii to get them stripped out again. On Sat, 4 Jan 2003, Phillip Smith wrote: Hi, Wondering what (if anything) can be done about this? freedom# tar -xf www.tar tar: Skipping to next file header... tar: Unknown file type '' for çÓîïæ8ËÜ«»ß[+î¯n·Ñ_}ûíÒMÂ2žð±çÕV´2¬£8(UvjÛu¾ßש¦ ä, extracted as normal file tar: Skipping to next file header... I don't understand what's happened to this archive (and serveral others that represent my entire system backup)? I'm having the same problem with a whole set of archives that I ftp to a remote Windows machine... the ones I stored on my other FreeBSD machine are fine. Did something happen during the transfer? Also, for each archive, the first few items are extracted properly and then there all this junk... any thought _really_ appreciated. If these are corrupt, I've lost a pile of data. Many thanks in advance, phillip. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
