Hello, It would help if you would re-state the specifics of your problems. I get hundreds of emails every day, so these things don't remain on my radar screen very long.
I assume you have already ensure that the FC is not caching SCSI data or status codes, which would be fatal to Bacula. I also assume that you have worked your way through the (9 if I remember right) steps in the Tape testing chapter of the manual. On Monday 08 October 2007 14:52, Mariusz Czulada wrote: > Hi all, > > Unfortunately I didn't get any help from my local support regarding my > problem. In fact the answer was IMHO quite arrogant, like "System must > work correctly. We don't know/care about bacula. Use tar instead or by > Legato". So it seems I have to fight it alone... > > As a remainder, my configuration: > > Hardware configuration: > * xSeries 3690, CentOS 4 (like RH ES4) > * Two DS4000 FC 4 Gb PCI-X Single Port HBA; in system identified as > QLogic QLA2460 - PCI-X 2.0 to 4Gb FC, Single Channel > * TS3310 library, with two ULT3580-TD3 drives, connected directly to HBAs. > > Drivers: > * drivers for qlaxxxx - v8.01.06 > * SANsurfer FC HBA Manager High Availability Edition v2.0.30 Build 81 > * IBMTape soft v. 3.0.5 > > Firmware: > * QLA2460: > BIOS Version 1.12, Firmware Version: 4.00.23 > * TS3310: > Name library > IBM Serial Number 1307494 > 3576-MTL Firmware Version 320G.GS006 > BSP Level BSP6.6 > Last Update 9/29/2006 1:18 > * ULT3580-TD3 drives: > Firmware Level: 69U2 > > Bacula: > * 2.2.4, configured with "--prefix=/opt/bacula > --with-postgresql=/opt/pgsql-8.1/ --with-openssl" > > Probably noone else is using such or similar configuration so will have > to do myself some debugging to search for the reason. I'd like to ask > you to help me: > > * how to place timestamp in SD log file? It is quite detailed, but > almost impossible to correlate with IBMtaped trace file. I never need a time stamp for debug output -- the normal job output has a time stamp. However, it is rather easy to add to the code. > > * how to increase debug level in specific code? Most (all?) of my > problems appear in stored/dev.c/DEVICE::fsf method. It would be nice to > set detailed debugging only in this function instead of generating > megabytes of unneeded messages. Generally, you can simply set the particular error levels in the file you want to some much smaller value and rebuilt. I've begun adding a: const int dbglvl = 100; in many files, so that you simply adjust it in one place. It *is* a bit crude, but we don't generally need much debug output. Regards, Kern > > TIA, > > Mariusz Czulada > > ---------------------------------------------------- > Wybierz najlepsze gry roku! Wygraj konsolę NINTENDO Wii! > Imperatory7: http://klik.wp.pl/?adr=http%3A%2F%2Fimperatory.wp.pl&sid=52 > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Bacula-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/bacula-devel ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
