Re: Tape drive recommendations
On Thu, Sep 20, 2012 at 2:45 PM, Steve Bertrand wrote: > Hi all, > > I know this is a bit off-topic, but I'm looking for suggestions. > > In one of my corporate sites, I've got a Tandberg Magnum 2x24 dual 10-slot > tape backup device that I feel is on its way out. > > The storage amount for this site is adequate with the existing device and so > is the performance, but I'm just curious to find out others opinions on what > they use for tape backup machines nowadays before I purchase something new. > I back up between 2 and 4 TB per day at this particular site. > > Off-list replies if you don't feel comfortable specifying vendors publicly > are welcome. > > Steve We've had good luck with our Spectralogic T50 with DLT3 drives, and mediocre luck with our Dell 124T with a DLT4 drive that replaced the Spectralogic. If I had to choose, I'd stick with the Spectralogic.. Kurt ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Tape drive recommendations
Hi all, I know this is a bit off-topic, but I'm looking for suggestions. In one of my corporate sites, I've got a Tandberg Magnum 2x24 dual 10-slot tape backup device that I feel is on its way out. The storage amount for this site is adequate with the existing device and so is the performance, but I'm just curious to find out others opinions on what they use for tape backup machines nowadays before I purchase something new. I back up between 2 and 4 TB per day at this particular site. Off-list replies if you don't feel comfortable specifying vendors publicly are welcome. Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Reading an unknown DAT Tape
On Mar 15, 2012, at 1:17 PM, Martin McCormick wrote:
> I opened it with dd files=2 if=/dev/sa0 of=testfile and
> then did the strings utility on testfile and got:
What does "file testfile" think?
("od -ax" on the first part of the file might be informative, also.)
Regards,
--
-Chuck
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Reading an unknown DAT Tape
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/15/2012 14:02, Jerry McAllister wrote: > On Thu, Mar 15, 2012 at 03:17:05PM -0500, Martin McCormick wrote: > >> This is a case of idle curiosity and not an urgent need to >> recover a valuable backup. I found an old DAT tape and attempted >> to read it on the very drive that probably once wrote it and it >> appears to read the tape properly in that I can use dd to copy it >> to a file and mt fsf 5, for example, takes the tape to the fifth >> file marker so there is sanity. >> >> Tar, however, does not recognize the format of the archive so it >> is either something proprietary or I am not using the correct >> utility on it. >> >> I opened it with dd files=2 if=/dev/sa0 of=testfile and then did >> the strings utility on testfile and got: >> >> TAPE SSET VOLB DIRB NACL Setting security iles SPAD DIRB NACL >> Setting security on system files... SPAD DIRB NACL SPAD DIRB >> NACL SPAD FILE NACL STAN Jun 23 2003 12:00AM Jan 1 1900 8:45AM >> Jan 1 1900 9:00AM > > I wondered about it being a dump(8) file, but just tried one and > strings output looked a little different. > > How about a db of some sort or a log from some lab test? > > jerry > > > >> >> Note that we are obviously able to read data from the tape as the >> top few lines are readible as words. The time stamps at the >> bottom are possibly not time stamps as some of them are not >> plausible. >> >> The dd command never faltered with errors although I did finally >> stop it manually. >> >> Is there any FreeBSD utility that can tell more about what >> created the original archive? >> >> Thank you. >> >> Martin McCormick A quick check of Google with the strings you dumped points at Microsoft Tape format. Possibly from the win2k utility. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.18 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk9iW/QACgkQrDN5kXnx8yYRawCePDzWmtZaHrvB1jq3gY3BS96f dvUAnRvBdclM3E0+WDus0dNlPVuN1ELD =p5oa -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Reading an unknown DAT Tape
On Thu, Mar 15, 2012 at 03:17:05PM -0500, Martin McCormick wrote: > This is a case of idle curiosity and not an urgent need > to recover a valuable backup. I found an old DAT tape and > attempted to read it on the very drive that probably once wrote > it and it appears to read the tape properly in that I can use dd > to copy it to a file and mt fsf 5, for example, takes the tape > to the fifth file marker so there is sanity. > > Tar, however, does not recognize the format of the > archive so it is either something proprietary or I am not using > the correct utility on it. > > I opened it with dd files=2 if=/dev/sa0 of=testfile and > then did the strings utility on testfile and got: > > TAPE > SSET > VOLB > DIRB > NACL > Setting security > iles > SPAD > DIRB > NACL > Setting security on system files... > SPAD > DIRB > NACL > SPAD > DIRB > NACL > SPAD > FILE > NACL > STAN > Jun 23 2003 12:00AM > Jan 1 1900 8:45AM > Jan 1 1900 9:00AM I wondered about it being a dump(8) file, but just tried one and strings output looked a little different. How about a db of some sort or a log from some lab test? jerry > > Note that we are obviously able to read data from the > tape as the top few lines are readible as words. The time stamps > at the bottom are possibly not time stamps as some of them are > not plausible. > > The dd command never faltered with errors although I > did finally stop it manually. > > Is there any FreeBSD utility that can tell more about > what created the original archive? > > Thank you. > > Martin McCormick > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Reading an unknown DAT Tape
This is a case of idle curiosity and not an urgent need to recover a valuable backup. I found an old DAT tape and attempted to read it on the very drive that probably once wrote it and it appears to read the tape properly in that I can use dd to copy it to a file and mt fsf 5, for example, takes the tape to the fifth file marker so there is sanity. Tar, however, does not recognize the format of the archive so it is either something proprietary or I am not using the correct utility on it. I opened it with dd files=2 if=/dev/sa0 of=testfile and then did the strings utility on testfile and got: TAPE SSET VOLB DIRB NACL Setting security iles SPAD DIRB NACL Setting security on system files... SPAD DIRB NACL SPAD DIRB NACL SPAD FILE NACL STAN Jun 23 2003 12:00AM Jan 1 1900 8:45AM Jan 1 1900 9:00AM Note that we are obviously able to read data from the tape as the top few lines are readible as words. The time stamps at the bottom are possibly not time stamps as some of them are not plausible. The dd command never faltered with errors although I did finally stop it manually. Is there any FreeBSD utility that can tell more about what created the original archive? Thank you. Martin McCormick ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: How to persist tape configuration
In the last episode (Nov 10), Andrea Venturoli said: > > I need to set my tape with: > mt comp off. > > After a reboot I need to do this again. > > I could write a script and place it in /usr/local/etc/rc.d, but I'm just > wondering if there's already something standard in /etc. A quick grep doesn't come up with anything. An rc.d script is probably your best bet. You might be able to do it with a devd.conf entry, too. -- Dan Nelson dnel...@allantgroup.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
How to persist tape configuration
Hello. I need to set my tape with: mt comp off. After a reboot I need to do this again. I could write a script and place it in /usr/local/etc/rc.d, but I'm just wondering if there's already something standard in /etc. bye & Thanks av. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Problem reading from tape drive -- SOLVED, or at least a workaround
Is there any way I could test to make sure this is in fact what's happening? Try writing several files to the tape, each in it's own operation, and issue a 'mt -bsf' between each operation. THEN try reading from the tape. with just successive 'read' operations. *NO* 'mt' positioning If everything is working 'properly', there will be *ONLY*ONE* file on the tape. If there is an O/S failure to 'backspace on close' you'll get all the original files, one on each read attempt. If the O/S has a _complete_ 'failure to backspace', you'll get a tape that functions identially to your earlier tests -- you can find all the file by 'mt -fsf' between reads Other things to try. 1) *write* a multi-file tape under Unbuntu, and try to read it under FreeBSD. 2) *write* a multi-file tape under FreeBSD, and try to read it under Unbuntu. 3) If there are read issues, see if the 'mt -fsf' hack allows you to find everything. OK, it's definitely an O/S failure to backspace on close, because the tape does read properly when I manually backspace after each file. Unfortunately, the "workaround" of running mt -fsf after every file read if it worked, 'mf -bsf' after every _write_ would be a better solution. But it probably suffers from the same 'not really usable' defect. *cheers* And YES That's a usable workaround! Luckily enough, Bacula will run a script after each backup job, all I'll have to do is add a mt -bsf command to that script! _I_ have no clue what 'bacula' is -- sounds sort-of like a Transylvanian back-up utility. One with 'fangs' init, and issues with mirrors. Close! It's a multi-platform client-server backup application. Its tagline used to be something like "Comes in the night, and sucks the essence from your computers." When I went to check the precise wording, though, it's no longer on their logo. I guess someone objected.too bad, I got a kick from that tagline. I find it to be a great open-source replacement for backup exec. I can have the Bacula server and tape drive on one FreeBSD or Linux box, and install clients on all of my other FreeBSD & Linux servers, and Linux & Windows desktops to back them all up to that one tape drive. Thanks for all of your help!! Renee ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Problem reading from tape drive
> From owner-freebsd-questi...@freebsd.org Fri Aug 26 13:51:51 2011 > Date: Fri, 26 Aug 2011 14:50:23 -0400 > From: Renee Gehlbach > To: questi...@freebsd.org > Cc: > Subject: Re: Problem reading from tape drive > > On 08/25/2011 06:38 PM, Robert Bonomi wrote: > >> From owner-freebsd-questi...@freebsd.org Thu Aug 25 13:57:20 2011 > >> Date: Thu, 25 Aug 2011 14:24:57 -0400 > >> From: Renee Gehlbach > >> To: questi...@freebsd.org > >> Cc: > >> Subject: Problem reading from tape drive [[ sneck ]] > >> So, when I tell it to forward space file at the end of each tar file, it > >> is able to read all four files correctly. This leaves me scratching my > >> head, and wondering what the heck I've set up wrong. Any ideas? > > Tape drivers _always_ write two EOFs when the tape device is closed. > > This ensures there is always a valid 'EOT' on the tape. > > > > They're _suppoesed_ to backspace over the 2nd EOF mark, so that > > a subsequent write has only one EOF between it and the prior file. > > > > Looks like your drive isn't doing the 'backspace' right. > > > > I suspect the 'easiest' work around is the one you've discovered -- do > > an 'mt -fsf' after avery tape file 'read'. > > > OK, I feel pretty dense When you're saying they write two EOFs when > the device is closed, would this happen every time you write a file? Authortative answer "it depends". you can 'cat' several files to te tape device, in one invocation, and there will be no EOF marks between the source files. I meant _exactly_ what I said, in describing tape operationss. To wit: Every time an application calls close(2) (or fclose(3), which calls close(2)) *or* exits without closing an open file in which case the O/S invokes close(2) on every open file descrriptor. > Or > would it be every time the tape is unmounted? Or would that depend on > the program you're using? Nope, it's automatic, and internal to th O/S. > Is there any way I could test to make sure this is in fact what's happening? Try writing several files to the tape, each in it's own operation, and issue a 'mt -bsf' between each operation. THEN try reading from the tape. with just successive 'read' operations. *NO* 'mt' positioning If everything is working 'properly', there will be *ONLY*ONE* file on the tape. If there is an O/S failure to 'backspace on close' you'll get all the original files, one on each read attempt. If the O/S has a _complete_ 'failure to backspace', you'll get a tape that functions identially to your earlier tests -- you can find all the file by 'mt -fsf' between reads Other things to try. 1) *write* a multi-file tape under Unbuntu, and try to read it under FreeBSD. 2) *write* a multi-file tape under FreeBSD, and try to read it under Unbuntu. 3) If there are read issues, see if the 'mt -fsf' hack allows you to find everything. > And would the problem with it not doing the backspace right be an issue > with the FreeBSD tape driver? Or SCSI card driver? Or what driver? "Yes." A prime candiate would be sa(4) . See 'filemark handling' at the end of the manpage. mtio(4) is another candidate, see para. 3 of that manpage. And it is _possible_, albeit *unlikely, that somebody screwed up on the scsi card driver and the code for that particular command is broken. > Obviously not a problem with the drive itself, since I don't have this > problem with Ubuntu. To be precise, it is not a case of a _defective_ drive. This does not eliminate the possibiity of 'non standard' behavior (where the drive is 'working as the manufacturer intends'), with Unbuntu having an embedded 'work around'. I've had too much experience with *REALLY*weird* problems to dismiss -anything-, out of hand. 30+ years ago, I discovered inadvertently) a very specific set of circumstances where I could render a mainframe _completely_ unusable -- by simply _rewinding_ a mag tape, as a regular user. The only recovery was a re-boot of the mainframe. If folks caught it _early_enough_, a reboot directive from the operator console was effective. If it developed a bit further, the *only* recourse/remedy was the 'big red button'. To add to the 'fun', this particular vulnerability was *confirmed* to exist on at least three separate, unrelated, operating systems running on _incompatible_ hardware. > Unfortunately, the "workaround" of running mt -fsf > a
Re: Problem reading from tape drive
On 08/25/2011 06:38 PM, Robert Bonomi wrote: From owner-freebsd-questi...@freebsd.org Thu Aug 25 13:57:20 2011 Date: Thu, 25 Aug 2011 14:24:57 -0400 From: Renee Gehlbach To: questi...@freebsd.org Cc: Subject: Problem reading from tape drive I recently purchased a FreeBSD-compatible SAS card (an Adaptec ASR 2045) and moved our backup server from Ubuntu to FreeBSD 8.2. I am trying to set up the backup software, but am having problems with the tape drive. Hopefully this is a "duh" type question, since I have a lot more experience working with tape drives in Ubuntu than FreeBSD. I installed bacula, and ran the test function in the btape utility. It wrote 1 blocks, wrote EOF, wrote 1 blocks, wrote EOF, wrote EOF. Rewound the tape. Read 1 blocks, failed reading the second 1 blocks. I had no luck researching the bacula error message, so I switched to mt and tar for further troubleshooting. camcontrol devlist does show the tape drive: backup# camcontrol devlist at scbus2 target 0 lun 0 (sa0,pass0) So then I went into a directory that had one subdirectory, which contained several plain text logfiles. I did four tars, alternating between that directory and the subdirectory (so I would be able to see a difference between the tar files). backup# mt -f /dev/nsa0 rewind backup# tar -cf /dev/nsa0 * backup# cd log/ backup# tar -cf /dev/nsa0 * backup# cd .. backup# tar -cf /dev/nsa0 * backup# cd log/ backup# tar -cf /dev/nsa0 * So far so good. Then I went back to read those tar files. backup# mt -f /dev/nsa0 rewind backup# tar -tf /dev/nsa0 log/ log/mbw01.log (insert rest of correct tar listing) backup# tar -tf /dev/nsa0 tar: Unrecognized archive format tar: Error exit delayed from previous errors. Sosame results as bacula's tape test utility was giving.it writes, it reads the first file, then errors on trying to read the second file. However: backup# mt -f /dev/nsa0 rewind backup# tar -tf /dev/nsa0 log/ log/mbw01.log (insert rest of correct tar listing) backup# mt -f /dev/nsa0 fsf backup# tar -tf /dev/nsa0 mbw01.log (insert rest of correct tar listing) backup# mt -f /dev/nsa0 fsf backup# tar -tf /dev/nsa0 log/ log/mbw01.log (insert rest of correct tar listing) backup# mt -f /dev/nsa0 fsf backup# tar -tf /dev/nsa0 mbw01.log (insert rest of correct tar listing) backup# mt -f /dev/nsa0 fsf So, when I tell it to forward space file at the end of each tar file, it is able to read all four files correctly. This leaves me scratching my head, and wondering what the heck I've set up wrong. Any ideas? Tape drivers _always_ write two EOFs when the tape device is closed. This ensures there is always a valid 'EOT' on the tape. They're _suppoesed_ to backspace over the 2nd EOF mark, so that a subsequent write has only one EOF between it and the prior file. Looks like your drive isn't doing the 'backspace' right. I suspect the 'easiest' work around is the one you've discovered -- do an 'mt -fsf' after avery tape file 'read'. OK, I feel pretty dense When you're saying they write two EOFs when the device is closed, would this happen every time you write a file? Or would it be every time the tape is unmounted? Or would that depend on the program you're using? Is there any way I could test to make sure this is in fact what's happening? And would the problem with it not doing the backspace right be an issue with the FreeBSD tape driver? Or SCSI card driver? Or what driver? Obviously not a problem with the drive itself, since I don't have this problem with Ubuntu. Unfortunately, the "workaround" of running mt -fsf after every file read isn't really usable workaround.I need the tape drive to work with bacula, not just running tars. Where do I go from here? Thanks, Renee ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Problem reading from tape drive
I recently purchased a FreeBSD-compatible SAS card (an Adaptec ASR 2045) and moved our backup server from Ubuntu to FreeBSD 8.2. I am trying to set up the backup software, but am having problems with the tape drive. Hopefully this is a "duh" type question, since I have a lot more experience working with tape drives in Ubuntu than FreeBSD. I installed bacula, and ran the test function in the btape utility. It wrote 1 blocks, wrote EOF, wrote 1 blocks, wrote EOF, wrote EOF. Rewound the tape. Read 1 blocks, failed reading the second 1 blocks. I had no luck researching the bacula error message, so I switched to mt and tar for further troubleshooting. camcontrol devlist does show the tape drive: backup# camcontrol devlist at scbus2 target 0 lun 0 (sa0,pass0) So then I went into a directory that had one subdirectory, which contained several plain text logfiles. I did four tars, alternating between that directory and the subdirectory (so I would be able to see a difference between the tar files). backup# mt -f /dev/nsa0 rewind backup# tar -cf /dev/nsa0 * backup# cd log/ backup# tar -cf /dev/nsa0 * backup# cd .. backup# tar -cf /dev/nsa0 * backup# cd log/ backup# tar -cf /dev/nsa0 * So far so good. Then I went back to read those tar files. backup# mt -f /dev/nsa0 rewind backup# tar -tf /dev/nsa0 log/ log/mbw01.log (insert rest of correct tar listing) backup# tar -tf /dev/nsa0 tar: Unrecognized archive format tar: Error exit delayed from previous errors. Sosame results as bacula's tape test utility was giving.it writes, it reads the first file, then errors on trying to read the second file. However: backup# mt -f /dev/nsa0 rewind backup# tar -tf /dev/nsa0 log/ log/mbw01.log (insert rest of correct tar listing) backup# mt -f /dev/nsa0 fsf backup# tar -tf /dev/nsa0 mbw01.log (insert rest of correct tar listing) backup# mt -f /dev/nsa0 fsf backup# tar -tf /dev/nsa0 log/ log/mbw01.log (insert rest of correct tar listing) backup# mt -f /dev/nsa0 fsf backup# tar -tf /dev/nsa0 mbw01.log (insert rest of correct tar listing) backup# mt -f /dev/nsa0 fsf So, when I tell it to forward space file at the end of each tar file, it is able to read all four files correctly. This leaves me scratching my head, and wondering what the heck I've set up wrong. Any ideas? Thanks, Renee Gehlbach ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
RE: LTO3 tape drive not detected
Seems in theory that LTO 3 should work ok based on this forum post: http://forums.freebsd.org/showthread.php?t=8042 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: LTO3 tape drive not detected
Adam Vande More wrote: > On Thu, Jun 23, 2011 at 9:35 AM, Joe in MPLS wrote: > > > The system sees the SCSI controller as mpt0, and it seems to know there's > > something at SCSI ID 4, but I get an "AutoSense Failed" for hba/id/lun 0:4:0 > > at boot and subsequent camcontrol rescans. > > > > I checked the supported hardware doc for the release but it doesn't get > > very specific about tape drives. This is my first experience with LTO3 tape. > > I was hoping that I'd automagically get a /dev/sa0 device like I always did > > with my old DLT drives but it wasn't to be this time. > > > > Is there a way to make this drive work? > > > > I don't the answer to your question, it's been quite some time since I > worked with a tape drive. Off-topic question, what type of capacities to > tapes support now days? > > I think think you may have more luck posting this question to a different > list, stable@ is the one that comes to mind for me. Could also ask on s...@freebsd.org Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Reply below, not above; Indent with "> "; Cumulative like a play script. Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: LTO3 tape drive not detected
On Thu, 23 Jun 2011 09:35:10 -0500, Joe in MPLS wrote: > > I have FreeBSD 8.2-RELEASE running on an HP DL360 G5. I recently added > an (HP branded) LSI Logic single channel SCSI 320 card and attached an > HP Ultrium 920 LTO3 tape drive. > > The system sees the SCSI controller as mpt0, and it seems to know > there's something at SCSI ID 4, but I get an "AutoSense Failed" for > hba/id/lun 0:4:0 at boot and subsequent camcontrol rescans. > > I checked the supported hardware doc for the release but it doesn't get > very specific about tape drives. This is my first experience with LTO3 > tape. I was hoping that I'd automagically get a /dev/sa0 device like I > always did with my old DLT drives but it wasn't to be this time. > > Is there a way to make this drive work? For better diagnostics, use the camcontrol utility, options reset, rescan, devlist and inquiry, after the system successfully booted. There should be a listing containing the tape drive and therefore the device node in /dev, or a more descriptive error message if something is wrong. % camcontrol devlist at scbus0 target 6 lun 0 (pass0) at scbus2 target 0 lun 0 (cd0,pass1) This example shows a SCSI scanner at 0:6:0, the controller is an Adaptec 2940 SCSI adapter (PCI), driver is ahc0, as real SCSI hardware. If you're using the ATAPICAM facility, don't get confused with the ATAPI devices being on that list too. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: LTO3 tape drive not detected
On Thu, Jun 23, 2011 at 9:35 AM, Joe in MPLS wrote: > The system sees the SCSI controller as mpt0, and it seems to know there's > something at SCSI ID 4, but I get an "AutoSense Failed" for hba/id/lun 0:4:0 > at boot and subsequent camcontrol rescans. > > I checked the supported hardware doc for the release but it doesn't get > very specific about tape drives. This is my first experience with LTO3 tape. > I was hoping that I'd automagically get a /dev/sa0 device like I always did > with my old DLT drives but it wasn't to be this time. > > Is there a way to make this drive work? > I don't the answer to your question, it's been quite some time since I worked with a tape drive. Off-topic question, what type of capacities to tapes support now days? I think think you may have more luck posting this question to a different list, stable@ is the one that comes to mind for me. -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
LTO3 tape drive not detected
I have FreeBSD 8.2-RELEASE running on an HP DL360 G5. I recently added an (HP branded) LSI Logic single channel SCSI 320 card and attached an HP Ultrium 920 LTO3 tape drive. The system sees the SCSI controller as mpt0, and it seems to know there's something at SCSI ID 4, but I get an "AutoSense Failed" for hba/id/lun 0:4:0 at boot and subsequent camcontrol rescans. I checked the supported hardware doc for the release but it doesn't get very specific about tape drives. This is my first experience with LTO3 tape. I was hoping that I'd automagically get a /dev/sa0 device like I always did with my old DLT drives but it wasn't to be this time. Is there a way to make this drive work? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Tape drive for backup soloution
On Tue, 29 Mar 2011 16:56:18 +1030 William Brown wrote: > Are there any recommendations that you can make about compatible > solutions. My knowledge in this area is limited. My needs are not so big and I use HP Ultrium 448 (LTO-2) drive, but I'm sure that buying HP's LTO-2 drive will be nice solution for you. btw, I recently switched from Bacula to Amanda, but I'm just in the process of moving to (Free)PCBSD, but I'm sure drive is supported well. Otoh, I also heard that IBM's drives are not bad and usually cheaper than HP brand. Sincerely, Gour -- “In the material world, conceptions of good and bad are all mental speculations…” (Sri Caitanya Mahaprabhu) http://atmarama.net | Hlapicina (Croatia) | GPG: CDBF17CA signature.asc Description: PGP signature
Tape drive for backup soloution
Hi I need to implement a tape drive backup solution at my place of work. I was wondering what is a good tape drive to get for this task, that works on freebsd with something like amanda. Its for a small business, and storing about 4TB max, and hopefully with some room spare for differential backups over time. My server on hand has sata and IDE available. Are there any recommendations that you can make about compatible solutions. My knowledge in this area is limited. Sincerely, William Brown Research & Teaching, Technology Services The University of Adelaide, AUSTRALIA 5005 CRICOS Provider Number 00123M - IMPORTANT: This message may contain confidential or legally privileged information. If you think it was sent to you by mistake, please delete all copies and advise the sender. For the purposes of the SPAM Act 2003, this email is authorised by The University of Adelaide. pgp.mit.edu PGP.sig Description: This is a digitally signed message part
Re: Sata Tape Drives
Il 07/16/10 00:24, Dan Nelson ha scritto: In the last episode (Jul 15), Michael Anderson said: Or, more clearly: Are SATA tape drives supported? I see they are on some other BSD flavors, but I haven't found any mention in the FreeBSD hardware compatibility documents. I see an "atapist" device in /sys/conf/NOTES: device atapist # ATAPI tape drives , which might work. The "atapicam" or "ahci" device may also make sata tapes show up as if they were scsi devices. Try "ahci" first. http://www.freebsd.org/cgi/man.cgi?query=ahci http://www.freebsd.org/cgi/man.cgi?query=atapicam And please, in case you try, let us know the results... I know I'm not helping you, but I've tried many times to find out whether SATA *and SAS* tape drives are expected to work. bye & Thanks av. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Sata Tape Drives
In the last episode (Jul 15), Michael Anderson said: > Or, more clearly: Are SATA tape drives supported? I see they are on some > other BSD flavors, but I haven't found any mention in the FreeBSD hardware > compatibility documents. I see an "atapist" device in /sys/conf/NOTES: device atapist # ATAPI tape drives , which might work. The "atapicam" or "ahci" device may also make sata tapes show up as if they were scsi devices. Try "ahci" first. http://www.freebsd.org/cgi/man.cgi?query=ahci http://www.freebsd.org/cgi/man.cgi?query=atapicam -- Dan Nelson dnel...@allantgroup.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Sata Tape Drives
Or, more clearly: Are SATA tape drives supported? I see they are on some other BSD flavors, but I haven't found any mention in the FreeBSD hardware compatibility documents. Will the OS just see a tape drive on a SATA controller as a sequential-access SCSI device the way it sees SATA disks as SCSI block devices? Quoting Michael Anderson : Hello, I'm looking to replace a busted tape drive with a Quantum DLT SATA drive. Is this supported? Thanks! -- Michael Anderson IT Services & Support elego Software Solutions GmbH Gustav-Meyer-Allee 25 Building 12.3 (BIG) room 227 13355 Berlin, Germany phone +49 30 23 45 86 96 michael.anderson at elegosoft.com fax +49 30 23 45 86 95 http://www.elegosoft.com Geschaeftsfuehrer: Olaf Wagner, Sitz Berlin Amtsgericht Berlin-Charlottenburg, HRB 77719, USt-IdNr: DE163214194 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" -- Michael Anderson IT Services & Support elego Software Solutions GmbH Gustav-Meyer-Allee 25 Building 12.3 (BIG) room 227 13355 Berlin, Germany phone +49 30 23 45 86 96 michael.anderson at elegosoft.com fax +49 30 23 45 86 95 http://www.elegosoft.com Geschaeftsfuehrer: Olaf Wagner, Sitz Berlin Amtsgericht Berlin-Charlottenburg, HRB 77719, USt-IdNr: DE163214194 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Sata Tape Drives
Hello, I'm looking to replace a busted tape drive with a Quantum DLT SATA drive. Is this supported? Thanks! -- Michael Anderson IT Services & Support elego Software Solutions GmbH Gustav-Meyer-Allee 25 Building 12.3 (BIG) room 227 13355 Berlin, Germany phone +49 30 23 45 86 96 michael.anderson at elegosoft.com fax +49 30 23 45 86 95 http://www.elegosoft.com Geschaeftsfuehrer: Olaf Wagner, Sitz Berlin Amtsgericht Berlin-Charlottenburg, HRB 77719, USt-IdNr: DE163214194 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Quantum DLT SATA tape drive
Hello, I'm looking to replace a busted tape ATA DAT drive with a Quantum DLT SATA drive. Is this supported? Thanks! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Tape changer/robot
>Is there someway I can get it to auto change tape? Take a look at mtx, in the ports collection at misc/mtx, a SCSI media changer and device control package. R's, John ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Promise TX4302 eSATA card doesn't play with a Quantum DLT-v4 tape drive
On 04/12/10 11:50, Mark wrote: I have the promise controller, I got it to add dvd burners to the system, but it will not work with the dvd drives. The promise site says the card is atapi compliant but it did not work that way for me. I had to move hard drives to the promise and add the dvd burners to the on board esata. YMMV Good grief. Thanks for the information. -- Kirk Strauser ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Promise TX4302 eSATA card doesn't play with a Quantum DLT-v4 tape drive
On 04/12/10 10:50, Mark wrote: Would you need to load atapicam into the kernel?? That doesn't seem to change things. I'll try again later today by rebooting with atapicam_load="YES" in /boot/loader.conf just for giggles. -- Kirk Strauser ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Promise TX4302 eSATA card doesn't play with a Quantum DLT-v4 tape drive
I have a FreeBSD 8 server with a Quantum DLT-v4 tape drive. I'd been using it over USB but want to switch to eSATA for various reasons. Here's the dmesg entry for the drive when connected via USB: sa0 at umass-sim0 bus 0 scbus0 target 0 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 40.000MB/s transfers Here are snippets of dmesg when connecting the drive via the new Promise TX4302 card I just installed: atapci0: port 0xdc80-0xdcff,0xd800-0xd8ff mem 0xdfbff000-0xdfbf,0xdfbc-0xdfbd irq 66 at device 7.0 on pci3 atapci0: [ITHREAD] atapci0: [ITHREAD] ata2: on atapci0 ata3: on atapci0 ata4: on atapci0 ata5: on atapci0 ata3: SIGNATURE: eb140101 ast0: FAILURE - MODE_SENSE timed out ata3: SIGNATURE: eb140101 ast0: FAILURE - MODE_SENSE timed out ata3: SIGNATURE: eb140101 ast0: FAILURE - MODE_SENSE timed out ata3: SIGNATURE: eb140101 ast0: FAILURE - MODE_SENSE timed out ata3: SIGNATURE: eb140101 ast0: FAILURE - MODE_SENSE timed out device_attach: ast0 attach returned 6 ...and then device ast0 never appears. Any idea how I can get these two pieces of hardware to play nicely together? -- Kirk Strauser ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
USB Tape Drives
Hello. Just a quick question before I buy... Are USB tape drives working? On 7.2? On 8.0? bye & Thanks av. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: HP USB 2.0 Tape Drive
On Fri, Dec 11, 2009 at 04:52:37AM +0100, Polytropon wrote: > On Thu, 10 Dec 2009 09:50:56 -0500, Jerry McAllister wrote: > > I don't think you will have a problem using a USB2 interface. > > But, I really cannot recommend DAT. That type of system seems > > to have been pushed beyond its ability.The tapes fail > > frequently. > > What about Ultrium tape? Is it better? Yes. I like the LTO tape system. It writes and reads fast. It seems reliable, though I haven't used it as heavily. It is missing a fast file search ability, so although it reads fast, it takes a while to find files. It is also expensive - like DLT - but if cheap fails, then that is really the most expensive. It is cheaper to get something that is reliable even if it has a higher price. jerry > > > But, if you can't read what you thought you wrote, it > > doesn't matter how fast you can search for it. > > A backup not readable is NOT a backup. And because it > isn't, your hard disks will fail. :-) > > -- > Polytropon > Magdeburg, Germany > Happy FreeBSD user since 4.0 > Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: HP USB 2.0 Tape Drive
Hi, I'm looking to buy a tape drive and am currently looking at USB 2.0 DAT tape drives from HP. I searched the hardware compatibility list and cannot locate any information tape drives except the disclaimer that SCSI tape drives do work on SCSI controller cards that are recognized by the FreeBSD OS. The only thing I can find is that apparently the ehci driver must be used if USB 2.0 interface is to be used with a tape drive. Does anyone have had positive or negative experience using these USB-based DAT tape drives? Specifically, I am looking at the HP (Hewlett-Packard) StorageWorks Q1581SB DAT 160 Tape Drive. If there are other branded USB 2.0-based tape drives (i.e. Quantum) that you've used with little or no problems, I would be interested in knowing about these. I have been using the usb HP Dat drives with ml115 servers with out any problems. They have been detected and work fine Terry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: HP USB 2.0 Tape Drive
On Thu, 10 Dec 2009 09:50:56 -0500, Jerry McAllister wrote: > I don't think you will have a problem using a USB2 interface. > But, I really cannot recommend DAT. That type of system seems > to have been pushed beyond its ability.The tapes fail > frequently. What about Ultrium tape? Is it better? > But, if you can't read what you thought you wrote, it > doesn't matter how fast you can search for it. A backup not readable is NOT a backup. And because it isn't, your hard disks will fail. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: HP USB 2.0 Tape Drive
On Wed, Dec 09, 2009 at 03:50:04PM -0800, Doug Sampson wrote: > Does anyone have had positive or negative experience using these USB-based > DAT tape drives? Specifically, I am looking at the HP (Hewlett-Packard) > StorageWorks Q1581SB DAT 160 Tape Drive. If there are other branded USB > 2.0-based tape drives (i.e. Quantum) that you've used with little or no > problems, I would be interested in knowing about these. Apparently the umass driver supports at least some models, they are reported as sa(4) devices; see http://lists.freebsd.org/pipermail/freebsd-questions/2005-November/104550.html I don't know if the speed problems in abovementioned message still exist. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgprbYJj7qfAI.pgp Description: PGP signature
Re: HP USB 2.0 Tape Drive
On Wed, Dec 09, 2009 at 03:50:04PM -0800, Doug Sampson wrote: > Hi, > > I'm looking to buy a tape drive and am currently looking at USB 2.0 DAT tape > drives from HP. I searched the hardware compatibility list and cannot locate > any information tape drives except the disclaimer that SCSI tape drives do > work on SCSI controller cards that are recognized by the FreeBSD OS. The > only thing I can find is that apparently the ehci driver must be used if USB > 2.0 interface is to be used with a tape drive. > > Does anyone have had positive or negative experience using these USB-based > DAT tape drives? Specifically, I am looking at the HP (Hewlett-Packard) > StorageWorks Q1581SB DAT 160 Tape Drive. If there are other branded USB > 2.0-based tape drives (i.e. Quantum) that you've used with little or no > problems, I would be interested in knowing about these. I don't think you will have a problem using a USB2 interface. But, I really cannot recommend DAT. That type of system seems to have been pushed beyond its ability.The tapes fail frequently.The only thing nice about DAT is its rapid search ability. But, if you can't read what you thought you wrote, it doesn't matter how fast you can search for it. jerry > > ~Doug > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: HP USB 2.0 Tape Drive
On Wed, 9 Dec 2009 17:09:05 -0800 , Doug Sampson wrote: > All I just want to know is whether FBSD will recognize and work with the > tape drive I posed in my previous email (the Hewlett-Packard StorageWorks > Q1581SB DAT 160 Tape Drive). Will it be identified as /dev/da* something? I would guess it will identify as /dev/sa* (da = direct access, sa = sequential access), at least SCSI tape drives occur in that manner. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
RE: HP USB 2.0 Tape Drive
> Hi Doug, > > > Does anyone have had positive or negative experience using > these USB-based > > DAT tape drives? Specifically, I am looking at the HP > (Hewlett-Packard) > > I know that I am not really answering your question but here are a > couple of thoughts that came to my mind when reading your post: > > - USB 2 should be able to sustain the transfer speed to stream your > DAT drive, I checked that point; > > - I always considered DAT one of the worse tape solution myself, too > sensitive to the physical conditions, too prone to errors, could > never read a tape after 6 months; > Interesting points you raise. I have owned several DAT drives (Quantum, Sony, and HP) over the past 17 years and have yet to lose ability to restore data due to bad tapes. I am careful where I store these between use. I use these with SCSI interfaces on Windows systems with one exception- I use a SCSI-based Sony DDS DAT 12/24 tape drive in a FBSD system running PGSQL. All I just want to know is whether FBSD will recognize and work with the tape drive I posed in my previous email (the Hewlett-Packard StorageWorks Q1581SB DAT 160 Tape Drive). Will it be identified as /dev/da* something? Can any one of you confirm if you got any USB 2.0 tape drive to work with FBSD? I like the fact that I can just plug a USB tape drive into a new system in seconds without having to fuss about installing a SCSI/SAS card and have a tape back up made relatively soon. As a side note: I had trouble getting certain branded USB external hard drives recognized by FreeBSD. I ended up using LaCie hard drives as these were listed as being compatible. Thus I am cautious about anything that uses USB in general with FreeBSD. I just got off the phone with a Quantum technical staffer and he was stymied by my question whether their USB 2.0 DAT 160 tape drive would be recognized by FBSD. He pushed me off to a sales representative who is just got off for the day. ~Doug ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: HP USB 2.0 Tape Drive
Hi Doug, > Does anyone have had positive or negative experience using these USB-based > DAT tape drives? Specifically, I am looking at the HP (Hewlett-Packard) I know that I am not really answering your question but here are a couple of thoughts that came to my mind when reading your post: - USB 2 should be able to sustain the transfer speed to stream your DAT drive, I checked that point; - I always considered DAT one of the worse tape solution myself, too sensitive to the physical conditions, too prone to errors, could never read a tape after 6 months; - why spending money in a 80GB tape drive when you can have 10TB of hard disk for the same price; I beleive you have a bunch of existing tapes that hold data you must read. Then I would plug my USB DAT to any operating system that supports it, transfer the data to some hard disc, and be done with the tapes. And if FreeBSD cannot use the tape drive, as it is a one time task only, I would go for some other OS. Good luck, Olivier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
HP USB 2.0 Tape Drive
Hi, I'm looking to buy a tape drive and am currently looking at USB 2.0 DAT tape drives from HP. I searched the hardware compatibility list and cannot locate any information tape drives except the disclaimer that SCSI tape drives do work on SCSI controller cards that are recognized by the FreeBSD OS. The only thing I can find is that apparently the ehci driver must be used if USB 2.0 interface is to be used with a tape drive. Does anyone have had positive or negative experience using these USB-based DAT tape drives? Specifically, I am looking at the HP (Hewlett-Packard) StorageWorks Q1581SB DAT 160 Tape Drive. If there are other branded USB 2.0-based tape drives (i.e. Quantum) that you've used with little or no problems, I would be interested in knowing about these. ~Doug ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: small question about tape-based dumps
On Sat, Oct 17, 2009 at 08:09:22PM -0600, Tim Judd wrote: > On 10/17/09, Stevan Tiefert wrote: > > Am Samstag, den 17.10.2009, 18:49 -0600 schrieb Tim Judd: > >> On 10/17/09, Jerry McAllister wrote: > >> > >> > >> > You do not need to. dump alrady writes that when it finishes each time. > >> > If you to that, you will get a second one at that location. > >> > > >> > You do not need to do the rewind and mt fsf between each dump. I just > >> > do it to make it very clear to myself in my scripts what I am expecting > >> > and that I am doing it right. > >> > > >> > jerry > >> > >> > >> > >> If dump is the tool for tapes, and tar is named after tape archives... > > > > Please, no flamewar!!! > > Wasn't planning on starting one. Sorry if it came across that way. > > > > >> Do both of these utilities write the *proper* EOF to whatever medium > >> it's writing to? > > > > They both write EOF. > > > >> I bring this up, because dump can also write to a file on a formatted > >> FS. Does the file end with this same EOF? What does tar do? > > > > There is only one EOF: The EOF. > > > > > >> Why have a mt weof function if it's useless? I'm loosing the logic in > >> this one, trying to make sure things work as they should. I admit > >> tapes on bsd are so foreign to me, I might as well be speaking > >> $another-language. > > > > weof is not useless. There are some file operations without writing an > > EOF, like streams or something like that, but tar and dump are writing > > with an EOF at the end of files :-) > > > So it's a item for "good measure" rather than an item "as necessity" > in creating backups. Not a good measure. It would do something different from what you expect. You might get 2 EOF-s in a row and the system think you have two files - one with stuff and one empty one. jerry > > Thanks for all the info. I'm happy knowing more. > > > --Tim > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: small question about tape-based dumps
On Sat, Oct 17, 2009 at 06:49:02PM -0600, Tim Judd wrote: > On 10/17/09, Jerry McAllister wrote: > > > > You do not need to. dump alrady writes that when it finishes each time. > > If you to that, you will get a second one at that location. > > > > You do not need to do the rewind and mt fsf between each dump. I just > > do it to make it very clear to myself in my scripts what I am expecting > > and that I am doing it right. > > > > jerry > > > > If dump is the tool for tapes, and tar is named after tape archives... > > Do both of these utilities write the *proper* EOF to whatever medium > it's writing to? > > I bring this up, because dump can also write to a file on a formatted > FS. Does the file end with this same EOF? What does tar do? EOF means something completely different on a file system than it does on a tape. So, yes, the system knows where the file ends on both, but it is done differently. jerry > > Why have a mt weof function if it's useless? I'm loosing the logic in > this one, trying to make sure things work as they should. I admit > tapes on bsd are so foreign to me, I might as well be speaking > $another-language. It is not useless. It just isn't necessary in that situation. Remember, mt(1) is used on more than just dumps. jerry > > > Please help. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: small question about tape-based dumps
On 10/17/09, Stevan Tiefert wrote: > Am Samstag, den 17.10.2009, 18:49 -0600 schrieb Tim Judd: >> On 10/17/09, Jerry McAllister wrote: >> >> >> > You do not need to. dump alrady writes that when it finishes each time. >> > If you to that, you will get a second one at that location. >> > >> > You do not need to do the rewind and mt fsf between each dump. I just >> > do it to make it very clear to myself in my scripts what I am expecting >> > and that I am doing it right. >> > >> > jerry >> >> >> >> If dump is the tool for tapes, and tar is named after tape archives... > > Please, no flamewar!!! Wasn't planning on starting one. Sorry if it came across that way. > >> Do both of these utilities write the *proper* EOF to whatever medium >> it's writing to? > > They both write EOF. > >> I bring this up, because dump can also write to a file on a formatted >> FS. Does the file end with this same EOF? What does tar do? > > There is only one EOF: The EOF. > > >> Why have a mt weof function if it's useless? I'm loosing the logic in >> this one, trying to make sure things work as they should. I admit >> tapes on bsd are so foreign to me, I might as well be speaking >> $another-language. > > weof is not useless. There are some file operations without writing an > EOF, like streams or something like that, but tar and dump are writing > with an EOF at the end of files :-) So it's a item for "good measure" rather than an item "as necessity" in creating backups. Thanks for all the info. I'm happy knowing more. --Tim ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: small question about tape-based dumps
Am Samstag, den 17.10.2009, 18:49 -0600 schrieb Tim Judd: > On 10/17/09, Jerry McAllister wrote: > > > > You do not need to. dump alrady writes that when it finishes each time. > > If you to that, you will get a second one at that location. > > > > You do not need to do the rewind and mt fsf between each dump. I just > > do it to make it very clear to myself in my scripts what I am expecting > > and that I am doing it right. > > > > jerry > > > > If dump is the tool for tapes, and tar is named after tape archives... Please, no flamewar!!! > Do both of these utilities write the *proper* EOF to whatever medium > it's writing to? They both write EOF. > I bring this up, because dump can also write to a file on a formatted > FS. Does the file end with this same EOF? What does tar do? There is only one EOF: The EOF. > Why have a mt weof function if it's useless? I'm loosing the logic in > this one, trying to make sure things work as they should. I admit > tapes on bsd are so foreign to me, I might as well be speaking > $another-language. weof is not useless. There are some file operations without writing an EOF, like streams or something like that, but tar and dump are writing with an EOF at the end of files :-) > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: small question about tape-based dumps
On 10/17/09, Jerry McAllister wrote: > You do not need to. dump alrady writes that when it finishes each time. > If you to that, you will get a second one at that location. > > You do not need to do the rewind and mt fsf between each dump. I just > do it to make it very clear to myself in my scripts what I am expecting > and that I am doing it right. > > jerry If dump is the tool for tapes, and tar is named after tape archives... Do both of these utilities write the *proper* EOF to whatever medium it's writing to? I bring this up, because dump can also write to a file on a formatted FS. Does the file end with this same EOF? What does tar do? Why have a mt weof function if it's useless? I'm loosing the logic in this one, trying to make sure things work as they should. I admit tapes on bsd are so foreign to me, I might as well be speaking $another-language. Please help. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: small question about tape-based dumps
On Fri, Oct 16, 2009 at 08:43:26PM -0600, Tim Judd wrote: > Replies inline > > On 10/16/09, Jerry McAllister wrote: > > On Fri, Oct 16, 2009 at 11:13:21PM +0200, Stevan Tiefert wrote: > > > >> Hello list, > >> > >> one example: If I have three partitions and I want to backup every day > >> these partitions, will I need 21 tapes? > >> > >> I ask because it seems it is not possible to place more than one dump on > >> one tape, isn't it? > > > > You can easily put more than one dump on a tape if there is > > room enough for them. Check out the mt(1) command. > > > > Something like mt fsf 1will skip over the first dump file > > so you can write the second.mt fsf 2 will skip over two files, etc. > > That is dump files, not files within the dump. Each dump of a > > filesystem is one file. > > > > If you need to restore, it is just the same. The first dump is > > the first file. The second dump is reached by skipping 1 file > > with the mt command, etc. > > > > I actually rewind and skip between each dump of multiples made > > to the same tape. I also use the no-rewind device for the tape. > > > > So first dump is:dump 0af /dev/nsa0 / > > I understand that this creates a dumpfile on nsa0, and as I understand > tapes (which may be wrong, which I ask for clarification here).. To > mark a end-of-file to be able to fast-forward/rewind, why can't you > use: > mt -f /dev/nsa0 weof > > It's description in mt(1) says it writes the end-of-file mark at > current position You do not need to. dump alrady writes that when it finishes each time. If you to that, you will get a second one at that location. You do not need to do the rewind and mt fsf between each dump. I just do it to make it very clear to myself in my scripts what I am expecting and that I am doing it right. jerry > > > For second dump: mt -f /dev/nsa0 rewind > > mt -f /dev/nsa0 fsf 1 > > dump 0af /dev/nsa0 /usr > > So if we use weof, would the 2nd dump then be: > dump 0af /dev/nsa0 /usr > mt -f /dev/nsa0 weof > > > thirdmt -f /dev/nsa0 rewind > > mt -f /dev/nsa0 fsf 2 > > dump 0af /dev/nsa0 /var > > And 3rd: > dump 0af /dev/nsa0 /var > mt -f /dev/nsa0 weof > > > etc. > > > > when all donemt -f /dev/nsa0 rewind > > mt -f /dev/nsa0 offline > > And I've never used offline, guess I'll start now. > > > I have this all in a script that also writes an index file > > as the first file on the tape. > > > > Of course if you are doing a change dump the dump command is > > going to look more like: > > > > dump 1af /dev/nsa0 > > etc. > > > > jerry > > > >> > >> With regards > >> Stevan Tiefert > > > > Thanks for any input! > --TJ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: small question about tape-based dumps
>> On Fri, 16 Oct 2009 17:37:32 -0400, >> Jerry McAllister said: J> You can easily put more than one dump on a tape if there is room enough J> for them. I actually rewind and skip between each dump of multiples J> made to the same tape. I also use the no-rewind device for the tape. Whenever possible, I set aside a 4-8 Gb partition for a staging area. This has helped me avoid several nasty tape problems: a. Dump to a file on the staging area, compressing it if possible. b. Get an MD5/SHA1/whatever signature for the dump. c. Write it to tape. When all the dumps are finished, rewind the tape. Read each tape file, get the signature, and compare it to what you got before; this way, you know your backup is good. Tapes stretch and wrinkle, tape heads get out of alignment, tapes can "bleed" over time, etc. There are few things worse than trying to restore someone's file and finding out you have a screwed backup. Another advantage of a staging area is better tape use; if you're copying a single file to tape (most of which is still in cache from the signature check), the tape drive won't spend as much time polishing the heads waiting for something to write. -- Karl Vogel I don't speak for the USAF or my company The RAID was dirty *and* degraded (insert "your mom" joke here). --Mike Markley on Slashdot discussing Linux drives ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: small question about tape-based dumps
Am Freitag, den 16.10.2009, 20:43 -0600 schrieb Tim Judd: > Replies inline > > On 10/16/09, Jerry McAllister wrote: --8< snip, snap... --8< > > Something like mt fsf 1will skip over the first dump file > > so you can write the second.mt fsf 2 will skip over two files, etc. > > That is dump files, not files within the dump. Each dump of a > > filesystem is one file. --8< snip, snap... --8< That means, that after ervery dump, the tape drive is automatically writing an EOF. It is not necessary to write with mt -f /dev/nsa0 weof the EOF again. > > Thanks for any input! > --TJ With regards Stevan Tiefert ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: small question about tape-based dumps
Replies inline On 10/16/09, Jerry McAllister wrote: > On Fri, Oct 16, 2009 at 11:13:21PM +0200, Stevan Tiefert wrote: > >> Hello list, >> >> one example: If I have three partitions and I want to backup every day >> these partitions, will I need 21 tapes? >> >> I ask because it seems it is not possible to place more than one dump on >> one tape, isn't it? > > You can easily put more than one dump on a tape if there is > room enough for them. Check out the mt(1) command. > > Something like mt fsf 1will skip over the first dump file > so you can write the second.mt fsf 2 will skip over two files, etc. > That is dump files, not files within the dump. Each dump of a > filesystem is one file. > > If you need to restore, it is just the same. The first dump is > the first file. The second dump is reached by skipping 1 file > with the mt command, etc. > > I actually rewind and skip between each dump of multiples made > to the same tape. I also use the no-rewind device for the tape. > > So first dump is:dump 0af /dev/nsa0 / I understand that this creates a dumpfile on nsa0, and as I understand tapes (which may be wrong, which I ask for clarification here).. To mark a end-of-file to be able to fast-forward/rewind, why can't you use: mt -f /dev/nsa0 weof It's description in mt(1) says it writes the end-of-file mark at current position > For second dump: mt -f /dev/nsa0 rewind > mt -f /dev/nsa0 fsf 1 > dump 0af /dev/nsa0 /usr So if we use weof, would the 2nd dump then be: dump 0af /dev/nsa0 /usr mt -f /dev/nsa0 weof > thirdmt -f /dev/nsa0 rewind > mt -f /dev/nsa0 fsf 2 > dump 0af /dev/nsa0 /var And 3rd: dump 0af /dev/nsa0 /var mt -f /dev/nsa0 weof > etc. > > when all donemt -f /dev/nsa0 rewind > mt -f /dev/nsa0 offline And I've never used offline, guess I'll start now. > I have this all in a script that also writes an index file > as the first file on the tape. > > Of course if you are doing a change dump the dump command is > going to look more like: > > dump 1af /dev/nsa0 > etc. > > jerry > >> >> With regards >> Stevan Tiefert Thanks for any input! --TJ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: small question about tape-based dumps
Am Freitag, den 16.10.2009, 17:37 -0400 schrieb Jerry McAllister: > On Fri, Oct 16, 2009 at 11:13:21PM +0200, Stevan Tiefert wrote: > > > Hello list, > > > > one example: If I have three partitions and I want to backup every day > > these partitions, will I need 21 tapes? > > > > I ask because it seems it is not possible to place more than one dump on > > one tape, isn't it? > > You can easily put more than one dump on a tape if there is > room enough for them. Check out the mt(1) command. > > Something like mt fsf 1will skip over the first dump file > so you can write the second.mt fsf 2 will skip over two files, etc. > That is dump files, not files within the dump. Each dump of a > filesystem is one file. > > If you need to restore, it is just the same. The first dump is > the first file. The second dump is reached by skipping 1 file > with the mt command, etc. > > I actually rewind and skip between each dump of multiples made > to the same tape. I also use the no-rewind device for the tape. > > So first dump is:dump 0af /dev/nsa0 / > > For second dump: mt -f /dev/nsa0 rewind > mt -f /dev/nsa0 fsf 1 > dump 0af /dev/nsa0 /usr > > thirdmt -f /dev/nsa0 rewind > mt -f /dev/nsa0 fsf 2 > dump 0af /dev/nsa0 /var > > etc. > > when all donemt -f /dev/nsa0 rewind > mt -f /dev/nsa0 offline > > I have this all in a script that also writes an index file > as the first file on the tape. > > Of course if you are doing a change dump the dump command is > going to look more like: > > dump 1af /dev/nsa0 > etc. > > jerry > > > > > With regards > > Stevan Tiefert > > > > > > > > ___ > > freebsd-questions@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" > Hello Jerry, The world can be so easy!!! Thanks for this hint :-) With regards Stevan Tiefert ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: small question about tape-based dumps
On Fri, Oct 16, 2009 at 11:13:21PM +0200, Stevan Tiefert wrote: > Hello list, > > one example: If I have three partitions and I want to backup every day > these partitions, will I need 21 tapes? > > I ask because it seems it is not possible to place more than one dump on > one tape, isn't it? You can easily put more than one dump on a tape if there is room enough for them. Check out the mt(1) command. Something like mt fsf 1will skip over the first dump file so you can write the second.mt fsf 2 will skip over two files, etc. That is dump files, not files within the dump. Each dump of a filesystem is one file. If you need to restore, it is just the same. The first dump is the first file. The second dump is reached by skipping 1 file with the mt command, etc. I actually rewind and skip between each dump of multiples made to the same tape. I also use the no-rewind device for the tape. So first dump is:dump 0af /dev/nsa0 / For second dump: mt -f /dev/nsa0 rewind mt -f /dev/nsa0 fsf 1 dump 0af /dev/nsa0 /usr thirdmt -f /dev/nsa0 rewind mt -f /dev/nsa0 fsf 2 dump 0af /dev/nsa0 /var etc. when all donemt -f /dev/nsa0 rewind mt -f /dev/nsa0 offline I have this all in a script that also writes an index file as the first file on the tape. Of course if you are doing a change dump the dump command is going to look more like: dump 1af /dev/nsa0 etc. jerry > > With regards > Stevan Tiefert > > > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
small question about tape-based dumps
Hello list, one example: If I have three partitions and I want to backup every day these partitions, will I need 21 tapes? I ask because it seems it is not possible to place more than one dump on one tape, isn't it? With regards Stevan Tiefert ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Odd behavior after installing a tape drive
> From: Polytropon > Subject: Re: Odd behavior after installing a tape drive > To: "Tim Judd" > Cc: mahle...@yahoo.com, freebsd-questions@freebsd.org > Date: Monday, July 20, 2009, 12:22 AM > On Sun, 19 Jul 2009 21:43:29 -0600, > Tim Judd > wrote: > > I'm no expert on tape drives either, but I was sure > that "losing a > > SCSI device" is a bad thing for SCSI -- think of it as > an IDE drive. > > you don't just go pulling power or data from a > running, booted > > computer. > > With SCSI, "hot plug" is usually not that problematic as > with > "modern" ATA and SATA on the PC. Anyway, using > > # camcontrol stop > > before switching off or detaching a SCSI component is often > a > good idea. > > > > > All the devices in a computer are on, stays on, until > the system shuts down. > > SCSI allows you to have "internal devices" outside the > computer, > connected with a cable. In principle, it doesn't even > matter if > a hard disk is inside the computer or outside, same for > optical > disc drives, tape drives, and even scanners. "Hot plug" has > always > been a nice feature of SCSI, even 10 or more years ago, > where > you couldn't imagine something similar in the PC world. > > > > > The PTY/SCSI subject of your email should be > unrelated, but a abruptly > > missing device is never a positive outcome for an > OS. Think about the > > old "removing a mounted USB drive = panic" issue we've > dealt with for > > years. > > Or /dev/mem: device disappeared. :-) > > > > > I am questioning your reasoning behind turning off a > tape drive on a > > live system. I would never recommend that. > > As I said, if you do it "the SCSI way", it's completely > unproblematic. > > > > > -- > Polytropon > From Magdeburg, Germany > Happy FreeBSD user since 4.0 > Andra moi ennepe, Mousa, ... > Thanks! I'll do that in the future - I was getting the idea that since camcontrol *includes* a "stop" command I should have done that before pulling the power anyway. :) I still don't know if the two items were related in any way, but I'm not really that worried about it unless it happens again - or at least more than once in a blue moon. I'll have a bit of time this week to test taking it down and back up a few times the "correct" way and see if it exhibits any of the same behavior. Thanks again! -Rich ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Odd behavior after installing a tape drive
On Sun, 19 Jul 2009 21:43:29 -0600, Tim Judd wrote: > I'm no expert on tape drives either, but I was sure that "losing a > SCSI device" is a bad thing for SCSI -- think of it as an IDE drive. > you don't just go pulling power or data from a running, booted > computer. With SCSI, "hot plug" is usually not that problematic as with "modern" ATA and SATA on the PC. Anyway, using # camcontrol stop before switching off or detaching a SCSI component is often a good idea. > All the devices in a computer are on, stays on, until the system shuts down. SCSI allows you to have "internal devices" outside the computer, connected with a cable. In principle, it doesn't even matter if a hard disk is inside the computer or outside, same for optical disc drives, tape drives, and even scanners. "Hot plug" has always been a nice feature of SCSI, even 10 or more years ago, where you couldn't imagine something similar in the PC world. > The PTY/SCSI subject of your email should be unrelated, but a abruptly > missing device is never a positive outcome for an OS. Think about the > old "removing a mounted USB drive = panic" issue we've dealt with for > years. Or /dev/mem: device disappeared. :-) > I am questioning your reasoning behind turning off a tape drive on a > live system. I would never recommend that. As I said, if you do it "the SCSI way", it's completely unproblematic. -- Polytropon >From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Odd behavior after installing a tape drive
I'm no expert on tape drives either, but I was sure that "losing a SCSI device" is a bad thing for SCSI -- think of it as an IDE drive. you don't just go pulling power or data from a running, booted computer. All the devices in a computer are on, stays on, until the system shuts down. The PTY/SCSI subject of your email should be unrelated, but a abruptly missing device is never a positive outcome for an OS. Think about the old "removing a mounted USB drive = panic" issue we've dealt with for years. I am questioning your reasoning behind turning off a tape drive on a live system. I would never recommend that. On 7/19/09, mahle...@yahoo.com wrote: > > After installing a tape drive and SCSI card in my home system, I got some > strange behavior that I think isn't directly related, but would like to get > an expert opinion about. > > mobius# uname -a > FreeBSD mobius 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #0: Fri Sep 5 02:34:20 > CDT 2008 r...@mobius:/usr/obj/usr/src/sys/GENERIC i386 > > On July 7, I turned off the system, installed the SCSI card, connected the > drive and turned it all back on. This all got correctly detected as (select > lines from /var/log/messages): > > Jul 7 03:10:40 mobius kernel: asr0: mem > 0xf400-0xf5ff irq 17 at device 12.1 on pci2 > Jul 7 03:10:40 mobius kernel: asr0: [GIANT-LOCKED] > Jul 7 03:10:40 mobius kernel: asr0: [ITHREAD] > Jul 7 03:10:40 mobius kernel: asr0: ADAPTEC 2100S FW Rev. 370F, 1 > channel, 256 CCBs, Protocol I2O > Jul 7 03:10:40 mobius kernel: sa0 at asr0 bus 0 target 11 lun 0 > Jul 7 03:10:40 mobius kernel: sa0: Removable > Sequential Access SCSI-3 device > > I stuck in a tape, did a level 0 dump of /home and tested a restore, both of > which worked perfectly. > > Only July 8, I ejected the tape via the button on the front, and then turned > off the tape drive so the visiting relatives wouldn't complain about the fan > noise (more from /var/log/messages): > Jul 8 02:27:01 mobius kernel: (sa0:asr0:0:11:0): lost device > > That next week, I tried to SSH to this box from work to do some minor random > thing or another, and I got this sort of error message: > Jul 14 15:27:16 mobius sshd[64290]: error: openpty: Invalid argument > Jul 14 15:27:16 mobius sshd[64293]: error: session_pty_req: session 0 alloc > failed > > I believe I had SSHed to it at least twice over the preceding week, on July > 10 and early in the day on July 14. > > As the system was running perfectly in all other ways (well, at least the > wife hadn't complained her network files were offline, which is the only > important thing!), it took a few days before I finally got around to logging > in at the console and rebooting it after which it has seemed to be fine. > The system has been eminently stable other than this one issue one time. > > I have not been able to find much from Google about this other than the > following two items- > > A) very specific bugs against different SSH versions than I am using. Doubt > this is the problem. > > B) some issues some folks have had with needing to create /dev/pty or > similar items. While it seems far fetched, this is the first time the > system was up with a new device and ... I don't know. New device in the > system and an old device goes wonky within a week seems to be a bit of a > coincidence. > > ** Does anyone have any thoughts if these are related or not? ** > > Also, any tips, tricks or sites with working with tape drives on FreeBSD > would be appreciated! (The handbook is a bit sparse on this point and I'm > used to autoloaders and better under Windows/Backup Exec). I'm learning my > way around camcontrol and mt, but should only need such things in certain > circumstances, like to get the tape drive "back" after turning it off for a > while, right? > > > > > > > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Odd behavior after installing a tape drive
After installing a tape drive and SCSI card in my home system, I got some strange behavior that I think isn't directly related, but would like to get an expert opinion about. mobius# uname -a FreeBSD mobius 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #0: Fri Sep 5 02:34:20 CDT 2008 r...@mobius:/usr/obj/usr/src/sys/GENERIC i386 On July 7, I turned off the system, installed the SCSI card, connected the drive and turned it all back on. This all got correctly detected as (select lines from /var/log/messages): Jul 7 03:10:40 mobius kernel: asr0: mem 0xf400-0xf5ff irq 17 at device 12.1 on pci2 Jul 7 03:10:40 mobius kernel: asr0: [GIANT-LOCKED] Jul 7 03:10:40 mobius kernel: asr0: [ITHREAD] Jul 7 03:10:40 mobius kernel: asr0: ADAPTEC 2100S FW Rev. 370F, 1 channel, 256 CCBs, Protocol I2O Jul 7 03:10:40 mobius kernel: sa0 at asr0 bus 0 target 11 lun 0 Jul 7 03:10:40 mobius kernel: sa0: Removable Sequential Access SCSI-3 device I stuck in a tape, did a level 0 dump of /home and tested a restore, both of which worked perfectly. Only July 8, I ejected the tape via the button on the front, and then turned off the tape drive so the visiting relatives wouldn't complain about the fan noise (more from /var/log/messages): Jul 8 02:27:01 mobius kernel: (sa0:asr0:0:11:0): lost device That next week, I tried to SSH to this box from work to do some minor random thing or another, and I got this sort of error message: Jul 14 15:27:16 mobius sshd[64290]: error: openpty: Invalid argument Jul 14 15:27:16 mobius sshd[64293]: error: session_pty_req: session 0 alloc failed I believe I had SSHed to it at least twice over the preceding week, on July 10 and early in the day on July 14. As the system was running perfectly in all other ways (well, at least the wife hadn't complained her network files were offline, which is the only important thing!), it took a few days before I finally got around to logging in at the console and rebooting it after which it has seemed to be fine. The system has been eminently stable other than this one issue one time. I have not been able to find much from Google about this other than the following two items- A) very specific bugs against different SSH versions than I am using. Doubt this is the problem. B) some issues some folks have had with needing to create /dev/pty or similar items. While it seems far fetched, this is the first time the system was up with a new device and ... I don't know. New device in the system and an old device goes wonky within a week seems to be a bit of a coincidence. ** Does anyone have any thoughts if these are related or not? ** Also, any tips, tricks or sites with working with tape drives on FreeBSD would be appreciated! (The handbook is a bit sparse on this point and I'm used to autoloaders and better under Windows/Backup Exec). I'm learning my way around camcontrol and mt, but should only need such things in certain circumstances, like to get the tape drive "back" after turning it off for a while, right? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Adaptec 29320ALP-R and tape drive
The pciconf -l line for the controller would be useful. Some other debug data may be useful too, but I'll need to review some code first before I know what more I need. -- Justin Jay Hall wrote: That worked. Would any of the information displayed while booting be helpful at this point? Jay On Jul 7, 2009, at 10:46 AM, Justin T. Gibbs wrote: Go into the card 29320's BIOS and configure your tape drive for non-packetized negotiation. If this works, we can try a few other things in the driver to see if it is possible to get things working in packetized mode. -- Justin Jay Hall wrote: I just installed an Adaptec 29320ALP-R in my FreeBSD 7.2 server. Connected to the card is an HP Ultrium 1/8 G2 tape drive. During the boot sequence, FreeBSD pauses to wait for the SCSI devices to settle. Then, I receive the following message (probe79:ahd0:0:4:0: Probable outgoing LQ CRC error. Retrying command. I have moved the card to a different slot with the same results, replaced the cable, etc. If I do not power on the tape drive, the system will boot normally. Any suggestions would be greatly appreciated. Thanks, Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Adaptec 29320ALP-R and tape drive
That worked. Would any of the information displayed while booting be helpful at this point? Jay On Jul 7, 2009, at 10:46 AM, Justin T. Gibbs wrote: Go into the card 29320's BIOS and configure your tape drive for non- packetized negotiation. If this works, we can try a few other things in the driver to see if it is possible to get things working in packetized mode. -- Justin Jay Hall wrote: I just installed an Adaptec 29320ALP-R in my FreeBSD 7.2 server. Connected to the card is an HP Ultrium 1/8 G2 tape drive. During the boot sequence, FreeBSD pauses to wait for the SCSI devices to settle. Then, I receive the following message (probe79:ahd0:0:4:0: Probable outgoing LQ CRC error. Retrying command. I have moved the card to a different slot with the same results, replaced the cable, etc. If I do not power on the tape drive, the system will boot normally. Any suggestions would be greatly appreciated. Thanks, Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org " ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Adaptec 29320ALP-R and tape drive
Go into the card 29320's BIOS and configure your tape drive for non-packetized negotiation. If this works, we can try a few other things in the driver to see if it is possible to get things working in packetized mode. -- Justin Jay Hall wrote: I just installed an Adaptec 29320ALP-R in my FreeBSD 7.2 server. Connected to the card is an HP Ultrium 1/8 G2 tape drive. During the boot sequence, FreeBSD pauses to wait for the SCSI devices to settle. Then, I receive the following message (probe79:ahd0:0:4:0: Probable outgoing LQ CRC error. Retrying command. I have moved the card to a different slot with the same results, replaced the cable, etc. If I do not power on the tape drive, the system will boot normally. Any suggestions would be greatly appreciated. Thanks, Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Adaptec 29320ALP-R and tape drive
I just installed an Adaptec 29320ALP-R in my FreeBSD 7.2 server. Connected to the card is an HP Ultrium 1/8 G2 tape drive. During the boot sequence, FreeBSD pauses to wait for the SCSI devices to settle. Then, I receive the following message (probe79:ahd0:0:4:0: Probable outgoing LQ CRC error. Retrying command. I have moved the card to a different slot with the same results, replaced the cable, etc. If I do not power on the tape drive, the system will boot normally. Any suggestions would be greatly appreciated. Thanks, Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Formatting a tape?
This looks like a hardware problem to me. However, I don't have any experience with this type of SCSI hardware. If it were my system I'd be double-checking the tape drive setup, cabling and termination, and then substituting other cables and SCSI controllers. One thing that confuses me is that the DLT drive is shown as a SCSI-2 device but is nonetheless running with 160MB/sec transfers. On my system (7.1-STABLE, SM P6DC6, onboard Adaptec 7899 UW160 controller, external Overland AIT# library I get the following: ahc0: port 0x9400-0x94ff mem 0xf3021000- 0xf3021fff irq 18 at device 4.0 on pci3 ahc0: [ITHREAD] ahc1: port 0x9800-0x98ff mem 0xf3022000- 0xf3022fff irq 18 at device 4.1 on pci3 ahc1: [ITHREAD] sa0 at ahc1 bus 0 target 4 lun 0 sa0 at ahc1 bus 0 target 4 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 40.000MB/s transfers (20.000MHz, offset 127, 16bit) On Thu, 19 Mar 2009, Jaime wrote: On Thu, Mar 19, 2009 at 2:18 PM, Michael L. Squires wrote: Have you looked at /var/log/messages? I've found error messages written there when trying to write to a tape which showed that I needed to change the block size. Good idea, but sadly there is nothing useful there. The following happened during my tinkering with mt, tar, and dd: Mar 19 14:06:32 atlas kernel: sa0 at ahc0 bus 0 target 6 lun 0 Mar 19 14:06:32 atlas kernel: sa0: Removable Sequential Access SCSI-2 device Mar 19 14:06:32 atlas kernel: sa0: 160.000MB/s transfers (80.000MHz, offset 96, 16bit) Mar 19 14:23:46 atlas kernel: (sa0:ahc0:0:6:0): Unexpected busfree in Data-out phase Mar 19 14:23:46 atlas kernel: SEQADDR == 0x86 Mar 19 14:23:46 atlas kernel: (sa0:ahc0:0:6:0): lost device Mar 19 14:23:46 atlas kernel: (sa0:ahc0:0:6:0): failed to write terminating filemark(s) Mar 19 14:23:47 atlas kernel: (sa0:ahc0:0:6:0): tape is now frozen- use an OFFLINE, REWIND or MTEOM command to clear this state. Mar 19 14:23:47 atlas kernel: (sa0:ahc0:0:6:0): removing device entry Mar 19 14:27:37 atlas kernel: sa0 at ahc0 bus 0 target 6 lun 0 Mar 19 14:27:37 atlas kernel: sa0: Removable Sequential Access SCSI-2 device Mar 19 14:27:37 atlas kernel: sa0: 160.000MB/s transfers (80.000MHz, offset 96, 16bit) Mar 19 14:29:19 atlas kernel: (sa0:ahc0:0:6:0): lost device Mar 19 14:29:19 atlas kernel: (sa0:ahc0:0:6:0): removing device entry Jaime ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Formatting a tape?
On Thu, 19 Mar 2009, Jaime wrote: On Thu, Mar 19, 2009 at 7:37 PM, Warren Block wrote: And the device acts flaky. That screams "SCSI termination problem" to me. That would also be consistent with most/all of the tapes failing, because it's not the tapes. I've checked the termination more times than I can remember. (No exaggeration. Problem had been on-going for months.) Its OK. I have one bent pin on one of the two "ports" on the SCSI cable, but it (1) isn't the one being used and (2) doesn't touch any other pins. Its just an unusable "port" on the cable, not a source of ... "cross contamination," I guess you could say. Two terminators, one at each end of the bus? Another possibility is that the terminators are fine, but nothing is providing termpower (blown fuse or jumper). And there are different SCSI bus widths. The more devices you have, the more interesting it gets. So I am pretty sure that we're OK on the SCSI chain. I *am* starting to wonder about the tape drive itself, though. Could be the drive, or could be cables. If you have other devices on the bus and they work fine on large, fast transfers, then suspect the tape drive. If you can get that one tape to work repeatedly but none of the other tapes will, maybe a bad batch of tapes. -Warren Block * Rapid City, South Dakota USA___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Formatting a tape?
On Thu, Mar 19, 2009 at 7:37 PM, Warren Block wrote: > And the device acts flaky. That screams "SCSI termination problem" to me. > That would also be consistent with most/all of the tapes failing, because > it's not the tapes. I've checked the termination more times than I can remember. (No exaggeration. Problem had been on-going for months.) Its OK. I have one bent pin on one of the two "ports" on the SCSI cable, but it (1) isn't the one being used and (2) doesn't touch any other pins. Its just an unusable "port" on the cable, not a source of ... "cross contamination," I guess you could say. So I am pretty sure that we're OK on the SCSI chain. I *am* starting to wonder about the tape drive itself, though. What do you think? Thanks again, Jaime ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Formatting a tape?
On Thu, 19 Mar 2009, Jaime wrote: On Thu, Mar 19, 2009 at 1:39 PM, Andrew Hamilton-Wright wrote: What happens if you use dd to try and write to the tape? The command dd if=/dev/zero of=/dev/sa0 count=8 should print out: 8+0 records in 8+0 records out I tried this and the output was: 8+0 records in 8+0 records out 4096 bytes transferred in 0.036611 secs (111879 bytes/sec) Small write works okay... So then I tried my backup script (which is basically a tar command) and got this on the console: (sa0:ahc0:0:6:0): Unexpected busfree in Data-out phase SEQADDR == 0x86 (sa0:ahc0:0:6:0): lost device (sa0:ahc0:0:6:0): failed to write terminating filemark(s) (sa0:ahc0:0:6:0): tape is now frozen- use an OFFLINE, REWIND, or MTEOM command to clear this state. (sa0:ahc0:0:6:0): removing device entry Bigger write fails... On the ssh terminal / standard output, I got this: tar: Write error: Input/output error Now "camcontrol devlist" doesn't show the tape drive, even though it did before. And the device acts flaky. That screams "SCSI termination problem" to me. That would also be consistent with most/all of the tapes failing, because it's not the tapes. ... I'm going to tinker some more and see if I can get this drive working again. I'll also try another tape. (Its worth noting that I DID manage to get a tape working thanks to mt -f /dev/sa0 fsf 1 && mt -f /dev/sa0 rewind.) More info later. Try that one working tape again. Betcha it "fails". -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Formatting a tape?
Try this : mt -f /dev/nsa0 rewind mt -f /dev/nsa0 weof 1 mt -f /dev/nsa0 rewind On Thu, 2009-03-19 at 12:15 -0400, Jaime wrote: > I have a DLT tape drive in a FreeBSD system. With one of the tapes, I > can get "tar -cvpf /dev/sa0 -C / ." to work. With all the other > tapes, I can't. > > Is there some kind of formatting process that I need to do? I tried > "mt fsf 1" from this page: > > http://www.freebsd.org/doc/en/books/handbook/backups-tapebackups.html > > This didn't seem to work, though. > > Any help is appreciated, > Jaime > -- Julien Cigar Belgian Biodiversity Platform http://www.biodiversity.be Université Libre de Bruxelles (ULB) Campus de la Plaine CP 257 Bâtiment NO, Bureau 4 N4 115C (Niveau 4) Boulevard du Triomphe, entrée ULB 2 B-1050 Bruxelles Mail: jci...@ulb.ac.be @biobel: http://biobel.biodiversity.be/person/show/471 Tel : 02 650 57 52 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Formatting a tape?
mt rewind should suffice. AFAIK DLT tapes doesn't need to be formatted On Thu, 19 Mar 2009, Jaime wrote: I have a DLT tape drive in a FreeBSD system. With one of the tapes, I can get "tar -cvpf /dev/sa0 -C / ." to work. With all the other tapes, I can't. Is there some kind of formatting process that I need to do? I tried "mt fsf 1" from this page: http://www.freebsd.org/doc/en/books/handbook/backups-tapebackups.html This didn't seem to work, though. Any help is appreciated, Jaime -- "To affect the quality of the day, that is the highest of arts." -- Henry David Thoreau Tone of voice in email is misunderstood 50% of the time. Source: http://www.howtoweb.com/cgi-bin/insider.pl?zone=214061 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Formatting a tape?
Have you looked at /var/log/messages? I've found error messages written there when trying to write to a tape which showed that I needed to change the block size. I've used DLT tapes with a variety of SCSI controllers from 4.X to 6.X, and don't remember having to change anything to use "tar cvf /dev/sa0 *". Those were DLTIII/DLTIII+/DLT40 tape. I'm currently using AIT3 tapes in an Overland library which works very well. Mike Squires ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Formatting a tape?
On Thu, Mar 19, 2009 at 2:18 PM, Michael L. Squires wrote: > Have you looked at /var/log/messages? I've found error messages written > there when trying to write to a tape which showed that I needed to change > the block size. Good idea, but sadly there is nothing useful there. The following happened during my tinkering with mt, tar, and dd: Mar 19 14:06:32 atlas kernel: sa0 at ahc0 bus 0 target 6 lun 0 Mar 19 14:06:32 atlas kernel: sa0: Removable Sequential Access SCSI-2 device Mar 19 14:06:32 atlas kernel: sa0: 160.000MB/s transfers (80.000MHz, offset 96, 16bit) Mar 19 14:23:46 atlas kernel: (sa0:ahc0:0:6:0): Unexpected busfree in Data-out phase Mar 19 14:23:46 atlas kernel: SEQADDR == 0x86 Mar 19 14:23:46 atlas kernel: (sa0:ahc0:0:6:0): lost device Mar 19 14:23:46 atlas kernel: (sa0:ahc0:0:6:0): failed to write terminating filemark(s) Mar 19 14:23:47 atlas kernel: (sa0:ahc0:0:6:0): tape is now frozen- use an OFFLINE, REWIND or MTEOM command to clear this state. Mar 19 14:23:47 atlas kernel: (sa0:ahc0:0:6:0): removing device entry Mar 19 14:27:37 atlas kernel: sa0 at ahc0 bus 0 target 6 lun 0 Mar 19 14:27:37 atlas kernel: sa0: Removable Sequential Access SCSI-2 device Mar 19 14:27:37 atlas kernel: sa0: 160.000MB/s transfers (80.000MHz, offset 96, 16bit) Mar 19 14:29:19 atlas kernel: (sa0:ahc0:0:6:0): lost device Mar 19 14:29:19 atlas kernel: (sa0:ahc0:0:6:0): removing device entry Jaime ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Formatting a tape?
On Thu, Mar 19, 2009 at 12:15:48PM -0400, Jaime wrote: > I have a DLT tape drive in a FreeBSD system. With one of the tapes, I > can get "tar -cvpf /dev/sa0 -C / ." to work. With all the other > tapes, I can't. > > Is there some kind of formatting process that I need to do? I tried > "mt fsf 1" from this page: > > http://www.freebsd.org/doc/en/books/handbook/backups-tapebackups.html > > This didn't seem to work, though. Tapes do not need to be formatted, though the issue mentioned in the page you indicate can cause problems.I have seen it a lot on DAT (DDS) tapes and never with a DLT. On the DAT tapes, the solutions given on that page have usually not helped for me. But, since I have never had any problem with DLT tapes, I can't say if they might be helpful. You can try writing a block or two to the drive using dd(1). That occasionally helped with the DAT (DDS) tapes. dd count=10 if=/dev/zero of=/dev/nsa0 Seems like it should have a bs=nn in there too, but I can't remember if the default of 512 is OK or not. jerry > > Any help is appreciated, > Jaime > > -- > "To affect the quality of the day, that is the highest of arts." -- > Henry David Thoreau > > Tone of voice in email is misunderstood 50% of the time. > Source: http://www.howtoweb.com/cgi-bin/insider.pl?zone=214061 > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Formatting a tape?
On Thu, Mar 19, 2009 at 1:39 PM, Andrew Hamilton-Wright wrote: > What happens if you use dd to try and write to the tape? > > The command >dd if=/dev/zero of=/dev/sa0 count=8 > should print out: >8+0 records in >8+0 records out I tried this and the output was: 8+0 records in 8+0 records out 4096 bytes transferred in 0.036611 secs (111879 bytes/sec) So then I tried my backup script (which is basically a tar command) and got this on the console: (sa0:ahc0:0:6:0): Unexpected busfree in Data-out phase SEQADDR == 0x86 (sa0:ahc0:0:6:0): lost device (sa0:ahc0:0:6:0): failed to write terminating filemark(s) (sa0:ahc0:0:6:0): tape is now frozen- use an OFFLINE, REWIND, or MTEOM command to clear this state. (sa0:ahc0:0:6:0): removing device entry On the ssh terminal / standard output, I got this: tar: Write error: Input/output error Now "camcontrol devlist" doesn't show the tape drive, even though it did before. So I use "camcontrol rescan all" and it comes back. On console, it says: sa0 at ahc0 bus 0 target 6 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 160.000MB/s transfers (80.000MHz, offset 96, 16 bit) So then I try: mt -f /dev/sa0 rewind mt: /dev/sa0: Device not configured atlas:jkikpole>camcontrol devlist at scbus0 target 0 lun 0 (pass0) at scbus0 target 1 lun 0 (pass1) at scbus0 target 2 lun 0 (pass2) at scbus1 target 0 lun 0 (da0,pass3) WTF? Its gone again. On console, I get: (sa0:ahc0:0:6:0): lost device (sa0:ahc0:0:6:0): removing device entry I'm going to tinker some more and see if I can get this drive working again. I'll also try another tape. (Its worth noting that I DID manage to get a tape working thanks to mt -f /dev/sa0 fsf 1 && mt -f /dev/sa0 rewind.) More info later. Thanks for the help Jaime ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Formatting a tape?
On Mar 19, 2009, at 9:15 AM, Jaime wrote: I have a DLT tape drive in a FreeBSD system. With one of the tapes, I can get "tar -cvpf /dev/sa0 -C / ." to work. With all the other tapes, I can't. Is there some kind of formatting process that I need to do? I tried "mt fsf 1" from this page: What's the SCSI controller that you're using, and which version of the OS are you running? What's "mt status" say? Can you try "mt blocksize 0", "mt rewind", "mt weof 2", "mt rewind" and then retry tar? Try changing your blocksize via tar's -b flag to 32, 64, 126, or 128 blocks. FreeBSD doesn't expose enabling/disabling hardware compression or tuning compression levels via the device name used (ala Solaris' /dev/rmt/0ubn for example), so you'll need to look to "mt blocksize" and "mt comp" to adjust, otherwise you'll get whatever default behavior the device is set to. In most cases, the device will want a fairly large blocksize in order to keep streaming the tape. (I've used both Quantum DLT and sDLT drives with FreeBSD 5.x & 6.x on various Adaptec & LSI MegaRAID SCSI controllers-- mostly Dell, some HP boxen) Regards, -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Formatting a tape?
> I assume that this is a fresh tape? Do other tapes from the same batch > work? Thanks for the reply. Yes, 10 new tapes. All Sony brand "DLTape VS1" on the box. (Only one "t". Damn marketers.) They all have this symptom. > What happens if you use dd to try and write to the tape? I'll give it a try. I've only used tar and mt so far. Thanks, Jaime -- "To affect the quality of the day, that is the highest of arts." -- Henry David Thoreau Tone of voice in email is misunderstood 50% of the time. Source: http://www.howtoweb.com/cgi-bin/insider.pl?zone=214061 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Formatting a tape?
On Thu, 19 Mar 2009, Jaime wrote: I have a DLT tape drive in a FreeBSD system. With one of the tapes, I can get "tar -cvpf /dev/sa0 -C / ." to work. With all the other tapes, I can't. Is there some kind of formatting process that I need to do? I tried "mt fsf 1" from this page: I assume that this is a fresh tape? Do other tapes from the same batch work? What happens if you use dd to try and write to the tape? The command dd if=/dev/zero of=/dev/sa0 count=8 should print out: 8+0 records in 8+0 records out If you are getting something else, I might suspect a physical media problem. I have certainly gotten the odd dud tape before. A. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Formatting a tape?
I have a DLT tape drive in a FreeBSD system. With one of the tapes, I can get "tar -cvpf /dev/sa0 -C / ." to work. With all the other tapes, I can't. Is there some kind of formatting process that I need to do? I tried "mt fsf 1" from this page: http://www.freebsd.org/doc/en/books/handbook/backups-tapebackups.html This didn't seem to work, though. Any help is appreciated, Jaime -- "To affect the quality of the day, that is the highest of arts." -- Henry David Thoreau Tone of voice in email is misunderstood 50% of the time. Source: http://www.howtoweb.com/cgi-bin/insider.pl?zone=214061 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Quantum tape drive
On Jan 28, 2009, at 4:47 PM, Warren Block wrote: There's also the issue of terminator power, which may have been supplied by the old drive but not by the new one. Yes, usually a jumper is available. Also used to be one-shot fuses before the Raychem self-reseting PTC Polyswitch fuses. -- David Kelly N4HHE, dke...@hiwaay.net Whom computers would destroy, they must first drive mad. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Quantum tape drive
On Wed, 28 Jan 2009, Jaime wrote: On Wed, Jan 28, 2009 at 4:51 PM, Wojciech Puchar wrote: When reading from the tape using tar (bsdtar from FreeBSD 6.2 -- and, yes, I'm preparing a cvsup as I write this :) ) the tape drive's Alarm and Fault LEDs are lit up and then camcontrol devlist no longer shows the tape drive. TERMINATION PROBLEM I was thinking of that... I shut down the server and checked the usual suspects (terminator on the cable, SCSI IDs, etc.) but didn't find anything out of place. Also, the same command in Knoppix (Linux) using /dev/st0 (the Linux equivalent of /dev/sa0) appeared to write to the tape and then list the items on that tape. I didn't see how long it would take, though. In retrospect, maybe I should have let that run longer. :( How certain are you that its a termination problem? It could just be a bad drive or tape, but termination was the first thing that came to mind for me also. The drive giving a fault on a read like that suggests it. Pardon the obvious, but remember that termination is needed at both ends of the SCSI bus, and only at the ends. There's also the issue of terminator power, which may have been supplied by the old drive but not by the new one. -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Quantum tape drive
On Wed, Jan 28, 2009 at 05:06:55PM -0500, Jaime wrote: > On Wed, Jan 28, 2009 at 4:51 PM, Wojciech Puchar > > > > TERMINATION PROBLEM > > I was thinking of that... I shut down the server and checked the > usual suspects (terminator on the cable, SCSI IDs, etc.) but didn't > find anything out of place. Also, the same command in Knoppix (Linux) > using /dev/st0 (the Linux equivalent of /dev/sa0) appeared to write to > the tape and then list the items on that tape. I didn't see how long > it would take, though. In retrospect, maybe I should have let that > run longer. :( > > How certain are you that its a termination problem? I'm tending to "certainly" agree. There are other things to consider as well, such as narrow, wide, ultra, and ultra-LVDT. Active termination and passive termination. Is there termination at the SCSI card? You said there was termination on the cable, but is there also on-board termination on the drive? No other drive on the bus has termination enabled? One terminator on each end of the bus, no more, no less. -- David Kelly N4HHE, dke...@hiwaay.net Whom computers would destroy, they must first drive mad. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Quantum tape drive
On Wed, Jan 28, 2009 at 4:51 PM, Wojciech Puchar wrote: >> When reading from the tape using tar (bsdtar from FreeBSD 6.2 -- and, >> yes, I'm preparing a cvsup as I write this :) ) the tape drive's Alarm >> and Fault LEDs are lit up and then camcontrol devlist no longer shows >> the tape drive. > > TERMINATION PROBLEM I was thinking of that... I shut down the server and checked the usual suspects (terminator on the cable, SCSI IDs, etc.) but didn't find anything out of place. Also, the same command in Knoppix (Linux) using /dev/st0 (the Linux equivalent of /dev/sa0) appeared to write to the tape and then list the items on that tape. I didn't see how long it would take, though. In retrospect, maybe I should have let that run longer. :( How certain are you that its a termination problem? Thanks, Jaime ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Quantum tape drive
On Wed, Jan 28, 2009 at 03:49:39PM -0600, Dan Nelson wrote: > In the last episode (Jan 28), Jaime said: > > > > Thanks. Would this decrease the ability of other Unixes being able > > to read the tape? For example, using pax (which can read tar > > archives) or GNU's tar? > > It shouldn't. At worst you may have to specify a matching blocksize > argument when reading. I once had problems with an SGI user writing tapes with megabyte block size. Works on ancient SGI IRIX but nowhere else that I know of. Worse, IRIX remembered the last block size used on a tape device, across multiple users. Learned to always set block size when writing else no telling how it would go. -- David Kelly N4HHE, dke...@hiwaay.net Whom computers would destroy, they must first drive mad. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Quantum tape drive
misc/buffer, and misc/cstream in ports are good for this. Thanks. Would this decrease the ability of other Unixes being able to read the tape? For example, using pax (which can read tar archives) or GNU's tar? no just use -b in other unices too :) When reading from the tape using tar (bsdtar from FreeBSD 6.2 -- and, yes, I'm preparing a cvsup as I write this :) ) the tape drive's Alarm and Fault LEDs are lit up and then camcontrol devlist no longer shows the tape drive. TERMINATION PROBLEM ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Quantum tape drive
I am trying to replace an older DLT tape drive (which doesn't like to eject tapes any more) with a new Quantum DLT-4 drive. Its connected by internal SCSI and seems to be set up right. But after DAYS of running a tar command, its still not done backing up 60GB. The old drive could backup 70-80GB in about 7 hours. try mt setblk 0 and then tar -b 64 some drives gets locked with small blocks. and most can get locked with improper termination ;) check it. I changed my backup script to include a -v flag in the tar command, and it now lists hundreds or possibly thousands of files. But it never even gets to /home before I killed the process (after 9 hours in this case). Any suggestions? If it helps, the backup script and output from camcontrol follows. However, this script is the same one that worked on the other drive. A quick test with a Knoppix disk suggested that the backups ran faster in Linux. Not positive of this, but it might be true. $ cat /etc/periodic/daily/910.backups #!/bin/sh # echo echo "Tape archives:" dow=`/bin/date +%w` if test "$dow" -gt 1; then echo " Beginning backup." /usr/bin/uptime /usr/bin/tar -cvpX /usr/local/etc/backups/skiplist-relative.txt -f /dev/sa0 -C / . /usr/bin/uptime else echo " Today is a weekend. Skipping backups." fi $ camcontrol devlist at scbus0 target 0 lun 0 (pass0) at scbus0 target 1 lun 0 (pass1) at scbus0 target 2 lun 0 (pass2) at scbus1 target 0 lun 0 (da0,pass3) at scbus2 target 4 lun 0 (sa0,pass4) Any help is greatly appreciated. Thanks in advance, Jaime ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Quantum tape drive
On Wed, Jan 28, 2009 at 4:27 PM, David Kelly wrote: > You list -v as a tar option. Is tar sticking on a file? I just added that to my script in order to see what was going on. I didn't use it a week ago. I'm dumping straight to the tar drive. Look at the tar command again and you'll see /dev/sa0 in there. :) > Another question is whether or not tar could be getting caught in a hard > link or symbolic link infinite loop? Look for duplicates in the output. > uniq(1) should be of assistance. Perhaps uniq needs a sort(1) to > preprocess, I forget? Not a bad thought. However, I'm certain that there is no recursion going on. The delays are happening too early on for that. Also, this script works well if I target an external HD but never finishes on the tape. Thanks for the idea. I hadn't considered it before. Jaime ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Quantum tape drive
In the last episode (Jan 28), Jaime said: > On Wed, Jan 28, 2009 at 3:23 PM, Dan Nelson wrote: > > > > In the last episode (Jan 28), Jaime said: > >> /usr/bin/tar -cvpX /usr/local/etc/backups/skiplist-relative.txt -f > >> /dev/sa0 -C / . > > > > If nothing else, I suggest bumping up your blocksize. The default for > > tar (10k) is pretty small for modern tape drives. Try -b 128 (for a 64k > > block size). Another optimization would be to put a buffering program > > in between tar and your tape drive to decouple disk reads from tape > > writes. misc/team, misc/buffer, and misc/cstream in ports are good for > > this. > > Thanks. Would this decrease the ability of other Unixes being able to > read the tape? For example, using pax (which can read tar archives) > or GNU's tar? It shouldn't. At worst you may have to specify a matching blocksize argument when reading. > Sadly, I forgot to mention something in my last message. Sorry. > > When reading from the tape using tar (bsdtar from FreeBSD 6.2 -- and, > yes, I'm preparing a cvsup as I write this :) ) the tape drive's Alarm > and Fault LEDs are lit up and then camcontrol devlist no longer shows > the tape drive. According to http://downloads.quantum.com/dlt_v4/DLT-V4_Product_Manual_81-81422-03_A01.pdf#page=67 , there is no alarm LED on a DLT-V4 drive, just Ready, Fault, Clean, and Media. If the Fault light is lit solid, it says that's an "Internal firmware error". If Fault and Clean are blinking slowly, you may have a bad tape or may need to put a cleaning tape in. > After I wrote to the tape via a quick boot into Knoppix, I found that > FreeBSD's tar command could list the files on the tape. So maybe that is > in the past now. Maybe not. I should have mentioned it earlier. Sorry. > > Any other thoughts before I try to OS update and the larger block size? -- Dan Nelson dnel...@allantgroup.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Quantum tape drive
On Wed, Jan 28, 2009 at 03:38:43PM -0500, Jaime wrote: > > > > In the last episode (Jan 28), Jaime said: > >> /usr/bin/tar -cvpX /usr/local/etc/backups/skiplist-relative.txt -f > >> /dev/sa0 -C / . [...] > Any other thoughts before I try to OS update and the larger block size? You list -v as a tar option. Is tar sticking on a file? Another question is whether or not tar could be getting caught in a hard link or symbolic link infinite loop? Look for duplicates in the output. uniq(1) should be of assistance. Perhaps uniq needs a sort(1) to preprocess, I forget? -- David Kelly N4HHE, dke...@hiwaay.net Whom computers would destroy, they must first drive mad. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Quantum tape drive
On Wed, Jan 28, 2009 at 3:23 PM, Dan Nelson wrote: > > In the last episode (Jan 28), Jaime said: >> /usr/bin/tar -cvpX /usr/local/etc/backups/skiplist-relative.txt -f >> /dev/sa0 -C / . > > If nothing else, I suggest bumping up your blocksize. The default for tar > (10k) is pretty small for modern tape drives. Try -b 128 (for a 64k block > size). Another optimization would be to put a buffering program in between > tar and your tape drive to decouple disk reads from tape writes. misc/team, > misc/buffer, and misc/cstream in ports are good for this. Thanks. Would this decrease the ability of other Unixes being able to read the tape? For example, using pax (which can read tar archives) or GNU's tar? Sadly, I forgot to mention something in my last message. Sorry. When reading from the tape using tar (bsdtar from FreeBSD 6.2 -- and, yes, I'm preparing a cvsup as I write this :) ) the tape drive's Alarm and Fault LEDs are lit up and then camcontrol devlist no longer shows the tape drive. After I wrote to the tape via a quick boot into Knoppix, I found that FreeBSD's tar command could list the files on the tape. So maybe that is in the past now. Maybe not. I should have mentioned it earlier. Sorry. Any other thoughts before I try to OS update and the larger block size? Jaime ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Quantum tape drive
In the last episode (Jan 28), Jaime said: > I am trying to replace an older DLT tape drive (which doesn't like to > eject tapes any more) with a new Quantum DLT-4 drive. Its connected > by internal SCSI and seems to be set up right. But after DAYS of > running a tar command, its still not done backing up 60GB. The old > drive could backup 70-80GB in about 7 hours. > > Any suggestions? > > /usr/bin/tar -cvpX /usr/local/etc/backups/skiplist-relative.txt -f > /dev/sa0 -C / . If nothing else, I suggest bumping up your blocksize. The default for tar (10k) is pretty small for modern tape drives. Try -b 128 (for a 64k block size). Another optimization would be to put a buffering program in between tar and your tape drive to decouple disk reads from tape writes. misc/team, misc/buffer, and misc/cstream in ports are good for this. -- Dan Nelson dnel...@allantgroup.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Quantum tape drive
I am trying to replace an older DLT tape drive (which doesn't like to eject tapes any more) with a new Quantum DLT-4 drive. Its connected by internal SCSI and seems to be set up right. But after DAYS of running a tar command, its still not done backing up 60GB. The old drive could backup 70-80GB in about 7 hours. I changed my backup script to include a -v flag in the tar command, and it now lists hundreds or possibly thousands of files. But it never even gets to /home before I killed the process (after 9 hours in this case). Any suggestions? If it helps, the backup script and output from camcontrol follows. However, this script is the same one that worked on the other drive. A quick test with a Knoppix disk suggested that the backups ran faster in Linux. Not positive of this, but it might be true. $ cat /etc/periodic/daily/910.backups #!/bin/sh # echo echo "Tape archives:" dow=`/bin/date +%w` if test "$dow" -gt 1; then echo " Beginning backup." /usr/bin/uptime /usr/bin/tar -cvpX /usr/local/etc/backups/skiplist-relative.txt -f /dev/sa0 -C / . /usr/bin/uptime else echo " Today is a weekend. Skipping backups." fi $ camcontrol devlist at scbus0 target 0 lun 0 (pass0) at scbus0 target 1 lun 0 (pass1) at scbus0 target 2 lun 0 (pass2) at scbus1 target 0 lun 0 (da0,pass3) at scbus2 target 4 lun 0 (sa0,pass4) Any help is greatly appreciated. Thanks in advance, Jaime ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: tape format
On Fri, Oct 24, 2008, Ansar Mohammed wrote: >Hello all > >Does anyone know if the tape format produced by Seagate backup is >documented? You might get a hint using ``file /dev/tapedevice'' which should show if it's a tar, cpio, or whatever archive. Bill -- INTERNET: [EMAIL PROTECTED] Bill Campbell; Celestial Software LLC URL: http://www.celestial.com/ PO Box 820; 6641 E. Mercer Way Voice: (206) 236-1676 Mercer Island, WA 98040-0820 Fax:(206) 232-9186 Once at a social gathering, Gladstone said to Disraeli, I predict, Sir, that you will die either by hanging or of some vile disease. Disraeli replied, "That all depends upon whether I embrace your principles or your mistress". ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
tape format
Hello all Does anyone know if the tape format produced by Seagate backup is documented? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Help! Tape drive resets the server!
On Aug 27, 2008, at 10:22 AM, Kirk Strauser wrote: Occasionally, whenever I open sa0 for reading (typically when Amanda starts flushing backups to tape), the system resets. In summary: RAM issues. Apparently I have to boost the RAM from 1.8V to 2.1V, or so says its manufacturer. Got my fingers crossed! -- Kirk Strauser ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Help! Tape drive resets the server!
On Wednesday 27 August 2008 14:53:44 Tyson Boellstorff wrote: > 3) Yes, it's possible that your drive is doing this, but more likely you > have a bent pin/short somewhere causing the scsi bus to reset, and your > kernel isn't handling this nicely. Check your pins. They bend easy, but a > mechanical pencil with no lead in it can help you with that. Interesting idea. I'll check that next time I power down. > 4) Is your termination auto or physical? Physical. > 5) Is the tape drive manually jumped for a specific ID? I assume that it is > set for 3. Try 4. Seriously? I mean, I certainly don't mind trying it and it wouldn't be any harder than pulling the cable to check the pins, but what's your line of thinking here? > 6) Try a slower transfer rate. Last night I bumped it down from 40MB/s to 20MB/s, disabled tagged queueing (which the adapter had enabled by default), and moved it to a different power lead. So far so good, but 24 hours does not my confidence earn. Thanks for the tips! If it's still acting wonky, I'll work through them. -- Kirk Strauser ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Help! Tape drive resets the server!
On Wednesday 27 August 2008 10:22:52 Kirk Strauser wrote: > I have a Seagate DDS-4 tape drive: > > sa0 at sym0 bus 0 target 3 lun 0 > sa0: Removable Sequential Access SCSI-3 > device sa0: 40.000MB/s transfers (20.000MHz, offset 16, 16bit) > > It's attached to a Tekram DC390F SCSI card: > > Is it possible that the drive itself is triggering the reset? I'd find > that a little unlikely, but am certainly not an expert on the matter. > Alternatively, has anyone had that sort of problem with drives attached to > that card? 1) try a different scsi cable. 2) Are you using adapters? Get the right cable. One new, known good cable, no adapters. 3) Yes, it's possible that your drive is doing this, but more likely you have a bent pin/short somewhere causing the scsi bus to reset, and your kernel isn't handling this nicely. Check your pins. They bend easy, but a mechanical pencil with no lead in it can help you with that. 4) Is your termination auto or physical? 5) Is the tape drive manually jumped for a specific ID? I assume that it is set for 3. Try 4. 6) Try a slower transfer rate. Can you dump the SCSI sense codes that are being seen on the SCSI bus? That will most likely tell you whats going on right there. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Help! Tape drive resets the server!
On Wednesday 27 August 2008 12:16:33 Chuck Swiger wrote: > That type of behavior might indicate a problem with the power supply; > if you've replaced that already, I'm not sure what else to say other > than to be be sure you've got a decent model which is adequately > spec'ed out for the number of drives in your system... It's actually a fairly new Antec PSU rated at 450W (? 500W? Somewhere in there) without too many components on it. Thanks for the suggestion, though. I might try some of the other power leads on that PSU. Maybe I picked one with an intermittent short or something. -- Kirk Strauser ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Help! Tape drive resets the server!
Hi-- On Aug 27, 2008, at 8:22 AM, Kirk Strauser wrote: Occasionally, whenever I open sa0 for reading (typically when Amanda starts flushing backups to tape), the system resets. I don't mean that the kernel panics or anything; I mean that within a second or two I'm looking at a POST screen. I'd been having this problem for a while, but recently upgraded literally every other piece of hardware on the system. The card and drive were the *only* components carried over to the new system, and I even swapped out the card for a duplicate I had stored away. That type of behavior might indicate a problem with the power supply; if you've replaced that already, I'm not sure what else to say other than to be be sure you've got a decent model which is adequately spec'ed out for the number of drives in your system... -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Help! Tape drive resets the server!
I have a Seagate DDS-4 tape drive: sa0 at sym0 bus 0 target 3 lun 0 sa0: Removable Sequential Access SCSI-3 device sa0: 40.000MB/s transfers (20.000MHz, offset 16, 16bit) It's attached to a Tekram DC390F SCSI card: sym0: <875> port 0xc000-0xc0ff mem 0xe9004000-0xe90040ff,0xe9006000-0xe9006fff irq 20 at device 0.0 on pci7 sym0: Tekram NVRAM, ID 7, Fast-20, SE, parity checking sym0: [ITHREAD] Occasionally, whenever I open sa0 for reading (typically when Amanda starts flushing backups to tape), the system resets. I don't mean that the kernel panics or anything; I mean that within a second or two I'm looking at a POST screen. I'd been having this problem for a while, but recently upgraded literally every other piece of hardware on the system. The card and drive were the *only* components carried over to the new system, and I even swapped out the card for a duplicate I had stored away. Is it possible that the drive itself is triggering the reset? I'd find that a little unlikely, but am certainly not an expert on the matter. Alternatively, has anyone had that sort of problem with drives attached to that card? -- Kirk Strauser ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Adapter to hook SCSI tape drive to SATA?
I have a Seagate DDS-4 tape drive hanging off a Tekram SCSI card. I was starting to get random hard resets whenever accessing the drive - as in "dd if=/dev/zero of=/dev/sa0" would get me to the BIOS POST screen in under a second - so this morning I swapped out an unused card of the same model from another system. Hopefully this was just a hardware glitch and the "new" card (which is also 9 years old) will be OK. This got me thinking, though: has anyone used any of the SCSI-to-SATA adapters to hook a tape drive to their FreeBSD system? More importantly, did it work? I'd just as soon use one of the on-board SATA connectors as an aging boat anchor of a SCSI card if I could get away with it. I mean, I still use SCSI a lot elsewhere, but I'd like to ditch it in this one specific application if possible. Thanks! -- Kirk Strauser ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: tape device not configured
Papp Tamas wrote: mt -f /dev/sa0 I mean mt -f /dev/sa0 status But actually I recogniozed, it was a cleaning tape. I'm sorry:) Thank you, tamas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: tape device not configured
Anders Trobäck wrote: On Mon, 07 Jul 2008 23:21:15 +0200 Papp Tamas <[EMAIL PROTECTED]> wrote: hi All, I have a new Exabyte VXA-320, I show it in dmesg as sa0. When I try to access it for example by mt, it says, "Device not configured", and of cource is not working. sa0 at ahd0 bus 0 target 2 lun 0 sa0: Removable Sequential Access SCSI-3 device sa0: 160.000MB/s transfers (80.000MHz DT, offset 126, 16bit) What do I miss? Thank you very much, tamas What is the exact command you are using? mt -f /dev/sa0 Thanks, tamas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: tape device not configured
On Mon, 07 Jul 2008 23:21:15 +0200 Papp Tamas <[EMAIL PROTECTED]> wrote: > hi All, > > I have a new Exabyte VXA-320, I show it in dmesg as sa0. > When I try to access it for example by mt, it says, "Device not > configured", and of cource is not working. > > sa0 at ahd0 bus 0 target 2 lun 0 > sa0: Removable Sequential Access SCSI-3 device > sa0: 160.000MB/s transfers (80.000MHz DT, offset 126, 16bit) > > > What do I miss? > > Thank you very much, > > tamas What is the exact command you are using? -- Windows: "Where do you want to go today?" Linux: "Where do you want to go tomorrow?" FreeBSD: "Are you guys coming, or what?" Anders Trobäck http://www.troback.com/ - ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
tape device not configured
hi All, I have a new Exabyte VXA-320, I show it in dmesg as sa0. When I try to access it for example by mt, it says, "Device not configured", and of cource is not working. sa0 at ahd0 bus 0 target 2 lun 0 sa0: Removable Sequential Access SCSI-3 device sa0: 160.000MB/s transfers (80.000MHz DT, offset 126, 16bit) What do I miss? Thank you very much, tamas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Replacing tape changer with USB disk drives.
I just looked at one of the most popular online shops around here. They have about 50 different USB enclosures; prices start at 10 EUR. But they have only six Firewire enclosures (and none of them is 2.5"!), the cheapest one is 34 EUR. i think this 24 EUR it's worth of. However, they do have a larger number of eSATA enclosures, SATA works fine too. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Replacing tape changer with USB disk drives.
On Jun 17, 2008, at 11:40 AM, Oliver Fromme wrote: Wojciech Puchar <[EMAIL PROTECTED]> wrote: you must have something wrong. my USB drive gets 27MB/s. yes this 480Mbit/s is USB isn't real, but half of it is. I agree. Want to take this private and help figure out what's wrong? :-) i simply have no idea why it could work so slow. Cheap controller in the USB enclosure. I've used quite a few USB enclosures in the past years, and there are significant performance differences. As a rule of thumb, the cheaper the box, the slower it is. Of course there are exceptions to that rule. By the way, for backup purposes I use a hot-swappable IDE drive frame. The one I use is PATA (UDMA-133), but there are also ones for SATA. It's much faster than USB and more reliable. You can use atacontrol(8) to attach and detach the drive while the system is running. (For that to work reliably, the frame must be the only device on its channel, i.e. no slave, in the PATA case.) Best regards Oliver I get good speeds from USB but they are bursty. I have a pair of identical controllers and both are USB/Firewire. Both have different brands and sizes of disk drive. Could the drive be part of the problem? One is connected via Firewire and doesn't have the bursty speed issue. I've only got it with USB. The poster who mentioned that I'm only looking for a backup against catastrophic disk failure is spot on. Offsite backup is something I'll work out down the road. Chris Hilton e: chris|at|vindaloo| dot|com "The pattern juggler lifts his hand; The orchestra begin. As slowly turns the grinding wheel in the court of the crimson king." -- Ian McDonald / Peter Sinfield ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
