PDA

View Full Version : tapedev "null:" problems



r8qt7
November 23rd, 2012, 01:23 AM
Hi,

for testing purposes I would like to use the null device. I included a tapetype.conf in my amanda.conf file


tapetype.conf:

tapedev "null:"
tapetype HD

define tapetype HD {
comment "Backup to Null"
length 7 tbytes
}


I'll get an error with amcheck:

backup@chronos:/etc/amanda/a2g$ amcheck a2g
Amanda Tape Server Host Check
-----------------------------
Holding disk /u1/amanda/ahd: 8528060416 kB disk space available, using 7516192768 kB as requested
found in slot 1: Can't open NULL device for reading or appending.
slot 1: Can't open NULL device for reading or appending.
all slots have been loaded
Taper scan algorithm did not find an acceptable volume.
(expecting a new volume)
ERROR: No acceptable volumes found

...


The man pages weren't very specific about it.

If I want to use just a null device to test if the 'grabbing' from the servers works fine: How do I do it?

martineau
November 23rd, 2012, 04:32 AM
The null device works only as a sub device of the rait device, I never tested it as a simple device.

The attached patch enable it to works as a simple device.

It require autolabel and a matching labelstr:
tapedev "null:"
autolabel "NULL-%%%" any
labelstr "NULL-[0-9][0-9][0-9]"

r8qt7
November 28th, 2012, 06:05 AM
The null device works only as a sub device of the rait device, I never tested it as a simple device.

The attached patch enable it to works as a simple device.

It require autolabel and a matching labelstr:
tapedev "null:"
autolabel "NULL-%%%" any
labelstr "NULL-[0-9][0-9][0-9]"

Sounds great. Will there be an update to the official branch?

martineau
November 28th, 2012, 06:22 AM
The patch is committed and will be in 3.3.3