Hi, 18.09.2007 23:07,, Erik P. Olsen wrote:: > When mounting a tape I often - but not always - see the following strange > sequence of events: > > #mount DDS-4 > Using default Catalog name=MyCatalog DB=bacula > 3905 Device "DDS-4" (/dev/nst0) open but no Bacula volume is mounted. > If this is not a blank tape, try unmounting and remounting the Volume. > #unmount DDS-4 > 3002 Device "DDS-4" (/dev/nst0) unmounted. > #mount DDS-43001 Mounted Volume: EPOL001 > 3001 Device "DDS-4" (/dev/nst0) is mounted with Volume "EPOL001" > ## > > There was no tape mounted at the first mount request since it has previously > been unmounted (and ejected) by the proper bacula unmount command. Is this a > bug > or are there instances in which bacula can't read the volume label?
Definitely... most of the time they are based on hardware related problems, like a tape drive needing very long to accept a tape. DDS is, in my experience, prone to these errors. With DDS taes, I often encountered problems where a tape could not be read, but after ejecting and reloading it, everything was fine. Arno -- Arno Lehmann IT-Service Lehmann www.its-lehmann.de ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users