Re: Continuing after "No acceptable volumes found"

2017-11-08 Thread Greg Dickie
It's 42Meg. I don't see any sign of it looking at slot 14 before​
 taper.20171104210102.debug

​
Greg

On Wed, Nov 8, 2017 at 1:18 PM, Jean-Louis Martineau <
[email protected]> wrote:

> I would like to understand why it didn't use slot 14.
> Can you send me the complete taper debug file?
> I would like to see what it did the first time it read the slot 14.
>
> Jean-Louis
>
>
> On 08/11/17 12:51 PM, Greg Dickie wrote:
>
> Good call, that worked!
>
> Wed Nov 08 12:12:02.180979631 2017: pid 23508: thd-0x18fd200: taper:
> Device is in variable block size
> Wed Nov 08 12:12:04.573098503 2017: pid 23508: thd-0x18fd200: taper: Slot
> 14 with label 000114L7 is usable
> Wed Nov 08 12:12:04.591316642 2017: pid 23508: thd-0x18fd200: taper:
> Building type TAPESTART header of 2097152-2097152 bytes with
> name='000114L7' disk='' dumplevel=0 and blocksize=2097152
>
> Rolling again,
>
> Thank you very much for the help,
> Greg
>
>
> On Wed, Nov 8, 2017 at 11:57 AM, Jean-Louis Martineau <
> [email protected]> wrote:
>
>> I do not understand why it doesn't want to use the tapes.
>>
>> Can you try the following: (If you agree amanda can overwrite 000114L7
>> amrmtape WeeklySet1 --keep-label 000114L7
>> amatpe WeeklySet1 update 14=
>>
>> After the update, the taper should load the slot, you should see it in
>> the taper debug file.
>>
>> Jean-Louis
>>
>>
>> On 08/11/17 11:45 AM, Greg Dickie wrote:
>>
>> Wed Nov 08 11:43:15.492889388 2017: pid 23508: thd-0x18fd200: taper:
>> invoking /usr/sbin/mtx -f /dev/sg1 status
>> Wed Nov 08 11:43:16.026704763 2017: pid 23508: thd-0x18fd200: taper:
>> mtx:   Storage Changer /dev/sg1:1 Drives, 24 Slots ( 0 Import/Export )
>> Wed Nov 08 11:43:16.026751421 2017: pid 23508: thd-0x18fd200: taper: mtx:
>> Data Transfer Element 0:Full (Storage Element 21 Loaded):VolumeTag =
>> 000121L7
>> Wed Nov 08 11:43:16.026780475 2017: pid 23508: thd-0x18fd200: taper:
>> mtx:   Storage Element 1:Empty
>> Wed Nov 08 11:43:16.026799697 2017: pid 23508: thd-0x18fd200: taper:
>> mtx:   Storage Element 2:Empty
>> Wed Nov 08 11:43:16.026809868 2017: pid 23508: thd-0x18fd200: taper:
>> mtx:   Storage Element 3:Empty
>> Wed Nov 08 11:43:16.026818338 2017: pid 23508: thd-0x18fd200: taper:
>> mtx:   Storage Element 4:Empty
>> Wed Nov 08 11:43:16.026825880 2017: pid 23508: thd-0x18fd200: taper:
>> mtx:   Storage Element 5:Empty
>> Wed Nov 08 11:43:16.026833781 2017: pid 23508: thd-0x18fd200: taper:
>> mtx:   Storage Element 6:Empty
>> Wed Nov 08 11:43:16.026841346 2017: pid 23508: thd-0x18fd200: taper:
>> mtx:   Storage Element 7:Empty
>> Wed Nov 08 11:43:16.026848729 2017: pid 23508: thd-0x18fd200: taper:
>> mtx:   Storage Element 8:Empty
>> Wed Nov 08 11:43:16.026857121 2017: pid 23508: thd-0x18fd200: taper:
>> mtx:   Storage Element 9:Empty
>> Wed Nov 08 11:43:16.026866301 2017: pid 23508: thd-0x18fd200: taper:
>> mtx:   Storage Element 10:Full :VolumeTag=000110L7
>> Wed Nov 08 11:43:16.026896922 2017: pid 23508: thd-0x18fd200: taper:
>> mtx:   Storage Element 11:Full :VolumeTag=000111L7
>> Wed Nov 08 11:43:16.026908845 2017: pid 23508: thd-0x18fd200: taper:
>> mtx:   Storage Element 12:Full :VolumeTag=000112L7
>> Wed Nov 08 11:43:16.026919029 2017: pid 23508: thd-0x18fd200: taper:
>> mtx:   Storage Element 13:Full :VolumeTag=000113L7
>> Wed Nov 08 11:43:16.026928701 2017: pid 23508: thd-0x18fd200: taper:
>> mtx:   Storage Element 14:Full :VolumeTag=000114L7
>> Wed Nov 08 11:43:16.026939958 2017: pid 23508: thd-0x18fd200: taper:
>> mtx:   Storage Element 15:Full :VolumeTag=000115L7
>> Wed Nov 08 11:43:16.026949743 2017: pid 23508: thd-0x18fd200: taper:
>> mtx:   Storage Element 16:Full :VolumeTag=000116L7
>> Wed Nov 08 11:43:16.026961396 2017: pid 23508: thd-0x18fd200: taper:
>> mtx:   Storage Element 17:Full :VolumeTag=000117L7
>> Wed Nov 08 11:43:16.026971300 2017: pid 23508: thd-0x18fd200: taper:
>> mtx:   Storage Element 18:Full :VolumeTag=000118L7
>> Wed Nov 08 11:43:16.026983376 2017: pid 23508: thd-0x18fd200: taper:
>> mtx:   Storage Element 19:Full :VolumeTag=000119L7
>> Wed Nov 08 11:43:16.026993560 2017: pid 23508: thd-0x18fd200: taper:
>> mtx:   Storage Element 20:Full :VolumeTag=000120L7
>> Wed Nov 08 11:43:16.027002906 2017: pid 23508: thd-0x18fd200: taper:
>> mtx:   Storage Element 21:Empty
>> Wed Nov 08 11:43:16.027010865 2017: pid 23508: thd-0x18fd200: taper:
>> mtx:   Storage Element 22:Empty
>> Wed Nov 08 11:43:16.027019542 2017: pid 23508: thd-0x18fd200: taper:
>> mtx:   Storage Element 23:Empty
>> Wed Nov 08 11:43:16.027026856 2017: pid 23508: thd-0x18fd200: taper:
>> mtx:   Storage Element 24:Empty
>> Wed Nov 08 11:43:16.027077019 2017: pid 23508: thd-0x18fd200: taper:
>> flexstorii: updating state
>> Wed Nov 08 11:43:16.029230821 2017: pid 23508: thd-0x18fd200: taper: new
>> Amanda

Re: Continuing after "No acceptable volumes found"

2017-11-08 Thread Jean-Louis Martineau

I would like to understand why it didn't use slot 14.
Can you send me the complete taper debug file?
I would like to see what it did the first time it read the slot 14.

Jean-Louis

On 08/11/17 12:51 PM, Greg Dickie wrote:

Good call, that worked!

Wed Nov 08 12:12:02.180979631 2017: pid 23508: thd-0x18fd200: taper: 
Device is in variable block size
Wed Nov 08 12:12:04.573098503 2017: pid 23508: thd-0x18fd200: taper: 
Slot 14 with label 000114L7 is usable
Wed Nov 08 12:12:04.591316642 2017: pid 23508: thd-0x18fd200: taper: 
Building type TAPESTART header of 2097152-2097152 bytes with 
name='000114L7' disk='' dumplevel=0 and blocksize=2097152


Rolling again,

Thank you very much for the help,
Greg


On Wed, Nov 8, 2017 at 11:57 AM, Jean-Louis Martineau 
mailto:[email protected]>> wrote:


I do not understand why it doesn't want to use the tapes.

Can you try the following: (If you agree amanda can overwrite 000114L7
amrmtape WeeklySet1 --keep-label 000114L7
amatpe WeeklySet1 update 14=

After the update, the taper should load the slot, you should see
it in the taper debug file.

Jean-Louis


On 08/11/17 11:45 AM, Greg Dickie wrote:

Wed Nov 08 11:43:15.492889388 2017: pid 23508: thd-0x18fd200:
taper: invoking /usr/sbin/mtx -f /dev/sg1 status
Wed Nov 08 11:43:16.026704763 2017: pid 23508: thd-0x18fd200:
taper: mtx:   Storage Changer /dev/sg1:1 Drives, 24 Slots ( 0
Import/Export )
Wed Nov 08 11:43:16.026751421 2017: pid 23508: thd-0x18fd200:
taper: mtx: Data Transfer Element 0:Full (Storage Element 21
Loaded):VolumeTag = 000121L7
Wed Nov 08 11:43:16.026780475 2017: pid 23508: thd-0x18fd200:
taper: mtx:   Storage Element 1:Empty
Wed Nov 08 11:43:16.026799697 2017: pid 23508: thd-0x18fd200:
taper: mtx:   Storage Element 2:Empty
Wed Nov 08 11:43:16.026809868 2017: pid 23508: thd-0x18fd200:
taper: mtx:   Storage Element 3:Empty
Wed Nov 08 11:43:16.026818338 2017: pid 23508: thd-0x18fd200:
taper: mtx:   Storage Element 4:Empty
Wed Nov 08 11:43:16.026825880 2017: pid 23508: thd-0x18fd200:
taper: mtx:   Storage Element 5:Empty
Wed Nov 08 11:43:16.026833781 2017: pid 23508: thd-0x18fd200:
taper: mtx:   Storage Element 6:Empty
Wed Nov 08 11:43:16.026841346 2017: pid 23508: thd-0x18fd200:
taper: mtx:   Storage Element 7:Empty
Wed Nov 08 11:43:16.026848729 2017: pid 23508: thd-0x18fd200:
taper: mtx:   Storage Element 8:Empty
Wed Nov 08 11:43:16.026857121 2017: pid 23508: thd-0x18fd200:
taper: mtx:   Storage Element 9:Empty
Wed Nov 08 11:43:16.026866301 2017: pid 23508: thd-0x18fd200:
taper: mtx:   Storage Element 10:Full :VolumeTag=000110L7
Wed Nov 08 11:43:16.026896922 2017: pid 23508: thd-0x18fd200:
taper: mtx:   Storage Element 11:Full :VolumeTag=000111L7
Wed Nov 08 11:43:16.026908845 2017: pid 23508: thd-0x18fd200:
taper: mtx:   Storage Element 12:Full :VolumeTag=000112L7
Wed Nov 08 11:43:16.026919029 2017: pid 23508: thd-0x18fd200:
taper: mtx:   Storage Element 13:Full :VolumeTag=000113L7
Wed Nov 08 11:43:16.026928701 2017: pid 23508: thd-0x18fd200:
taper: mtx:   Storage Element 14:Full :VolumeTag=000114L7
Wed Nov 08 11:43:16.026939958 2017: pid 23508: thd-0x18fd200:
taper: mtx:   Storage Element 15:Full :VolumeTag=000115L7
Wed Nov 08 11:43:16.026949743 2017: pid 23508: thd-0x18fd200:
taper: mtx:   Storage Element 16:Full :VolumeTag=000116L7
Wed Nov 08 11:43:16.026961396 2017: pid 23508: thd-0x18fd200:
taper: mtx:   Storage Element 17:Full :VolumeTag=000117L7
Wed Nov 08 11:43:16.026971300 2017: pid 23508: thd-0x18fd200:
taper: mtx:   Storage Element 18:Full :VolumeTag=000118L7
Wed Nov 08 11:43:16.026983376 2017: pid 23508: thd-0x18fd200:
taper: mtx:   Storage Element 19:Full :VolumeTag=000119L7
Wed Nov 08 11:43:16.026993560 2017: pid 23508: thd-0x18fd200:
taper: mtx:   Storage Element 20:Full :VolumeTag=000120L7
Wed Nov 08 11:43:16.027002906 2017: pid 23508: thd-0x18fd200:
taper: mtx:   Storage Element 21:Empty
Wed Nov 08 11:43:16.027010865 2017: pid 23508: thd-0x18fd200:
taper: mtx:   Storage Element 22:Empty
Wed Nov 08 11:43:16.027019542 2017: pid 23508: thd-0x18fd200:
taper: mtx:   Storage Element 23:Empty
Wed Nov 08 11:43:16.027026856 2017: pid 23508: thd-0x18fd200:
taper: mtx:   Storage Element 24:Empty
Wed Nov 08 11:43:16.027077019 2017: pid 23508: thd-0x18fd200:
taper: flexstorii: updating state
Wed Nov 08 11:43:16.029230821 2017: pid 23508: thd-0x18fd200:
taper: new Amanda::Changer::Error: type='failed',
reason='notfound', message='No acceptable volumes found'


On Wed, Nov 8, 2017 at 10:15 AM, Jean-Louis Martineau
mailto:[email protected]>> wrote:

On 08/11/17 10:07 AM, Greg Dickie wrote:
> So in /var/

Re: Continuing after "No acceptable volumes found"

2017-11-08 Thread Greg Dickie
Good call, that worked!

Wed Nov 08 12:12:02.180979631 2017: pid 23508: thd-0x18fd200: taper: Device
is in variable block size
Wed Nov 08 12:12:04.573098503 2017: pid 23508: thd-0x18fd200: taper: Slot
14 with label 000114L7 is usable
Wed Nov 08 12:12:04.591316642 2017: pid 23508: thd-0x18fd200: taper:
Building type TAPESTART header of 2097152-2097152 bytes with
name='000114L7' disk='' dumplevel=0 and blocksize=2097152

Rolling again,

Thank you very much for the help,
Greg


On Wed, Nov 8, 2017 at 11:57 AM, Jean-Louis Martineau <
[email protected]> wrote:

> I do not understand why it doesn't want to use the tapes.
>
> Can you try the following: (If you agree amanda can overwrite 000114L7
> amrmtape WeeklySet1 --keep-label 000114L7
> amatpe WeeklySet1 update 14=
>
> After the update, the taper should load the slot, you should see it in the
> taper debug file.
>
> Jean-Louis
>
>
> On 08/11/17 11:45 AM, Greg Dickie wrote:
>
> Wed Nov 08 11:43:15.492889388 2017: pid 23508: thd-0x18fd200: taper:
> invoking /usr/sbin/mtx -f /dev/sg1 status
> Wed Nov 08 11:43:16.026704763 2017: pid 23508: thd-0x18fd200: taper: mtx:
>  Storage Changer /dev/sg1:1 Drives, 24 Slots ( 0 Import/Export )
> Wed Nov 08 11:43:16.026751421 2017: pid 23508: thd-0x18fd200: taper: mtx:
> Data Transfer Element 0:Full (Storage Element 21 Loaded):VolumeTag =
> 000121L7
> Wed Nov 08 11:43:16.026780475 2017: pid 23508: thd-0x18fd200: taper: mtx:
>  Storage Element 1:Empty
> Wed Nov 08 11:43:16.026799697 2017: pid 23508: thd-0x18fd200: taper: mtx:
>  Storage Element 2:Empty
> Wed Nov 08 11:43:16.026809868 2017: pid 23508: thd-0x18fd200: taper: mtx:
>  Storage Element 3:Empty
> Wed Nov 08 11:43:16.026818338 2017: pid 23508: thd-0x18fd200: taper: mtx:
>  Storage Element 4:Empty
> Wed Nov 08 11:43:16.026825880 2017: pid 23508: thd-0x18fd200: taper: mtx:
>  Storage Element 5:Empty
> Wed Nov 08 11:43:16.026833781 2017: pid 23508: thd-0x18fd200: taper: mtx:
>  Storage Element 6:Empty
> Wed Nov 08 11:43:16.026841346 2017: pid 23508: thd-0x18fd200: taper: mtx:
>  Storage Element 7:Empty
> Wed Nov 08 11:43:16.026848729 2017: pid 23508: thd-0x18fd200: taper: mtx:
>  Storage Element 8:Empty
> Wed Nov 08 11:43:16.026857121 2017: pid 23508: thd-0x18fd200: taper: mtx:
>  Storage Element 9:Empty
> Wed Nov 08 11:43:16.026866301 2017: pid 23508: thd-0x18fd200: taper: mtx:
>  Storage Element 10:Full :VolumeTag=000110L7
> Wed Nov 08 11:43:16.026896922 2017: pid 23508: thd-0x18fd200: taper: mtx:
>  Storage Element 11:Full :VolumeTag=000111L7
> Wed Nov 08 11:43:16.026908845 2017: pid 23508: thd-0x18fd200: taper: mtx:
>  Storage Element 12:Full :VolumeTag=000112L7
> Wed Nov 08 11:43:16.026919029 2017: pid 23508: thd-0x18fd200: taper: mtx:
>  Storage Element 13:Full :VolumeTag=000113L7
> Wed Nov 08 11:43:16.026928701 2017: pid 23508: thd-0x18fd200: taper: mtx:
>  Storage Element 14:Full :VolumeTag=000114L7
> Wed Nov 08 11:43:16.026939958 2017: pid 23508: thd-0x18fd200: taper: mtx:
>  Storage Element 15:Full :VolumeTag=000115L7
> Wed Nov 08 11:43:16.026949743 2017: pid 23508: thd-0x18fd200: taper: mtx:
>  Storage Element 16:Full :VolumeTag=000116L7
> Wed Nov 08 11:43:16.026961396 2017: pid 23508: thd-0x18fd200: taper: mtx:
>  Storage Element 17:Full :VolumeTag=000117L7
> Wed Nov 08 11:43:16.026971300 2017: pid 23508: thd-0x18fd200: taper: mtx:
>  Storage Element 18:Full :VolumeTag=000118L7
> Wed Nov 08 11:43:16.026983376 2017: pid 23508: thd-0x18fd200: taper: mtx:
>  Storage Element 19:Full :VolumeTag=000119L7
> Wed Nov 08 11:43:16.026993560 2017: pid 23508: thd-0x18fd200: taper: mtx:
>  Storage Element 20:Full :VolumeTag=000120L7
> Wed Nov 08 11:43:16.027002906 2017: pid 23508: thd-0x18fd200: taper: mtx:
>  Storage Element 21:Empty
> Wed Nov 08 11:43:16.027010865 2017: pid 23508: thd-0x18fd200: taper: mtx:
>  Storage Element 22:Empty
> Wed Nov 08 11:43:16.027019542 2017: pid 23508: thd-0x18fd200: taper: mtx:
>  Storage Element 23:Empty
> Wed Nov 08 11:43:16.027026856 2017: pid 23508: thd-0x18fd200: taper: mtx:
>  Storage Element 24:Empty
> Wed Nov 08 11:43:16.027077019 2017: pid 23508: thd-0x18fd200: taper:
> flexstorii: updating state
> Wed Nov 08 11:43:16.029230821 2017: pid 23508: thd-0x18fd200: taper: new
> Amanda::Changer::Error: type='failed', reason='notfound', message='No
> acceptable volumes found'
>
>
> On Wed, Nov 8, 2017 at 10:15 AM, Jean-Louis Martineau <
> [email protected]> wrote:
>
>> On 08/11/17 10:07 AM, Greg Dickie wrote:
>> > So in /var/lib/amanda/CONFIG I do not see taper logs. I'll figure out
>> > why..
>> run: amgetconf build.amanda_dbgdir
>> Go in the resulting directory /server/WeeklySet1
>>
>> Jean-Louis
>>
>>
>> *Disclaimer*
>>
>> This message is the property of *CARBONITE, INC.*
>>  and may contain confidential or privileged
>> information.
>>
>> If this message has been delivered to you by mistake, then do no

Re: Continuing after "No acceptable volumes found"

2017-11-08 Thread Jean-Louis Martineau

I do not understand why it doesn't want to use the tapes.

Can you try the following: (If you agree amanda can overwrite 000114L7
amrmtape WeeklySet1 --keep-label 000114L7
amatpe WeeklySet1 update 14=

After the update, the taper should load the slot, you should see it in 
the taper debug file.


Jean-Louis

On 08/11/17 11:45 AM, Greg Dickie wrote:
Wed Nov 08 11:43:15.492889388 2017: pid 23508: thd-0x18fd200: taper: 
invoking /usr/sbin/mtx -f /dev/sg1 status
Wed Nov 08 11:43:16.026704763 2017: pid 23508: thd-0x18fd200: taper: 
mtx:   Storage Changer /dev/sg1:1 Drives, 24 Slots ( 0 Import/Export )
Wed Nov 08 11:43:16.026751421 2017: pid 23508: thd-0x18fd200: taper: 
mtx: Data Transfer Element 0:Full (Storage Element 21 
Loaded):VolumeTag = 000121L7
Wed Nov 08 11:43:16.026780475 2017: pid 23508: thd-0x18fd200: taper: 
mtx:   Storage Element 1:Empty
Wed Nov 08 11:43:16.026799697 2017: pid 23508: thd-0x18fd200: taper: 
mtx:   Storage Element 2:Empty
Wed Nov 08 11:43:16.026809868 2017: pid 23508: thd-0x18fd200: taper: 
mtx:   Storage Element 3:Empty
Wed Nov 08 11:43:16.026818338 2017: pid 23508: thd-0x18fd200: taper: 
mtx:   Storage Element 4:Empty
Wed Nov 08 11:43:16.026825880 2017: pid 23508: thd-0x18fd200: taper: 
mtx:   Storage Element 5:Empty
Wed Nov 08 11:43:16.026833781 2017: pid 23508: thd-0x18fd200: taper: 
mtx:   Storage Element 6:Empty
Wed Nov 08 11:43:16.026841346 2017: pid 23508: thd-0x18fd200: taper: 
mtx:   Storage Element 7:Empty
Wed Nov 08 11:43:16.026848729 2017: pid 23508: thd-0x18fd200: taper: 
mtx:   Storage Element 8:Empty
Wed Nov 08 11:43:16.026857121 2017: pid 23508: thd-0x18fd200: taper: 
mtx:   Storage Element 9:Empty
Wed Nov 08 11:43:16.026866301 2017: pid 23508: thd-0x18fd200: taper: 
mtx:   Storage Element 10:Full :VolumeTag=000110L7
Wed Nov 08 11:43:16.026896922 2017: pid 23508: thd-0x18fd200: taper: 
mtx:   Storage Element 11:Full :VolumeTag=000111L7
Wed Nov 08 11:43:16.026908845 2017: pid 23508: thd-0x18fd200: taper: 
mtx:   Storage Element 12:Full :VolumeTag=000112L7
Wed Nov 08 11:43:16.026919029 2017: pid 23508: thd-0x18fd200: taper: 
mtx:   Storage Element 13:Full :VolumeTag=000113L7
Wed Nov 08 11:43:16.026928701 2017: pid 23508: thd-0x18fd200: taper: 
mtx:   Storage Element 14:Full :VolumeTag=000114L7
Wed Nov 08 11:43:16.026939958 2017: pid 23508: thd-0x18fd200: taper: 
mtx:   Storage Element 15:Full :VolumeTag=000115L7
Wed Nov 08 11:43:16.026949743 2017: pid 23508: thd-0x18fd200: taper: 
mtx:   Storage Element 16:Full :VolumeTag=000116L7
Wed Nov 08 11:43:16.026961396 2017: pid 23508: thd-0x18fd200: taper: 
mtx:   Storage Element 17:Full :VolumeTag=000117L7
Wed Nov 08 11:43:16.026971300 2017: pid 23508: thd-0x18fd200: taper: 
mtx:   Storage Element 18:Full :VolumeTag=000118L7
Wed Nov 08 11:43:16.026983376 2017: pid 23508: thd-0x18fd200: taper: 
mtx:   Storage Element 19:Full :VolumeTag=000119L7
Wed Nov 08 11:43:16.026993560 2017: pid 23508: thd-0x18fd200: taper: 
mtx:   Storage Element 20:Full :VolumeTag=000120L7
Wed Nov 08 11:43:16.027002906 2017: pid 23508: thd-0x18fd200: taper: 
mtx:   Storage Element 21:Empty
Wed Nov 08 11:43:16.027010865 2017: pid 23508: thd-0x18fd200: taper: 
mtx:   Storage Element 22:Empty
Wed Nov 08 11:43:16.027019542 2017: pid 23508: thd-0x18fd200: taper: 
mtx:   Storage Element 23:Empty
Wed Nov 08 11:43:16.027026856 2017: pid 23508: thd-0x18fd200: taper: 
mtx:   Storage Element 24:Empty
Wed Nov 08 11:43:16.027077019 2017: pid 23508: thd-0x18fd200: taper: 
flexstorii: updating state
Wed Nov 08 11:43:16.029230821 2017: pid 23508: thd-0x18fd200: taper: 
new Amanda::Changer::Error: type='failed', reason='notfound', 
message='No acceptable volumes found'



On Wed, Nov 8, 2017 at 10:15 AM, Jean-Louis Martineau 
mailto:[email protected]>> wrote:


On 08/11/17 10:07 AM, Greg Dickie wrote:
> So in /var/lib/amanda/CONFIG I do not see taper logs. I'll
figure out
> why..
run: amgetconf build.amanda_dbgdir
Go in the resulting directory /server/WeeklySet1

Jean-Louis


*Disclaimer*

This message is the property of *CARBONITE, INC.*

and may contain confidential or privileged information.

If this message has been delivered to you by mistake, then do not
copy or deliver this message to anyone. Instead, destroy it and
notify me by reply e-mail.




--


Greg Dickie
just a guy
514-983-5400

This message is the property of CARBONITE, INC. and may contain confidential or 
privileged information.
If this message has been delivered to you by mistake, then do not copy or 
deliver this message to anyone.  Instead, destroy it and notify me by reply 
e-mail


Re: Continuing after "No acceptable volumes found"

2017-11-08 Thread Greg Dickie
Wed Nov 08 11:43:15.492889388 2017: pid 23508: thd-0x18fd200: taper:
invoking /usr/sbin/mtx -f /dev/sg1 status
Wed Nov 08 11:43:16.026704763 2017: pid 23508: thd-0x18fd200: taper: mtx:
 Storage Changer /dev/sg1:1 Drives, 24 Slots ( 0 Import/Export )
Wed Nov 08 11:43:16.026751421 2017: pid 23508: thd-0x18fd200: taper: mtx:
Data Transfer Element 0:Full (Storage Element 21 Loaded):VolumeTag =
000121L7
Wed Nov 08 11:43:16.026780475 2017: pid 23508: thd-0x18fd200: taper: mtx:
 Storage Element 1:Empty
Wed Nov 08 11:43:16.026799697 2017: pid 23508: thd-0x18fd200: taper: mtx:
 Storage Element 2:Empty
Wed Nov 08 11:43:16.026809868 2017: pid 23508: thd-0x18fd200: taper: mtx:
 Storage Element 3:Empty
Wed Nov 08 11:43:16.026818338 2017: pid 23508: thd-0x18fd200: taper: mtx:
 Storage Element 4:Empty
Wed Nov 08 11:43:16.026825880 2017: pid 23508: thd-0x18fd200: taper: mtx:
 Storage Element 5:Empty
Wed Nov 08 11:43:16.026833781 2017: pid 23508: thd-0x18fd200: taper: mtx:
 Storage Element 6:Empty
Wed Nov 08 11:43:16.026841346 2017: pid 23508: thd-0x18fd200: taper: mtx:
 Storage Element 7:Empty
Wed Nov 08 11:43:16.026848729 2017: pid 23508: thd-0x18fd200: taper: mtx:
 Storage Element 8:Empty
Wed Nov 08 11:43:16.026857121 2017: pid 23508: thd-0x18fd200: taper: mtx:
 Storage Element 9:Empty
Wed Nov 08 11:43:16.026866301 2017: pid 23508: thd-0x18fd200: taper: mtx:
 Storage Element 10:Full :VolumeTag=000110L7
Wed Nov 08 11:43:16.026896922 2017: pid 23508: thd-0x18fd200: taper: mtx:
 Storage Element 11:Full :VolumeTag=000111L7
Wed Nov 08 11:43:16.026908845 2017: pid 23508: thd-0x18fd200: taper: mtx:
 Storage Element 12:Full :VolumeTag=000112L7
Wed Nov 08 11:43:16.026919029 2017: pid 23508: thd-0x18fd200: taper: mtx:
 Storage Element 13:Full :VolumeTag=000113L7
Wed Nov 08 11:43:16.026928701 2017: pid 23508: thd-0x18fd200: taper: mtx:
 Storage Element 14:Full :VolumeTag=000114L7
Wed Nov 08 11:43:16.026939958 2017: pid 23508: thd-0x18fd200: taper: mtx:
 Storage Element 15:Full :VolumeTag=000115L7
Wed Nov 08 11:43:16.026949743 2017: pid 23508: thd-0x18fd200: taper: mtx:
 Storage Element 16:Full :VolumeTag=000116L7
Wed Nov 08 11:43:16.026961396 2017: pid 23508: thd-0x18fd200: taper: mtx:
 Storage Element 17:Full :VolumeTag=000117L7
Wed Nov 08 11:43:16.026971300 2017: pid 23508: thd-0x18fd200: taper: mtx:
 Storage Element 18:Full :VolumeTag=000118L7
Wed Nov 08 11:43:16.026983376 2017: pid 23508: thd-0x18fd200: taper: mtx:
 Storage Element 19:Full :VolumeTag=000119L7
Wed Nov 08 11:43:16.026993560 2017: pid 23508: thd-0x18fd200: taper: mtx:
 Storage Element 20:Full :VolumeTag=000120L7
Wed Nov 08 11:43:16.027002906 2017: pid 23508: thd-0x18fd200: taper: mtx:
 Storage Element 21:Empty
Wed Nov 08 11:43:16.027010865 2017: pid 23508: thd-0x18fd200: taper: mtx:
 Storage Element 22:Empty
Wed Nov 08 11:43:16.027019542 2017: pid 23508: thd-0x18fd200: taper: mtx:
 Storage Element 23:Empty
Wed Nov 08 11:43:16.027026856 2017: pid 23508: thd-0x18fd200: taper: mtx:
 Storage Element 24:Empty
Wed Nov 08 11:43:16.027077019 2017: pid 23508: thd-0x18fd200: taper:
flexstorii: updating state
Wed Nov 08 11:43:16.029230821 2017: pid 23508: thd-0x18fd200: taper: new
Amanda::Changer::Error: type='failed', reason='notfound', message='No
acceptable volumes found'


On Wed, Nov 8, 2017 at 10:15 AM, Jean-Louis Martineau <
[email protected]> wrote:

> On 08/11/17 10:07 AM, Greg Dickie wrote:
> > So in /var/lib/amanda/CONFIG I do not see taper logs. I'll figure out
> > why..
> run: amgetconf build.amanda_dbgdir
> Go in the resulting directory /server/WeeklySet1
>
> Jean-Louis
>
>
> *Disclaimer*
>
> This message is the property of *CARBONITE, INC.*
>  and may contain confidential or privileged
> information.
>
> If this message has been delivered to you by mistake, then do not copy or
> deliver this message to anyone. Instead, destroy it and notify me by reply
> e-mail.
>



-- 


Greg Dickie
just a guy
514-983-5400


Re: Continuing after "No acceptable volumes found"

2017-11-08 Thread Jean-Louis Martineau

On 08/11/17 10:07 AM, Greg Dickie wrote:
So in /var/lib/amanda/CONFIG I do not see taper logs. I'll figure out 
why..

run: amgetconf build.amanda_dbgdir
Go in the resulting directory /server/WeeklySet1

Jean-Louis
This message is the property of CARBONITE, INC. and may contain confidential or 
privileged information.
If this message has been delivered to you by mistake, then do not copy or 
deliver this message to anyone.  Instead, destroy it and notify me by reply 
e-mail


Re: Continuing after "No acceptable volumes found"

2017-11-08 Thread Greg Dickie
So in /var/lib/amanda/CONFIG I do not see taper logs. I'll figure out why..

touching the file regenerates the email so it's looking at the file. I ran

amtape WeeklySet1 update 14-21=

no change.

Lots of helpful info here, thanks guys.

Greg

On Wed, Nov 8, 2017 at 9:52 AM, Nathan Stratton Treadway  wrote:

> On Wed, Nov 08, 2017 at 09:17:31 -0500, Greg Dickie wrote:
> > running 3.4.5 and interactivity is set up
>
> Okay, good.
>
> >   but whatever I do to the
> > /tmp/email_input file just recreates the message. I'm pretty sure if I
> put
>
> You mean it just sends repeatedly sends new email messages?
>
> The line at the bottom of each message should tell you want it is
> waiting for, and i.e. the time stamp mentioned in that message should
> change if you make any changes to the file.
>
> Assume that it is monitoring the email_input file as expected, I belive
> the fact that the dump hasn't proceeded implies that the taper doesn't
> actually think it has an acceptable tape.  You may find some hints
> regarding that problem in the taper.*.debug file.
> ("Amanda::Changer::Error" is a string I see there when the taper is
> searching for a usuable volume.)
>
> Nathan
>
> 
> 
> Nathan Stratton Treadway  -  [email protected]  -  Mid-Atlantic region
> Ray Ontko & Co.  -  Software consulting services  -
> http://www.ontko.com/
>  GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt   ID: 1023D/ECFB6239
>  Key fingerprint = 6AD8 485E 20B9 5C71 231C  0C32 15F3 ADCD ECFB 6239
>



-- 


Greg Dickie
just a guy
514-983-5400


Re: Continuing after "No acceptable volumes found"

2017-11-08 Thread Nathan Stratton Treadway
On Wed, Nov 08, 2017 at 09:17:31 -0500, Greg Dickie wrote:
> running 3.4.5 and interactivity is set up

Okay, good.

>   but whatever I do to the
> /tmp/email_input file just recreates the message. I'm pretty sure if I put

You mean it just sends repeatedly sends new email messages? 

The line at the bottom of each message should tell you want it is
waiting for, and i.e. the time stamp mentioned in that message should
change if you make any changes to the file.

Assume that it is monitoring the email_input file as expected, I belive
the fact that the dump hasn't proceeded implies that the taper doesn't
actually think it has an acceptable tape.  You may find some hints
regarding that problem in the taper.*.debug file. 
("Amanda::Changer::Error" is a string I see there when the taper is
searching for a usuable volume.)

Nathan


Nathan Stratton Treadway  -  [email protected]  -  Mid-Atlantic region
Ray Ontko & Co.  -  Software consulting services  -   http://www.ontko.com/
 GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt   ID: 1023D/ECFB6239
 Key fingerprint = 6AD8 485E 20B9 5C71 231C  0C32 15F3 ADCD ECFB 6239


Re: Continuing after "No acceptable volumes found"

2017-11-08 Thread Jean-Louis Martineau

The taper debug files, not the taperscan debug file

Try: amtape WeeklySet1 update 14-21=

On 08/11/17 09:43 AM, Greg Dickie wrote:

define interactivity inter_tty_email {
plugin "tty_email"
property "mailto" "[email protected] "
property "resend-delay" "0"
property "check-file" "/tmp/email_input"
property "check-file-delay" "10"
}
interactivity "inter_tty_email"

define taperscan taper_traditional {
comment "traditional"
plugin "traditional"
}
define taperscan taper_oldest {
comment "oldest"
plugin "oldest"
}
define taperscan taper_lexical {
comment "lexical"
plugin "lexical"
}
taperscan "taper_lexical"



touching the file sends another email:

No acceptable volumes found

Insert a new volume in flexstorii
or write the name of a new changer in '/tmp/email_input'
or write 'abort' in the file to abort the scan.

(Waiting for the file to be modified after:
Wed Nov  8 09:38:12 2017.)

**
[root@backup WeeklySet1]# sudo -u amandabackup amtape WeeklySet1 inventory
slot 1: empty (current)
slot 2: empty
slot 3: empty
slot 4: empty
slot 5: empty
slot 6: empty
slot 7: empty
slot 8: empty
slot 9: empty
slot 10: label 000110L7 barcode 000110L7 [retention-tapes]
slot 11: label 000111L7 barcode 000111L7 [retention-tapes]
slot 12: label 000112L7 barcode 000112L7 [retention-tapes]
slot 13: label 000113L7 barcode 000113L7 [retention-tapes]
slot 14: label 000114L7 barcode 000114L7 (in drive 0) [retention-no]
slot 15: label 000115L7 barcode 000115L7 [retention-no]
slot 16: label 000116L7 barcode 000116L7 [retention-no]
slot 17: label 000117L7 barcode 000117L7 [retention-no]
slot 18: label 000118L7 barcode 000118L7 [retention-no]
slot 19: label 000119L7 barcode 000119L7 [retention-no]
slot 20: label 000120L7 barcode 000120L7 [retention-no]
slot 21: label 000121L7 barcode 000121L7 [retention-no]
slot 22: empty
slot 23: empty
slot 24: empty

Cannot find any taperscan logs, I guess I need to enable them?

Thanks,
Greg







On Wed, Nov 8, 2017 at 9:28 AM, Jean-Louis Martineau 
mailto:[email protected]>> wrote:


On 08/11/17 09:17 AM, Greg Dickie wrote:

running 3.4.5 and interactivity is set up but whatever I do to
the /tmp/email_input file just recreates the message. I'm pretty
sure if I put abort in there it will abort but I don't want to
abort unless there is no choice.


How the interactivity is configured?
Which taperscan are you using?
What happen if you 'touch /tmp/email_input'?
Post the taper debug files.

Are you sure you have a tape amanda can use in the changer?
Post the output of 'amtape CONFIG inventory'

Jean-Louis



no holding disk, backing up 48TB.

Thanks,
Greg

On Wed, Nov 8, 2017 at 9:03 AM, Nathan Stratton Treadway
mailto:[email protected]>> wrote:

On Tue, Nov 07, 2017 at 18:23:25 -0500, Greg Dickie wrote:
>   After 32TB of 48TB backed up I suddenly get a "No
acceptable volumes
> found". Is there a way to continue the backup rather than
aborting and
> restarting? I have ensured there are valid tape loaded.

What version of Amanda are you running (on the server)?

Do you have a holding disk configured?  If so, normally
Amanda will go
ahead and dump the remaining DLEs there before aborting, and
you can
then flush those dumps to the next tape with "amflush".  (The
emailed
Amanda report would have some hints about what exactly happened.)

  Nsthan



Nathan Stratton Treadway  - [email protected]
 -  Mid-Atlantic region
Ray Ontko & Co.  -  Software consulting services  -
http://www.ontko.com/

 GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt

 ID: 1023D/ECFB6239
 Key fingerprint = 6AD8 485E 20B9 5C71 231C  0C32 15F3 ADCD
ECFB 6239




-- 



Greg Dickie
just a guy
514-983-5400 





*Disclaimer*

This message is the property of *CARBONITE, INC.*

and may contain confidential or privileged information.

If this message has been delivered to you by mistake, then do not
copy or deliver this message to anyone. Instead, destroy it and
notify me by reply e-mail.




--


Greg Dickie
just a guy
514-983-5400

This message is the property of CARBONITE, INC. and may contain confidential or 
privileged information.
If this message has been delivered to you by mistake, then do not copy or 
deli

Re: Continuing after "No acceptable volumes found"

2017-11-08 Thread Greg Dickie
define interactivity inter_tty_email {
plugin "tty_email"
property "mailto" "[email protected]"
property "resend-delay" "0"
property "check-file" "/tmp/email_input"
property "check-file-delay" "10"
}
interactivity "inter_tty_email"

define taperscan taper_traditional {
comment "traditional"
plugin "traditional"
}
define taperscan taper_oldest {
comment "oldest"
plugin "oldest"
}
define taperscan taper_lexical {
comment "lexical"
plugin "lexical"
}
taperscan "taper_lexical"



touching the file sends another email:

No acceptable volumes found

Insert a new volume in flexstorii
or write the name of a new changer in '/tmp/email_input'
or write 'abort' in the file to abort the scan.

(Waiting for the file to be modified after:
Wed Nov  8 09:38:12 2017.)

**
[root@backup WeeklySet1]# sudo -u amandabackup amtape WeeklySet1 inventory
slot 1: empty (current)
slot 2: empty
slot 3: empty
slot 4: empty
slot 5: empty
slot 6: empty
slot 7: empty
slot 8: empty
slot 9: empty
slot 10: label 000110L7 barcode 000110L7 [retention-tapes]
slot 11: label 000111L7 barcode 000111L7 [retention-tapes]
slot 12: label 000112L7 barcode 000112L7 [retention-tapes]
slot 13: label 000113L7 barcode 000113L7 [retention-tapes]
slot 14: label 000114L7 barcode 000114L7 (in drive 0) [retention-no]
slot 15: label 000115L7 barcode 000115L7 [retention-no]
slot 16: label 000116L7 barcode 000116L7 [retention-no]
slot 17: label 000117L7 barcode 000117L7 [retention-no]
slot 18: label 000118L7 barcode 000118L7 [retention-no]
slot 19: label 000119L7 barcode 000119L7 [retention-no]
slot 20: label 000120L7 barcode 000120L7 [retention-no]
slot 21: label 000121L7 barcode 000121L7 [retention-no]
slot 22: empty
slot 23: empty
slot 24: empty

Cannot find any taperscan logs, I guess I need to enable them?

Thanks,
Greg







On Wed, Nov 8, 2017 at 9:28 AM, Jean-Louis Martineau <
[email protected]> wrote:

> On 08/11/17 09:17 AM, Greg Dickie wrote:
>
> running 3.4.5 and interactivity is set up but whatever I do to the
> /tmp/email_input file just recreates the message. I'm pretty sure if I put
> abort in there it will abort but I don't want to abort unless there is no
> choice.
>
>
> How the interactivity is configured?
> Which taperscan are you using?
> What happen if you 'touch /tmp/email_input'?
> Post the taper debug files.
>
> Are you sure you have a tape amanda can use in the changer?
> Post the output of 'amtape CONFIG inventory'
>
> Jean-Louis
>
>
> no holding disk, backing up 48TB.
>
> Thanks,
> Greg
>
> On Wed, Nov 8, 2017 at 9:03 AM, Nathan Stratton Treadway <
> [email protected]> wrote:
>
>> On Tue, Nov 07, 2017 at 18:23:25 -0500, Greg Dickie wrote:
>> >   After 32TB of 48TB backed up I suddenly get a "No acceptable volumes
>> > found". Is there a way to continue the backup rather than aborting and
>> > restarting? I have ensured there are valid tape loaded.
>>
>> What version of Amanda are you running (on the server)?
>>
>> Do you have a holding disk configured?  If so, normally Amanda will go
>> ahead and dump the remaining DLEs there before aborting, and you can
>> then flush those dumps to the next tape with "amflush".  (The emailed
>> Amanda report would have some hints about what exactly happened.)
>>
>> Nsthan
>>
>> 
>> 
>> Nathan Stratton Treadway  -  [email protected]  -  Mid-Atlantic region
>> Ray Ontko & Co.  -  Software consulting services  -
>> http://www.ontko.com/
>>  GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt   ID: 1023D/ECFB6239
>>  Key fingerprint = 6AD8 485E 20B9 5C71 231C  0C32 15F3 ADCD ECFB 6239
>>
>
>
>
> --
>
>
> Greg Dickie
> just a guy
> 514-983-5400 <(514)%20983-5400>
>
>
>
>
> *Disclaimer*
>
> This message is the property of *CARBONITE, INC.*
>  and may contain confidential or privileged
> information.
>
> If this message has been delivered to you by mistake, then do not copy or
> deliver this message to anyone. Instead, destroy it and notify me by reply
> e-mail.
>



-- 


Greg Dickie
just a guy
514-983-5400


Re: Continuing after "No acceptable volumes found"

2017-11-08 Thread Jean-Louis Martineau

On 08/11/17 09:17 AM, Greg Dickie wrote:
running 3.4.5 and interactivity is set up but whatever I do to the 
/tmp/email_input file just recreates the message. I'm pretty sure if I 
put abort in there it will abort but I don't want to abort unless 
there is no choice.


How the interactivity is configured?
Which taperscan are you using?
What happen if you 'touch /tmp/email_input'?
Post the taper debug files.

Are you sure you have a tape amanda can use in the changer?
Post the output of 'amtape CONFIG inventory'

Jean-Louis



no holding disk, backing up 48TB.

Thanks,
Greg

On Wed, Nov 8, 2017 at 9:03 AM, Nathan Stratton Treadway 
mailto:[email protected]>> wrote:


On Tue, Nov 07, 2017 at 18:23:25 -0500, Greg Dickie wrote:
>   After 32TB of 48TB backed up I suddenly get a "No acceptable
volumes
> found". Is there a way to continue the backup rather than
aborting and
> restarting? I have ensured there are valid tape loaded.

What version of Amanda are you running (on the server)?

Do you have a holding disk configured?  If so, normally Amanda will go
ahead and dump the remaining DLEs there before aborting, and you can
then flush those dumps to the next tape with "amflush". (The emailed
Amanda report would have some hints about what exactly happened.)

Nsthan


Nathan Stratton Treadway  - [email protected]
 -  Mid-Atlantic region
Ray Ontko & Co.  -  Software consulting services  -
http://www.ontko.com/

 GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt

 ID: 1023D/ECFB6239
 Key fingerprint = 6AD8 485E 20B9 5C71 231C  0C32 15F3 ADCD ECFB 6239




--


Greg Dickie
just a guy
514-983-5400

This message is the property of CARBONITE, INC. and may contain confidential or 
privileged information.
If this message has been delivered to you by mistake, then do not copy or 
deliver this message to anyone.  Instead, destroy it and notify me by reply 
e-mail


Re: Continuing after "No acceptable volumes found"

2017-11-08 Thread Greg Dickie
running 3.4.5 and interactivity is set up but whatever I do to the
/tmp/email_input file just recreates the message. I'm pretty sure if I put
abort in there it will abort but I don't want to abort unless there is no
choice.

no holding disk, backing up 48TB.

Thanks,
Greg

On Wed, Nov 8, 2017 at 9:03 AM, Nathan Stratton Treadway  wrote:

> On Tue, Nov 07, 2017 at 18:23:25 -0500, Greg Dickie wrote:
> >   After 32TB of 48TB backed up I suddenly get a "No acceptable volumes
> > found". Is there a way to continue the backup rather than aborting and
> > restarting? I have ensured there are valid tape loaded.
>
> What version of Amanda are you running (on the server)?
>
> Do you have a holding disk configured?  If so, normally Amanda will go
> ahead and dump the remaining DLEs there before aborting, and you can
> then flush those dumps to the next tape with "amflush".  (The emailed
> Amanda report would have some hints about what exactly happened.)
>
> Nsthan
>
> 
> 
> Nathan Stratton Treadway  -  [email protected]  -  Mid-Atlantic region
> Ray Ontko & Co.  -  Software consulting services  -
> http://www.ontko.com/
>  GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt   ID: 1023D/ECFB6239
>  Key fingerprint = 6AD8 485E 20B9 5C71 231C  0C32 15F3 ADCD ECFB 6239
>



-- 


Greg Dickie
just a guy
514-983-5400


Re: Continuing after "No acceptable volumes found"

2017-11-08 Thread Nathan Stratton Treadway
On Tue, Nov 07, 2017 at 18:23:25 -0500, Greg Dickie wrote:
>   After 32TB of 48TB backed up I suddenly get a "No acceptable volumes
> found". Is there a way to continue the backup rather than aborting and
> restarting? I have ensured there are valid tape loaded.

What version of Amanda are you running (on the server)?

Do you have a holding disk configured?  If so, normally Amanda will go
ahead and dump the remaining DLEs there before aborting, and you can
then flush those dumps to the next tape with "amflush".  (The emailed
Amanda report would have some hints about what exactly happened.)

Nsthan


Nathan Stratton Treadway  -  [email protected]  -  Mid-Atlantic region
Ray Ontko & Co.  -  Software consulting services  -   http://www.ontko.com/
 GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt   ID: 1023D/ECFB6239
 Key fingerprint = 6AD8 485E 20B9 5C71 231C  0C32 15F3 ADCD ECFB 6239


Re: Continuing after "No acceptable volumes found"

2017-11-08 Thread Jean-Louis Martineau

On 07/11/17 06:23 PM, Greg Dickie wrote:

Hi,


  After 32TB of 48TB backed up I suddenly get a "No acceptable volumes 
found". Is there a way to continue the backup rather than aborting and 
restarting? I have ensured there are valid tape loaded.

There is no way to continue the current run.

But for the future run, you can add an interactivity, and amanda will 
ask you what to do if doesn't find a volume to write to.


Jean-Louis


Thanks,
Greg

--


Greg Dickie
just a guy
514-983-5400

This message is the property of CARBONITE, INC. and may contain confidential or 
privileged information.
If this message has been delivered to you by mistake, then do not copy or 
deliver this message to anyone.  Instead, destroy it and notify me by reply 
e-mail