On Tue, Jan 31, 2012 at 1:41 PM, Rao, Uthra R. (GSFC-672.0)[ADNET SYSTEMS INC] <uthra.r....@nasa.gov> wrote: > This is what I have done so far: > > Added the Minimum Block Size = 262144/Maximum Block Size = 262144 in the > Bacula-sd.conf > > Erased the tape in the tape drive which was in the Append status and > re-labeled it. > > Now if I run tapeinfo: > > # tapeinfo -f /dev/sg0 > Product Type: Tape Drive > Vendor ID: 'IBM ' > Product ID: 'ULT3580-TD5 ' > Revision: 'B5BF' > Attached Changer API: No > SerialNumber: '1068007095' > MinBlock: 1 > MaxBlock: 16777215 > SCSI ID: 0 > SCSI LUN: 0 > Ready: yes > BufferedMode: yes > Medium Type: 0x58 > Density Code: 0x58 > BlockSize: 0 > DataCompEnabled: yes > DataCompCapable: yes > DataDeCompEnabled: yes > CompType: 0x1 > DeCompType: 0x1 > Block Position: 2 > Partition 0 Remaining Kbytes: -1 > Partition 0 Size in Kbytes: -1 > ActivePartition: 0 > EarlyWarningSize: 0 > NumPartitions: 0 > MaxPartitions: 1 > > I don't know why the min/max block size still remains the same and has not > changed to the new value? >
This means you are running in variable block mode. I think that is fine. I believe when I created my tapes they were in fixed block size. Hmm was there a change in the handling that I do not know of? I will try to check my tapes later today. I am working on 3 different medical imaging programming projects today so I can not look now. John ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
