Re: Unrecognized archive format with RELENG_6_2 and RELENG_6
Quoting Tim Kientzle [EMAIL PROTECTED]: This morning I have revert libarchive (src/lib/libarchive) and tar (src/usr.bin/tar) back to RELENG_6_1 and surprisingly (or maybe not) it works fine now. After that I try to read/list the tar from tape with tar -t: $ sudo tar -tf /dev/sa0 archive.dmp tar: Unrecognized archive format: Inappropriate file type or format But when I extract the archive from tape, it works perfectly: $ sudo tar -xvf /dev/sa0 x archive.dmp What SCSI controller are you using? This could conceivably be an issue with a particular SCSI controller. A few lines from 'dmesg' could help here. Here you go ciss0: HP Smart Array 6i port 0x4000-0x40ff mem 0xfdff-0xfdff1fff,0xfdf800 00-0xfdfb irq 51 at device 3.0 on pci4 ciss0: [GIANT-LOCKED] .. sa0 at ciss0 bus 33 target 5 lun 0 sa0: HP C7438A V312 Removable Sequential Access SCSI-3 device sa0: 135.168MB/s transfers cut P.S. In the meantime, of course, tar from 6.1 and gtar should both work in this situation. Yep, at the moment I have switched the tar release back to the one from 6.1. Kind regards, Robin Gruyters Network and Security Engineer Yirdis B.V. I: http://yirdis.com P: +31 (0)36 5300394 F: +31 (0)36 5489119 pgpNv9Aco2ggJ.pgp Description: PGP Digital Signature
Re: Unrecognized archive format with RELENG_6_2 and RELENG_6
Quoting Tim Kientzle [EMAIL PROTECTED]: After that I try to read/list the tar from tape with tar -t: $ sudo tar -tf /dev/sa0 archive.dmp tar: Unrecognized archive format: Inappropriate file type or format But when I extract the archive from tape, it works perfectly: $ sudo tar -xvf /dev/sa0 Using dd to feed tar does work though. (I think this agrees with Robin's findings although the fact that it works with -z is curious) This is a Tandberg TS400 (LTO2 drive, LTO1 tape) idd, same problem here. When using -z option, works perfectly. Without it, it fails. Our tapedrive is a HP C7438A V312. (DAT) Please try the following: sudo ktrace tar -tf /dev/sa0 Then run 'kdump | less' and see if you can find a pair of 'lseek' calls, which will probably look something like this: 53127 bsdtar CALL lseek(0x3,0,0,0,0x1) 53127 bsdtar RET lseek 6656000/0x659000 53127 bsdtar CALL lseek(0x3,0,0x70800,0,0x1) 53127 bsdtar RET lseek 7116800/0x6c9800 Here you go: 95225 bsdtar CALL lseek(0x3,0,0,0,0x1) 95225 bsdtar RET lseek 65536/0x1 95225 bsdtar CALL lseek(0x3,0,0,0,0x1) 95225 bsdtar RET lseek 65536/0x1 Robin Gruyters Network and Security Engineer Yirdis B.V. I: http://yirdis.com P: +31 (0)36 5300394 F: +31 (0)36 5489119 pgpBeBLBin0Cu.pgp Description: PGP Digital Signature
Re: Unrecognized archive format with RELENG_6_2 and RELENG_6
Quoting Tim Kientzle [EMAIL PROTECTED]: On Monday 04 June 2007 17:46, Robin Gruyters wrote: This morning I have revert libarchive (src/lib/libarchive) and tar (src/usr.bin/tar) back to RELENG_6_1 and surprisingly (or maybe not) it works fine now. Maybe tar doesn't use the -b option when listing the content? (-t) Could you please send me details of the problem you're having? Ok, here a small setup. I create a random file with roughly size of 5MB: $ dd if=/dev/random of=archive.dmp bs=1024 count=5120 5120+0 records in 5120+0 records out 5242880 bytes transferred in 0.174116 secs (30111397 bytes/sec) Then a tar the file (with or without blocksize set) to tape: $ sudo tar -cf /dev/sa0 archive.dmp $ After that I try to read/list the tar from tape with tar -t: $ sudo mt -f /dev/sa0 rewind $ sudo tar -tf /dev/sa0 archive.dmp tar: Unrecognized archive format: Inappropriate file type or format $ I get strait away the Unrecognized archive message. But when I extract the archive from tape, it works perfectly: $ sudo tar -xvf /dev/sa0 x archive.dmp $ I have tested this with libarchive and tar from RELENG_6 and RELENG_6_2. No problems with libarchive and tar from RELENG_6_1. If you need more (debug) info, let me know Kind regards, Robin Gruyters Network and Security Engineer Yirdis B.V. I: http://yirdis.com P: +31 (0)36 5300394 F: +31 (0)36 5489119 pgp5dVyZcTE26.pgp Description: PGP Digital Signature
Re: Unrecognized archive format with RELENG_6_2 and RELENG_6
Quoting Daniel O'Connor [EMAIL PROTECTED]: On Wednesday 06 June 2007 16:14, Robin Gruyters wrote: Then a tar the file (with or without blocksize set) to tape: $ sudo tar -cf /dev/sa0 archive.dmp $ After that I try to read/list the tar from tape with tar -t: $ sudo mt -f /dev/sa0 rewind $ sudo tar -tf /dev/sa0 archive.dmp tar: Unrecognized archive format: Inappropriate file type or format $ I get strait away the Unrecognized archive message. But when I extract the archive from tape, it works perfectly: $ sudo tar -xvf /dev/sa0 x archive.dmp $ I have tested this with libarchive and tar from RELENG_6 and RELENG_6_2. No problems with libarchive and tar from RELENG_6_1. I did.. tar -zcvf /dev/sa0 /boot tar -ztvf /dev/sa0 tar -b 1 -zcvf /dev/sa0 /boot tar -b 1 -ztvf /dev/sa0 tar -b 20 -zcvf /dev/sa0 /boot tar -b 20 -ztvf /dev/sa0 tar -b 128 -zcvf /dev/sa0 /boot tar -b 128 -ztvf /dev/sa0 And they work. The example you gave failed however, so do.. tar -b 1 -cvf /dev/sa0 /boot tar -b 1 -tvf /dev/sa0 tar -b 20 -cvf /dev/sa0 /boot tar -b 20 -tvf /dev/sa0 tar -b 128 -cvf /dev/sa0 /boot tar -b 128 -tvf /dev/sa0 Using dd to feed tar does work though. (I think this agrees with Robin's findings although the fact that it works with -z is curious) [cain 17:05] ~ mt status Mode Density Blocksize bpi Compression Current: 0x40 variable 0disabled -available modes- 0:0x40 variable 00x1 1:0x40 variable 00x1 2:0x40 variable 00x1 3:0x40 variable 00x1 - Current Driver State: at rest. - File Number: 0 Record Number: 0Residual Count 0 This is a Tandberg TS400 (LTO2 drive, LTO1 tape) idd, same problem here. When using -z option, works perfectly. Without it, it fails. Here is mine 'mt status' output: $ sudo mt status Mode Density Blocksize bpi Compression Current: 0x47 variable 0DCLZ -available modes- 0:0x47 variable 0DCLZ 1:0x47 variable 0DCLZ 2:0x47 variable 0DCLZ 3:0x47 variable 0DCLZ - Current Driver State: at rest. - File Number: 0 Record Number: 0Residual Count 0 Our tapedrive is a HP C7438A V312. (DAT) Kind regards, Robin Gruyters Network and Security Engineer Yirdis B.V. I: http://yirdis.com P: +31 (0)36 5300394 F: +31 (0)36 5489119 pgpUmqzKSinmP.pgp Description: PGP Digital Signature
Re: Unrecognized archive format with RELENG_6_2 and RELENG_6
Quoting Daniel O'Connor [EMAIL PROTECTED]: On Friday 01 June 2007 23:39, Robin Gruyters wrote: What happens if you try tar -b 128 -tf /dev/sa0 Same problem. What did you upgrade from? Some gnutar using system I guess? (5.x or 4.x?) I'd upgraded from FreeBSD 6.1-RELEASE-p10 OK. Can you read the archive as a normal file from the tape? eg dd if=/dev/sa0 of=/tmp/foo If so does it work? Are you getting errors reading from the drive, or just the tar file is broken? Nope, it doesn't work. # dd if=/dev/sa0 of=/data3/tmp/bla dd: /dev/sa0: Input/output error 0+0 records in 0+0 records out 0 bytes transferred in 0.005972 secs (0 bytes/sec) # When setting the correct blocksize, it does work: # dd if=/dev/sa0 of=/data3/tmp/bla bs=65536 count=32 32+0 records in 32+0 records out 2097152 bytes transferred in 9.698233 secs (216241 bytes/sec) # This morning I have revert libarchive (src/lib/libarchive) and tar (src/usr.bin/tar) back to RELENG_6_1 and surprisingly (or maybe not) it works fine now. Maybe tar doesn't use the -b option when listing the content? (-t) Kind regards, Robin Gruyters Network and Security Engineer Yirdis B.V. I: http://yirdis.com P: +31 (0)36 5300394 F: +31 (0)36 5489119 pgpFRkTZCvB8k.pgp Description: PGP Digital Signature
Unrecognized archive format with RELENG_6_2 and RELENG_6
Hi ya, Yesterday I have upgraded one of servers to RELENG_6_2 and no problems so far. This morning I recieved an email from one of our system manager and told me that the backup has failed with the following message: tar: Unrecognized archive format: Inappropriate file type or format This happends when the following command is used: # tar -tf /dev/sa0 It will show you the first 10 files and then exits. After searching the MARC list, I found the following post: http://marc.info/?l=freebsd-questionsm=117442965732289 Apparently nobody has (yet) replied to it. After reading a few posts about similar problems http://www.freebsd.org/cgi/query-pr.cgi?pr=111236 I'd updated the libarchive (lib/libarchive) and tar (usr.bin/tar) in the source tree to RELENG_6 and recompiled both, but still encounter same problem. Anybody any idea how to fix this? Kind regards, Robin Gruyters Network and Security Engineer Yirdis B.V. I: http://yirdis.com P: +31 (0)36 5300394 F: +31 (0)36 5489119 pgpN8n7ath6O5.pgp Description: PGP Digital Signature ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Unrecognized archive format with RELENG_6_2 and RELENG_6
What happens if you try tar -b 128 -tf /dev/sa0 Same problem. What did you upgrade from? Some gnutar using system I guess? (5.x or 4.x?) I'd upgraded from FreeBSD 6.1-RELEASE-p10 Kind regards, Robin Gruyters Network and Security Engineer Yirdis B.V. I: http://yirdis.com P: +31 (0)36 5300394 F: +31 (0)36 5489119 Quoting Daniel O'Connor [EMAIL PROTECTED]: On Friday 01 June 2007 19:10, Robin Gruyters wrote: This happends when the following command is used: # tar -tf /dev/sa0 It will show you the first 10 files and then exits. After searching the MARC list, I found the following post: What happens if you try tar -b 128 -tf /dev/sa0 What did you upgrade from? Some gnutar using system I guess? (5.x or 4.x?) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgpRJu4fc4xY1.pgp Description: PGP Digital Signature
Re: bge Ierr rate increase from 5.3R - 6.1R
Quoting Jeremy Chadwick [EMAIL PROTECTED]: [...] Set your Cisco configuration to use 100/full, and edit the ifconfig_bge0 line in rc.conf on your FreeBSD box to have media 100baseTX mediaopt full-duplex, then reboot the FreeBSD box. If the problem continues, there may be faulty cabling, but usually errors on one direction are a sign of duplex mismatch. If after replacing the cabling the issue continues, then there's a chance the bge(4) driver may be obtaining statistics wrong for the particular chip revision being used (this is hearsay on my part; I'm just guessing...) Ok, I have set the Cisco port to 100/full-duplex and update the bge* interfaces on the development server, but the problem still exists. I have also updated the other server, which is connected to another Cisco switch, but the same results. Regards, Robin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bge Ierr rate increase from 5.3R - 6.1R
Quoting Jeremy Chadwick [EMAIL PROTECTED]: On Thu, Jan 25, 2007 at 12:07:22PM +0100, Robin Gruyters wrote: Quoting Jeremy Chadwick [EMAIL PROTECTED]: [...] Set your Cisco configuration to use 100/full, and edit the ifconfig_bge0 line in rc.conf on your FreeBSD box to have media 100baseTX mediaopt full-duplex, then reboot the FreeBSD box. If the problem continues, there may be faulty cabling, but usually errors on one direction are a sign of duplex mismatch. If after replacing the cabling the issue continues, then there's a chance the bge(4) driver may be obtaining statistics wrong for the particular chip revision being used (this is hearsay on my part; I'm just guessing...) Ok, I have set the Cisco port to 100/full-duplex and update the bge* interfaces on the development server, but the problem still exists. I have also updated the other server, which is connected to another Cisco switch, but the same results. Okay so at least we know it's not specific to your switch, or to auto-neg nor the cabling (two different switches + boxes with the same problem probably isn't your fault. :) ). That's definitely evidence that it's a driver problem, probably specific to the 5704 (since I have two machines using 5750s without this problem). Looks like we'll need someone with the Broadcom data sheet for the 5704 to help out. There's also the Bill Paul [EMAIL PROTECTED] and David Christensen [EMAIL PROTECTED] (who worked on bce(4), but might know of some details here...) Hmmm, ok. BTW, I found out there another thread going on on the freebsd-net mailinglist about the same issue(s): http://marc.theaimsgroup.com/?l=freebsd-netw=2r=1s=bge+ierrq=b There are some patches available, but looks like only for the -CURRENT not for 6.x releases. Regards, Robin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bge Ierr rate increase from 5.3R - 6.1R
) pci0: serial bus, USB at device 29.7 (no driver attached) pcib8: ACPI PCI-PCI bridge at device 30.0 on pci0 pci1: ACPI PCI bus on pcib8 pci1: display, VGA at device 3.0 (no driver attached) pci1: base peripheral at device 4.0 (no driver attached) pci1: base peripheral at device 4.2 (no driver attached) isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel 6300ESB UDMA100 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x500-0x50f irq 18 at device 31.1 on pci0 ata0: ATA channel 0 on atapci0 ata1: ATA channel 1 on atapci0 acpi_tz0: Thermal Zone on acpi0 atkbdc0: Keyboard controller (i8042) port 0x60,0x64 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse Explorer, device ID 4 sio0: Standard PC COM port port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A fdc0: floppy drive controller (FDE) port 0x3f2-0x3f5 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: 1440-KB 3.5 drive on fdc0 drive 0 pmtimer0 on isa0 orm0: ISA Option ROMs at iomem 0xc-0xc7fff,0xc8000-0xcbfff,0xee000-0xe on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounter TSC frequency 3000124702 Hz quality 800 Timecounters tick every 1.000 msec acd0: CDROM COMPAQ CD-ROM SN-124/N104 at ata0-master PIO4 da0 at ciss0 bus 0 target 0 lun 0 da0: COMPAQ RAID 1 VOLUME OK Fixed Direct Access SCSI-0 device da0: 135.168MB/s transfers da0: 69459MB (142253280 512 byte sectors: 255H 32S/T 17433C) Trying to mount root from ufs:/dev/da0s1a Accounting enabled [/FreeBSD 6.2R] And here is the netstat -ni output from our development server: [netstat -ni] NameMtu Ipkts Ierrs Opkts Oerrs Coll ste0* 15000 0 0 0 0 ste1* 15000 0 0 0 0 ste2* 15000 0 0 0 0 ste3* 15000 0 0 0 0 bge015009866912 2114443 188352090 0 bge015002004841 - 18833483- - bge015001723393 - 1719554 - - bge0150082 - 66 - - bge0150019036813- 14796159- - bge0150038709278- 35167554- - bge015000 - 0 - - bge01500621 - 0 - - bge015001716- 0 - - bge01500184 - 0 - - bge0150052881 - 2336- - bge1* 15000 0 0 0 0 pflog 33208 0 0 0 0 lo0 16384 0 516926240 0 lo0 16384 6611- 6611- - [...] Is there a fix for it already, or maybe a workaround? Regards, Robin Gruyters Network and Security Engineer Yirdis B.V. I: http://yirdis.com P: +31 (0)36 5300394 F: +31 (0)36 5489119 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bge Ierr rate increase from 5.3R - 6.1R
Quoting Jeremy Chadwick [EMAIL PROTECTED]: Is there a fix for it already, or maybe a workaround? The problem was that the driver code was not properly obtaining error statistics from the Broadcom chip, thus errors _were_ (before the fix) not being calculated/accounted for. Now (after the fix) errors are being accounted for correctly. So the errors you see in your netstat output are probably real/ ccurate. I'll vote for a duplex-related problem or some naughty cabling. Should this not be visible on the switch as well?!? Here some output from the interface on the server and from the switch (Cisco) [development interface] bge0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=1bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING ether 00:12:79:94:ed:12 media: Ethernet autoselect (100baseTX full-duplex) status: active [/development interface] [switch] FastEthernet0/3 is up, line protocol is up (connected) Hardware is Fast Ethernet, address is 000e.84d0.de03 (bia 000e.84d0.de03) Description: development MTU 1500 bytes, BW 10 Kbit, DLY 100 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation ARPA, loopback not set Keepalive set (10 sec) Full-duplex, 100Mb/s input flow-control is off, output flow-control is off ARP type: ARPA, ARP Timeout 04:00:00 Last input never, output 00:00:02, output hang never Last clearing of show interface counters never Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: fifo Output queue: 0/40 (size/max) 5 minute input rate 179000 bits/sec, 28 packets/sec 5 minute output rate 56000 bits/sec, 24 packets/sec 22823978 packets input, 4067576147 bytes, 0 no buffer Received 13138 broadcasts (0 multicast) 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored 0 watchdog, 12929 multicast, 0 pause input 0 input packets with dribble condition detected 15673035 packets output, 3975127029 bytes, 0 underruns 0 output errors, 0 collisions, 1 interface resets 0 babbles, 0 late collision, 0 deferred 0 lost carrier, 0 no carrier, 0 PAUSE output 0 output buffer failures, 0 output buffers swapped out [/switch] Regards, Robin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
