Re: tar backup ok but restore errors w/ scsi dat dds2
Update - Thanks for all the good input from everyone. Nice to know you are all there in time of need (even if we couldn't solve the problem from the software side). I swapped out the mobo, went from an AOpen MX46VG(E) to an AOpen AX4SPE-UN. Same CPU, RAM, NIC, SCSI, DAT - went from on board video to a GeForce MX4000 8x AGP. Said the magic word: Abra-ca-pocus! and the problem dissapeared. Ralph Eagle Kubinski Business Systems -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: tar backup ok but restore errors w/ scsi dat dds2
File system limits don't apply to tape drives because there seen by the system as a black hole, it's a serial stream rather than a file system. Your only limit is the capacity of the drive. :o) -Original Message- From: Ralph Eagle [mailto:[EMAIL PROTECTED] Sent: 27 September 2005 2:28pm To: debian-user@lists.debian.org Subject: Re: tar backup ok but restore errors w/ scsi dat dds2 you're not hitting the 2Gb limit (with some tar) are you? Nope... while trying to debug the problem, I've been using groups of files in the 2 to 10 MB range. And, when I put the card and tape drive into the other boxes (SCO 486 and Linux PII) I used the same set of data for testing. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: tar backup ok but restore errors w/ scsi dat dds2
- moreimportantly, do NOT type commands and hints people post in the list w/o knowing what it will do :( -- feeling like a scolded step child now... :( - i assume you know to add the right options to find - i assume you know to go find the program called buffer - i assume you know the options for tar to read from stdin Yes, Yes and Yes I've worked with SCO Xenix/Unix, Novell Unixware, Slackware/Red Hat/Debian Linux, Solaris, and AIX over 14 years. But I don't claim to be a guru - that's why I came to the list for help after trying everything I knew. We use tape backup on all our in-house and customer's systems and have never run into this problem. yeah.. yeah about assume ... lol... ... Besides it looks like buffer will only help writing the data to the tape... The problem I have is reading the data back off the tape. if its written wrong ... it will barf at reading Excellent point. I assumed that if there was a problem writing the data I would get an error. yeah.. yeah about assume ... lol When I create the tar archive using: tar cvf /dev/st0 /usr/kbmosas there are no errors reported by tar. The problem is trying to read the data back from the archive just made. of course not... and do you know why not .. :( -- more scolding -- :( and that doesnt solve the problem of maybe the data is nto written as you expected due to other problems - what kind of tape noises does it make when its writing and it should be a nice and steady/constant whine ... Sounds normal to me - although it is a DAT drive and pretty quiet, not like the old QIC 1/4in or Travan drives. I think I've exhausted my resources attacking this from the software side. Will do a little mobo swap and see what happens. c ya alvin Thanks for your help Alvin Ralph Eagle Kubinski Business Systems -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: tar backup ok but restore errors w/ scsi dat dds2
hi ya ralph On Wed, 28 Sep 2005, Ralph Eagle wrote: - moreimportantly, do NOT type commands and hints people post in the list w/o knowing what it will do :( -- feeling like a scolded step child now... :( :-) ... just watching out for ya... to not cut-n-paste commands but couldn;t resist that initial comment of course not... and do you know why not .. :( -- more scolding -- :( so try to copy stuff to tape, again ... find /home/ralph | buffer | tar zcvf /dev/st0 -T - should sound nice and smooth .. no stopping and starting - it should be a constant and steady whine I think I've exhausted my resources attacking this from the software side. Will do a little mobo swap and see what happens. yeah.. but first get the tar command and buffer right... than spend some dough on a better mb, but no guarantee to fix the original problem - get a new tape cleaner and new tape - try a different tape drive - make sure you have enough cpu hp - make sure yu have enough memory - ( top -i ) should be almost no load while writing to tapes c ya alvin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: tar backup ok but restore errors w/ scsi dat dds2
On Wed, 28 Sep 2005, Ralph Eagle wrote: shinzon:~# find /usr/kbmosas/std | buffer | tar zcvf /dev/st0 -T - Backed up 110 files, 1.2MB without any errors from tar ... shinzon:~# tar tzvf /dev/st0 drwxrws--- root/users0 2005-08-25 10:10:35 usr/kbmosas/std/ -rw-rw root/users 7516 2005-08-25 10:31:52 usr/kbmosas/std/_amort tar: Skipping to next header tar: Archive contains obsolescent base-64 headers gzip: stdin: invalid compressed data--format violated tar: Child died with signal 13 tar: Error exit delayed from previous errors sounds like youhave: - bad motherboard/memory - bad tape drive cables - do NOT put a tape drives on the same (ide) cables as disks - do NOT put disk ond cdrom/dvd on the same (ide) cables - which scsi card .. - i'd always be using the latest kernel to 2.4.31 or 2.6.13 for the latest drivers at the first sign of something broken and going down to latest gcc/glibc/bash if needed Tested writing/reading tar ball to hd with no problem good ansity check And there is the fact that if I put this scsi card and either tape drive in another box (tried two other 1- SCO Unix on a 486DX266 and 2- Debian Linux on a PII in testing), they work fine. good .. hw might be okay with the distro you ran the test with This all leads me to think that the problem is the environment (mobo). Maybe this particular combination of mobo/scsi? yup or memory that wasn't used in the previous tests c ya alvin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: tar backup ok but restore errors w/ scsi dat dds2
so try to copy stuff to tape, again ... find /home/ralph | buffer | tar zcvf /dev/st0 -T - should sound nice and smooth .. no stopping and starting - it should be a constant and steady whine I think I've exhausted my resources attacking this from the software side. Will do a little mobo swap and see what happens. yeah.. but first get the tar command and buffer right... than spend some dough on a better mb, but no guarantee to fix the original problem - get a new tape cleaner and new tape - try a different tape drive - make sure you have enough cpu hp - make sure yu have enough memory - ( top -i ) should be almost no load while writing to tapes c ya alvin Ok, but only cause you asked all nice like :) I tried it one more time... Cleaned the drive with a new cleaning cart and used a new tape. I was the only user logged on the box and top -i showed CPU 99.7% idle Running a Celeron 2.4GHz w/ 512MB RAM Ran the tar through buffer: shinzon:~# find /usr/kbmosas/std | buffer | tar zcvf /dev/st0 -T - tar: Removing leading `/' from member names /usr/kbmosas/std/ /usr/kbmosas/std/_amort /usr/kbmosas/std/_ascii /usr/kbmosas/std/_browse ... /usr/kbmosas/std/_label /usr/kbmosas/std/_qres /usr/kbmosas/std/_xkey.utl Backed up 110 files, 1.2MB without any errors from tar ok, now read the tape back: shinzon:~# tar tzvf /dev/st0 drwxrws--- root/users0 2005-08-25 10:10:35 usr/kbmosas/std/ -rw-rw root/users 7516 2005-08-25 10:31:52 usr/kbmosas/std/_amort tar: Skipping to next header tar: Archive contains obsolescent base-64 headers gzip: stdin: invalid compressed data--format violated tar: Child died with signal 13 tar: Error exit delayed from previous errors = barfd I have already tried two different tape drives (seagate/sony), different tapes, cleaned the drive repeatedly, flashed bios on scsi with latest ver, updated tar to 1.15.1-2, and now tried buffer(ing). Tested writing/reading tar ball to hd with no problem. And there is the fact that if I put this scsi card and either tape drive in another box (tried two other 1- SCO Unix on a 486DX266 and 2- Debian Linux on a PII in testing), they work fine. This all leads me to think that the problem is the environment (mobo). Maybe this particular combination of mobo/scsi? I'll let you know what happens. Ralph Eagle Kubinski Business Systems -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: tar backup ok but restore errors w/ scsi dat dds2
On Wed, Sep 28, 2005 at 10:18:18AM -0400, Ralph Eagle wrote: Ran the tar through buffer: Yes, but you didn't give tar an output block size. shinzon:~# find /usr/kbmosas/std | buffer | tar zcvf /dev/st0 -T - Try: mt -f /dev/st0 setblk 32768 find /usr/kbmosas/std | tar zcvf /dev/st0 -T -b 64 - (if the drive doesn't accept 32768, try 16384, and -b 32 with tar) That way, the tape drive and tar both use the same blocksize. Frank -- Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. - Brian W. Kernighan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: tar backup ok but restore errors w/ scsi dat dds2
Alvin Oga wrote:
[snip]
- do NOT put a tape drives on the same (ide) cables as disks
- do NOT put disk ond cdrom/dvd on the same (ide) cables
[snip]
Umm, why not put hard disc and CDROM drive on same ATA cable?
I agree that it is bad practice to make a hard disc a slave to
a CDROM drive, but the other way 'round is IMO the preferred method
for connecting them. IOW, I have two ATA interfaces on my MB, and
I have four drives. Each controller has one hard disc and one CDROM
drive. This permits multiple seeks to be issued. Putting both
hard discs on one controller would result in reduced throughput
(to/from the hard discs).
What is your reasoning?
Mike
--
p=p=%c%s%c;main(){printf(p,34,p,34);};main(){printf(p,34,p,34);}
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: tar backup ok but restore errors w/ scsi dat dds2
On Wed, Sep 28, 2005 at 10:18:18AM -0400, Ralph Eagle wrote: so try to copy stuff to tape, again ... find /home/ralph | buffer | tar zcvf /dev/st0 -T - should sound nice and smooth .. no stopping and starting - it should be a constant and steady whine I think I've exhausted my resources attacking this from the software side. Will do a little mobo swap and see what happens. yeah.. but first get the tar command and buffer right... than spend some dough on a better mb, but no guarantee to fix the original problem - get a new tape cleaner and new tape - try a different tape drive - make sure you have enough cpu hp - make sure yu have enough memory - ( top -i ) should be almost no load while writing to tapes c ya alvin Ok, but only cause you asked all nice like :) I tried it one more time... Cleaned the drive with a new cleaning cart and used a new tape. I was the only user logged on the box and top -i showed CPU 99.7% idle Running a Celeron 2.4GHz w/ 512MB RAM Ran the tar through buffer: shinzon:~# find /usr/kbmosas/std | buffer | tar zcvf /dev/st0 -T - tar: Removing leading `/' from member names /usr/kbmosas/std/ /usr/kbmosas/std/_amort /usr/kbmosas/std/_ascii /usr/kbmosas/std/_browse ... /usr/kbmosas/std/_label /usr/kbmosas/std/_qres /usr/kbmosas/std/_xkey.utl Backed up 110 files, 1.2MB without any errors from tar ok, now read the tape back: shinzon:~# tar tzvf /dev/st0 drwxrws--- root/users0 2005-08-25 10:10:35 usr/kbmosas/std/ -rw-rw root/users 7516 2005-08-25 10:31:52 usr/kbmosas/std/_amort tar: Skipping to next header tar: Archive contains obsolescent base-64 headers gzip: stdin: invalid compressed data--format violated tar: Child died with signal 13 tar: Error exit delayed from previous errors = barfd I have already tried two different tape drives (seagate/sony), different tapes, cleaned the drive repeatedly, flashed bios on scsi with latest ver, updated tar to 1.15.1-2, and now tried buffer(ing). Tested writing/reading tar ball to hd with no problem. And there is the fact that if I put this scsi card and either tape drive in another box (tried two other 1- SCO Unix on a 486DX266 and 2- Debian Linux on a PII in testing), they work fine. This all leads me to think that the problem is the environment (mobo). Maybe this particular combination of mobo/scsi? I'll let you know what happens. Ralph Eagle Kubinski Business Systems I had a similar problem with tar a while ago. I wasn't using scsi though but just backing up files to CD and DVD. Reading the archives gave me errors, but I can't remember if they were exactly the same as yours. Memory test (compiling xorg :) revealed a memory problem which turned out to be just badly installed memory module. Reinstalling the modules solved my problem and all was fine after that. Simo -- :r ~/.signature signature.asc Description: Digital signature
Re: tar backup ok but restore errors w/ scsi dat dds2
Hi Frank, Yes, but you didn't give tar an output block size. shinzon:~# find /usr/kbmosas/std | buffer | tar zcvf /dev/st0 -T - Try: mt -f /dev/st0 setblk 32768 find /usr/kbmosas/std | tar zcvf /dev/st0 -T -b 64 - Ok - here's what I got: ran this - shinzon:~# mt -f /dev/st0 setblk 32768 shinzon:~# find /usr/kbmosas/std | tar zcvbf 64 /dev/st0 -T - tar finished without error 110 files, 1.2MB Now, read it back and BAM: shinzon:~# tar tzvbf 64 /dev/st0 incomplete literal tree drwxrws--- root/users0 2005-08-25 10:10:35 usr/kbmosas/std/ -rw-rw root/users 7516 2005-08-25 10:31:52 usr/kbmosas/std/_amort -rw-rw root/users 5872 2005-08-25 10:31:52 usr/kbmosas/std/_ascii -rw-rw root/users 2127 2005-08-25 10:31:52 usr/kbmosas/std/_browse -rw-rw root/users 6494 2005-08-25 10:31:52 usr/kbmosas/std/_bundle -rw-rw root/users 8624 2005-08-25 10:31:52 usr/kbmosas/std/_calc gzip: stdin: invalid compressed data--format violated tar: Unexpected EOF in archive tar: Error is not recoverable: exiting now That way, the tape drive and tar both use the same blocksize. Frank Good try Frank, thanks for the input - I really think I'm dealing with a hardware issue. Ralph Eagle Kubinski Business Systems -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: tar backup ok but restore errors w/ scsi dat dds2
On Wed, 28 Sep 2005, Ralph Eagle wrote: shinzon:~# mt -f /dev/st0 setblk 32768 shinzon:~# find /usr/kbmosas/std | tar zcvbf 64 /dev/st0 -T - ... shinzon:~# tar tzvbf 64 /dev/st0 incomplete literal tree ... gzip: stdin: invalid compressed data--format violated tar: Unexpected EOF in archive ... Good try Frank, thanks for the input - I really think I'm dealing with a hardware issue. yup... take the drive and controller and system disk to a different motherboard, ps and memory and see what breaks i think your powersupply is dying ... c ya alvin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: tar backup ok but restore errors w/ scsi dat dds2
On Wed, 28 Sep 2005, Mike McCarty wrote: Alvin Oga wrote: [snip] - do NOT put a tape drives on the same (ide) cables as disks - do NOT put disk ond cdrom/dvd on the same (ide) cables [snip] Umm, why not put hard disc and CDROM drive on same ATA cable? cdroms are typically ata-33 disks are typically ata-100 or ata-133 - the timing on the cable is different sized signals ( pulse widths ) and different loads/terminations... blah.. blah... whenver the disks does stuff ... it will try to talk at 133MB/sec and if the cdrom is smart enough, it'd will say, hey whaabout slowing down the disk, which the system says go away, it aint for you ( cdrom ) slowly releasing the disk interrupt again I agree that it is bad practice to make a hard disc a slave to a CDROM drive ever wonder why that was dell's decault config for some systems ?? where cdrom is hda and disk is hdb c ya alvin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: tar backup ok but restore errors w/ scsi dat dds2
you're not hitting the 2Gb limit (with some tar) are you? Nope... while trying to debug the problem, I've been using groups of files in the 2 to 10 MB range. And, when I put the card and tape drive into the other boxes (SCO 486 and Linux PII) I used the same set of data for testing. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: tar backup ok but restore errors w/ scsi dat dds2
tar: Skipping to next header means the tape was jumping around waiting for your system or .. tar: Archive contains obsolescent base-64 headers tar: Error exit delayed from previous errors your tape is bad .. and/or clean the head ... Before posting, I did some extensive searching for other posts on the problem and tape cleaning came up a fair number of times. I have cleaned the drive with a cleaning cart. When I put the scsi card and tape drive into the other boxes (SCO 486/Linux PII) I used the same tape, and the same set of backup files for my tests - experienced no problem I think this might be some type of conflict with the mobo perhaps? and/or when writing .. find /home/kbmosas | buffer | tar cvf /dev/st0 Hmmm, can not seem to get the above command to work. Produces the following error: tar: Cowardly refusing to create an empty archive Try `tar --help' or `tar --usage' for more information. Looked at the buffer man page and tried several permutations of your command but could not get it to work. Besides it looks like buffer will only help writing the data to the tape... The problem I have is reading the data back off the tape. When I create the tar archive using: tar cvf /dev/st0 /usr/kbmosas there are no errors reported by tar. The problem is trying to read the data back from the archive just made. c ya alvin Ralph Eagle Kubinski Business Systems -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: tar backup ok but restore errors w/ scsi dat dds2
hi ya eagle On Tue, 27 Sep 2005, Ralph Eagle wrote: and/or when writing .. find /home/kbmosas | buffer | tar cvf /dev/st0 Hmmm, can not seem to get the above command to work. Produces the following error: tar: Cowardly refusing to create an empty archive Try `tar --help' or `tar --usage' for more information. welll.. what does the message say ?? - moreimportantly, do NOT type commands and hints people post in the list w/o knowing what it will do - i assume you know to add the right options to find - i assume you know to go find the program called buffer - i assume you know the options for tar to read from stdin ( does tar cvf /dev/std0 - help ?? or ( even tar cvf /dev/std0 -T - or ( lots of other permutations yeah.. yeah about assume ... Looked at the buffer man page and tried several permutations of your command but could not get it to work. Besides it looks like buffer will only help writing the data to the tape... The problem I have is reading the data back off the tape. if its written wrong ... it will barf at reading it's written wrong if you do NOT hear a constant whine of the tape vs the stop/rewind/start noises When I create the tar archive using: tar cvf /dev/st0 /usr/kbmosas there are no errors reported by tar. The problem is trying to read the data back from the archive just made. of course not... and do you know why not .. and that doesnt solve the problem of maybe the data is nto written as you expected due to other problems - what kind of tape noises does it make when its writing and it should be a nice and steady/constant whine ... c ya alvin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: tar backup ok but restore errors w/ scsi dat dds2
I think this might be a hardware compatibility problem, but you be the judge. Using tar, I can write a tape archive to the scsi dat drive (tar cvf /dev/st0 /usr/kbmosas) without any errors but when I try to read the tape back (tar tvf /dev/st0 or tar xvf /dev/st0), I get the following messages intermingled with the verbose output from tar listing the files in the archive; tar: Skipping to next header tar: Archive contains obsolescent base-64 headers tar: Error exit delayed from previous errors The messages do not seem to be consistent - sometimes the base-64 header message does not happen and once or twice out of about ten or twenty tries, I can read the tape back without an error. It seems like the bigger the backup the more likely the problem. you're not hitting the 2Gb limit (with some tar) are you? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: tar backup ok but restore errors w/ scsi dat dds2
On Tue, 27 Sep 2005, michael wrote: I think this might be a hardware compatibility problem, but you be the judge. Using tar, I can write a tape archive to the scsi dat drive (tar cvf /dev/st0 /usr/kbmosas) without any errors but when I try to read the tape back (tar tvf /dev/st0 or tar xvf /dev/st0), I get the following messages intermingled with the verbose output from tar listing the files in the archive; tar: Skipping to next header means the tape was jumping around waiting for your system or .. tar: Archive contains obsolescent base-64 headers tar: Error exit delayed from previous errors your tape is bad .. and/or clean the head ... and/or when writing .. find /home/kbmosas | buffer | tar cvf /dev/st0 c ya alvin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
