Hi, thanks a lot for this post. We had exactly the same problem today and were able to solve it with "mt -f /dev/nst0 defblksize 0" too.
Interestingly, writing to tape worked for a few days after upgrading to Bareos 23 (including kernel updates and server restart). But this weekend we had a planned power outage and had to power down the entire infrastructure including the tape library. After bringing everything up again, the drive was not accessible - just as you described. Our hardware seems to be nearly identical to yours: LSI SAS2008 Fusion SAS-Controller (Perc H200), Quantum Ultrium 5 SAS drive in a Quantum Superloader 3. We are using Ubuntu 22.04 though. The next time I'm in the office, I will test whether this command will permanently resolve the problem or whether it will reappear after restarting the tape library. Cheers, Markus Alexandre Denault schrieb am Donnerstag, 18. Juli 2024 um 03:27:01 UTC+2: > Hi, > > Ii it possible that OS was always defaulting to 512 and Bareos before 23.0 > was just ignoring the setting. I have a hard time explaining what happened, > other than "mt -f /dev/nst0 defblksize 0" fixed the problem. > > I check my Bareos configuration for the last 2 years ( I keep it versioned > in git ) and I've never set a default block size, so I know I didn't change > anything in Bareos. > > I'm running Debian Bullseye (11). > > My SAS controller is a Broadcom / LSI SAS2008 PCI-Express Fusion-MPT > SAS-2, most likely a Dell Perc H200 controller that I flashed to IT mode. > > The tape drive is a Quantum Ultrium 5 SAS Internal Half Height. > > Hopefully this helps, > > Alex > > > > On Tuesday, July 16, 2024 at 4:06:57 AM UTC-4 Andreas Rogge wrote: > >> Am 15.07.24 um 20:56 schrieb Alan Brown: >> > >> > _ALL_ LTO drives (even LTO-1) can handle block sizes of at least 1MB >> and >> > you would need to be running a pretty awful (5-10MB/s) scsi adaptor for >> > a restriction there >> >> You wish! >> >> After changing the default block size to 1 MB we have seen more than one >> large enterprise setup that could not handle 1 MB blocks. >> The drives were fine, the controllers were fine, but some intermediate >> component (*cough* FC director *cough*) didn't allow the large SCSI >> frames to pass. >> >> Also, there are people attaching their drives to the external >> SAS-interface of (rather cheap) RAID controllers. Some of these don't >> allow block sizes of 1 MB either. >> >> Best Regards, >> Andreas >> >> -- >> Andreas Rogge [email protected] >> Bareos GmbH & Co. KG Phone: +49 221-630693-86 <+49%20221%2063069386> >> http://www.bareos.com >> >> Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646 >> Komplementär: Bareos Verwaltungs-GmbH >> Geschäftsführer: Stephan Dühr, Jörg Steffens, Philipp Storz >> > -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/db9deaef-ef6b-467f-9d7a-628166c2db4an%40googlegroups.com.
