From: Kern S. <ke...@si...> - 2008-08-30 16:59:02
|
Hello, Unfortunately there were a good number of problems in 2.4.0 and 2.4.1 due to the redesign of some critical parts of the SD having to do with loading and tracking volumes. On Saturday 30 August 2008 17:19:44 Shad L. Lords wrote: > Shad L. Lords wrote: > > Here is the relevant part of status storage from bconsole: > > > > Device status: > > Autochanger "SL-10K" with devices: > > "SL-10K-Drive1" (/dev/nst0) > > "SL-10K-Drive2" (/dev/nst1) > > Device "SL-10K-Drive1" (/dev/nst0) is not open. > > Drive 0 is not loaded. > > Device "SL-10K-Drive2" (/dev/nst1) is not open. > > Drive 1 is not loaded. > > ==== > > > > In Use Volume status: > > MA3004 on device "SL-10K-Drive2" (/dev/nst1) > > Reader=0 writers=0 devres=0 volinuse=0 > > WA3003 on device "SL-10K-Drive2" (/dev/nst1) > > Reader=0 writers=0 devres=0 volinuse=0 > > It appears this issue still exists in 2.4.2. Your subject mentions 2.4.1 and here you mention 2.4.2. If you are running 2.4.1, please upgrade to 2.4.2, where there have been no reports of such problems. There may still be problems on 2.4.2, but for the moment they all seem to be fixed. If you are actually running on 2.4.2, please let me know and we can discuss it further. Regards, Kern > I've just run into a > situation similar. Before it just used to mark the tape as in use but > the backup would complete. This time however it blocked the backup. > Here is the output I've currently got: > > Device status: > Autochanger "Scalar-100" with devices: > "Scalar-100-Drive1" (/dev/nst0) > "Scalar-100-Drive2" (/dev/nst1) > "Scalar-100-Drive3" (/dev/nst2) > "Scalar-100-Drive4" (/dev/nst3) > Device "Scalar-100-Drive1" (/dev/nst0) is mounted with: > Volume: DA2019 > Pool: Daily > Media type: AIT-2 > Slot 59 is loaded in drive 0. > Total Bytes=22,594,424,832 Blocks=350,235 Bytes/block=64,512 > Positioned at File=24 Block=0 > Device "Scalar-100-Drive2" (/dev/nst1) is not open. > Drive 1 is not loaded. > Device "Scalar-100-Drive3" (/dev/nst2) is mounted with: > Volume: DA3007 > Pool: Daily > Media type: AIT-3 > Device is BLOCKED waiting for mount of volume "DA3007", > Pool: Daily > Media type: AIT-3 > Slot 8 is loaded in drive 2. > Total Bytes Read=0 Blocks Read=0 Bytes/block=0 > Positioned at File=0 Block=0 > Device "Scalar-100-Drive4" (/dev/nst3) is not open. > Device is BLOCKED waiting for mount of volume "DA3008", > Pool: Daily > Media type: AIT-3 > Drive 3 status unknown. > ==== > > Used Volume status: > DA2019 on device "Scalar-100-Drive1" (/dev/nst0) > Reader=0 writers=0 devres=0 volinuse=0 > DA3007 on device "Scalar-100-Drive4" (/dev/nst3) > Reader=0 writers=0 devres=1 volinuse=1 > DA3008 on device "Scalar-100-Drive4" (/dev/nst3) > Reader=0 writers=0 devres=1 volinuse=1 > ==== > > The interesting thing is that DA3008 is in slot 8. Drive3 (nst2) says > DA3007 is in the drive but it is blocking waiting for that same tape. > It also mentions that slot 8 is loaded but that is wrong. Slot 7 is > loaded. I've visually verified that DA3007 is in drive 3. I'm still > trying to get a debugging log for you. > > -Shad > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge Build the coolest Linux based applications with Moblin SDK & win > great prizes Grand prize is a trip for two to an Open Source event anywhere > in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Bacula-devel mailing list > Bac...@li... > https://lists.sourceforge.net/lists/listinfo/bacula-devel |