Re: tape record bigger than supplied buffer
Damian Sobieralski wrote: I added the following to my tape drive area in the bacula-sd-conf: Minimum Block Size = 64512 Maximum Block Size = 64512 I'm not seeing those errors any longer. I've restored and all seems to go well. Good stuff! Did that number come out of your tape drive manual, in the end? Just wondering why 64512 rather than 65536... --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: tape record bigger than supplied buffer
Alex Zbyslaw wrote: Damian Sobieralski wrote: I added the following to my tape drive area in the bacula-sd-conf: Minimum Block Size = 64512 Maximum Block Size = 64512 I'm not seeing those errors any longer. I've restored and all seems to go well. Good stuff! Did that number come out of your tape drive manual, in the end? Just wondering why 64512 rather than 65536... It's 63K. I've seen recommendations elsewhere to use a tape blocksize of 63K rather than 64K if hardware compression is enabled, because sometimes the data doesn't have a positive compression ratio... -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: tape record bigger than supplied buffer
Chuck Swiger wrote: Alex Zbyslaw wrote: Damian Sobieralski wrote: I added the following to my tape drive area in the bacula-sd-conf: Minimum Block Size = 64512 Maximum Block Size = 64512 I'm not seeing those errors any longer. I've restored and all seems to go well. Good stuff! Did that number come out of your tape drive manual, in the end? Just wondering why 64512 rather than 65536... It's 63K. I've seen recommendations elsewhere to use a tape blocksize of 63K rather than 64K if hardware compression is enabled, because sometimes the data doesn't have a positive compression ratio... Thanks for the tip! That trailing 512 should have been a giveaway... --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: tape record bigger than supplied buffer
FYI: I added the following to my tape drive area in the bacula-sd-conf: Minimum Block Size = 64512 Maximum Block Size = 64512 I'm not seeing those errors any longer. I've restored and all seems to go well. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: tape record bigger than supplied buffer
Damian Sobieralski wrote: 2) See if you can't find some option to match the bacula record size to that of your tape drive. Dump, for example, has a -b option e.g. -b 64 to set its record size. I'm puzzled by you only seeing three messages though. Why would three buffers be smaller and not the rest? That's a good question that I don't know the answer to. I thank you for the response. I'll see if I can get a bit more information by restoring the data for us to work with. When you say match the record size to my tape drive's, is this something that should be listed in my tape drives literature? Well, I'm guessing yes, but only based on that error message. I know older tape drives had fixed record sizes, and maybe some kinds of new ones do too. My DAT drive does variable sized records, because it has native compression, but yours may not. You could also try mt -f /dev/sa0 and see what it says. I can't remember off had if it shows anything useful but it only takes seconds. (I'd check, but I'm in the middle of upgrading hardware/software and the tape drive isn't connected up yet). You could also try man 4 sa which talks about fixed and variable block sizes. (As far as I know, there is a limit of 64k for the record size, but this was info from the 4.X series, so I reserve the right to be wrong :-) --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
tape record bigger than supplied buffer
I realize that I posted this earlier this weekend but with the American holiday weekend, I am worried some people didn't see it. I really could use any opinion on this as tape backups are really new to me. I'm test piloting bacula on a FreeBSD 5.4-REL system. All seemed to work well in monitored tests. So last night I set up a job to run at night. When I came in this morning, all seemed to go well...the backup happened but I noticed 3 messages on the console: (sa0:ahc0:0:6:0): 65536-byte tape record bigger than supplied buffer (sa0:ahc0:0:6:0): 65536-byte tape record bigger than supplied buffer (sa0:ahc0:0:6:0): 65536-byte tape record bigger than supplied buffer The backup seemed to go okay as I restored several files off of that tape with no problems. Realizing the console messages mean what it does at face value, was any data lost(should i take this as a warning or as an error) ? Thnak you for any experience that you can share with me on tape backups. - Damian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: tape record bigger than supplied buffer
Damian Sobieralski wrote: I'm test piloting bacula on a FreeBSD 5.4-REL system. All seemed to work well in monitored tests. So last night I set up a job to run at night. When I came in this morning, all seemed to go well...the backup happened but I noticed 3 messages on the console: (sa0:ahc0:0:6:0): 65536-byte tape record bigger than supplied buffer (sa0:ahc0:0:6:0): 65536-byte tape record bigger than supplied buffer (sa0:ahc0:0:6:0): 65536-byte tape record bigger than supplied buffer The backup seemed to go okay as I restored several files off of that tape with no problems. Realizing the console messages mean what it does at face value, was any data lost(should i take this as a warning or as an error) ? I've never used bacula, but no one else is jumping in... 1) Try restoring the whole tape to either an empty partition, or if you don't have one of those, to /dev/null. /dev/null isn't conclusive proof, but I assume that if data weas dropped then there *should* be a failed checksum somewhere along the line. 2) See if you can't find some option to match the bacula record size to that of your tape drive. Dump, for example, has a -b option e.g. -b 64 to set its record size. I'm puzzled by you only seeing three messages though. Why would three buffers be smaller and not the rest? --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: tape record bigger than supplied buffer
1) Try restoring the whole tape to either an empty partition, or if you don't have one of those, to /dev/null. /dev/null isn't conclusive proof, but I assume that if data weas dropped then there *should* be a failed checksum somewhere along the line. I'll do that tomorrow (restore the whole thing). 2) See if you can't find some option to match the bacula record size to that of your tape drive. Dump, for example, has a -b option e.g. -b 64 to set its record size. I'm puzzled by you only seeing three messages though. Why would three buffers be smaller and not the rest? That's a good question that I don't know the answer to. I thank you for the response. I'll see if I can get a bit more information by restoring the data for us to work with. When you say match the record size to my tape drive's, is this something that should be listed in my tape drives literature? - Damian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
tape record bigger than supplied buffer
I'm test piloting bacula on a FreeBSD 5.4-REL system. All seemed to work well in monitored tests. So last night I set up a job to run at night. When I came in this morning, all seemed to go well...the backup happened but I noticed 3 messages on the console: (sa0:ahc0:0:6:0): 65536-byte tape record bigger than supplied buffer (sa0:ahc0:0:6:0): 65536-byte tape record bigger than supplied buffer (sa0:ahc0:0:6:0): 65536-byte tape record bigger than supplied buffer Realizing this means what it does at face value, was any data lost (should i take this as a warning or as an error) ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
