Re: amanda-3.4 amtapetype: Error setting FSF_AFTER_FILEMARK

[Jean-Francois Malouin]

Hi,

* Jean-Louis Martineau <jmartin...@carbonite.com> [20161114 12:00]:
> Try the attached patch.

That seemed to have done it. So far so good and still going but looking
good. Smaller block size used here compared to what I used before with
hw compression on so it doesn't compare directly with what I had before.


~amanda/sbin/amtapetype -f -b 256k -t tape-lto6 /dev/nst0
Checking for FSF_AFTER_FILEMARK requirement
Applying heuristic check for compression.
Wrote random (uncompressible) data at 28406877.0909091 bytes/sec
Wrote fixed (compressible) data at 156237824 bytes/sec  
Compression: enabled
Writing one file to fill the volume.
Wrote 2518892150784 bytes at 130857 kb/sec  
Writing smaller files (25188892672 bytes) to determine filemark.
File 17, block 54320

Thanks Jean-Louis!
jf

> 
> Jean-Louis
> 
> On 14/11/16 10:06 AM, Jean-Francois Malouin wrote:
> >Hi,
> >
> >Amanda-3.4 and a new LTO6 tape library:
> >
> >~amanda/sbin/amtapetype --version
> >amtapetype-3.4
> >
> >~amanda/sbin/amtapetype -b 2048k -t tape-lto6 -f /dev/nst1
> >Checking for FSF_AFTER_FILEMARK requirement
> >amtapetype: Error setting FSF_AFTER_FILEMARK: Success at 
> >/opt/amanda/sbin/amtapetype line 372.
> >
> >Any ideas?
> >
> >The 3.3.6 version happily produced an tapetype entry:
> >
> >/usr/sbin/amtapetype --version
> >amtapetype-3.3.6
> >
> >/usr/sbin/amtapetype -b 2048k -t tape-lto6 -f /dev/nst1
> >
> >define tapetype tape-lto6 {
> > comment "Created by amtapetype; compression disabled"
> > length 2459914240 kbytes
> > filemark 3227 kbytes
> > speed 156832 kps
> > blocksize 2048 kbytes
> >}
> ># LEOM is not supported for this drive and kernel
> >
> >
> >Thanks,
> >jf
> 
> 

> diff --git a/device-src/amtapetype.pl b/device-src/amtapetype.pl
> index d46fbc5..60f9475 100644
> --- a/device-src/amtapetype.pl
> +++ b/device-src/amtapetype.pl
> @@ -368,8 +368,10 @@ sub check_property {
>  $device->finish();
>  
>  #set fsf_after_filemark to false
> -$device->property_set('FSF_AFTER_FILEMARK', 0)
> - or die "Error setting FSF_AFTER_FILEMARK: " . 
> $device->error_or_status();
> +my $r = $device->property_set('FSF_AFTER_FILEMARK', 0);
> +if ($r) {
> + die "Error setting FSF_AFTER_FILEMARK: $r";
> +}
>  
>  my $need_fsf_after_filemark = 0;
>  
> @@ -420,8 +422,10 @@ sub check_property {
>  my $fsf_after_filemark_works = 0;
>  if ($need_fsf_after_filemark) {
>   #set fsf_after_filemark to true
> - $device->property_set('FSF_AFTER_FILEMARK', 1)
> - or die "Error setting FSF_AFTER_FILEMARK: " . 
> $device->error_or_status();
> + $r = $device->property_set('FSF_AFTER_FILEMARK', 1);
> + if ($r) {
> + die "Error setting FSF_AFTER_FILEMARK: $r";
> + }
>  
>   if ($device->read_label() != $DEVICE_STATUS_SUCCESS) {
>   die ("Could not read label from: " . $device->error_or_status());
> @@ -467,12 +471,18 @@ sub check_property {
>   if (defined $opt_property || $fsf_after_filemark) {
>   print STDOUT "device-property \"FSF_AFTER_FILEMARK\" \"false\"\n";
>   }
> - $device->property_set('FSF_AFTER_FILEMARK', 0);
> + $r = $device->property_set('FSF_AFTER_FILEMARK', 0);
> + if ($r) {
> + die "Error setting FSF_AFTER_FILEMARK: $r";
> + }
>  } elsif ($need_fsf_after_filemark == 1 && $fsf_after_filemark_works == 
> 1) {
>   if (defined $opt_property || !$fsf_after_filemark) {
>   print STDOUT "device-property \"FSF_AFTER_FILEMARK\" \"true\"\n";
>   }
> - $device->property_set('FSF_AFTER_FILEMARK', 1);
> + $r = $device->property_set('FSF_AFTER_FILEMARK', 1);
> + if ($r) {
> + die "Error setting FSF_AFTER_FILEMARK: $r";
> + }
>  } else {
>   die ("Broken seek_file");
>  }

Re: amanda-3.4 amtapetype: Error setting FSF_AFTER_FILEMARK

[Uwe Menges]

On 11/14/16 16:06, Jean-Francois Malouin wrote:
> amtapetype: Error setting FSF_AFTER_FILEMARK: Success at 
> /opt/amanda/sbin/amtapetype line 372.
> 
> Any ideas?

The IRC bot recently pointed at https://git.io/vXPb4

Yours, Uwe

Re: amanda-3.4: new parameters etc

[Stefan G. Weichinger]

Am 2016-11-14 um 18:07 schrieb Ochressandro Rettinger:
>   This is what I have in my 3.4 config for a single tape drive:
> 
> ---
> tapetype "LTO6"
> define tapetype LTO6 {  
> comment "Created by amtapetype; compression disabled"
> length 2459879424 kbytes
> filemark 2684 kbytes
> speed 154767 kps
> blocksize 256 kbytes
> }
> 
> define changer "tape_drive" {
> tpchanger "chg-single:tape:/dev/nst0"
> device-property "BLOCK_SIZE" "256 kbytes"
> }
> 
> tpchanger "tape_drive"
> ---
> 
> 
>   It works for me.  I have made backups and recovered from them.

yes, works here as well, thanks (nightly dumps and restore-test still to
do here).

Do you agree that it is different from the man-pages ... ?
Stefan

RE: amanda-3.4: new parameters etc

[Ochressandro Rettinger]

This is what I have in my 3.4 config for a single tape drive:

---
tapetype "LTO6"
define tapetype LTO6 {  
comment "Created by amtapetype; compression disabled"
length 2459879424 kbytes
filemark 2684 kbytes
speed 154767 kps
blocksize 256 kbytes
}

define changer "tape_drive" {
tpchanger "chg-single:tape:/dev/nst0"
device-property "BLOCK_SIZE" "256 kbytes"
}

tpchanger "tape_drive"
---


It works for me.  I have made backups and recovered from them.

-Sandro

-Original Message-
From: owner-amanda-us...@amanda.org [mailto:owner-amanda-us...@amanda.org] On 
Behalf Of Stefan G. Weichinger
Sent: Monday, November 14, 2016 9:36 AM
To: Jean-Francois Malouin ; 
amanda-users@amanda.org
Subject: Re: amanda-3.4: new parameters etc

Am 2016-11-14 um 17:12 schrieb Jean-Francois Malouin:

> I'm just starting experimenting with amanda-3.4 new feature set so I 
> can't really say anything relevant at the moment. I'm still curious at 
> the new 'storage' and 'policy' stuff and will experiment with them 
> later this week.
> 
> Regarding your problem, I usually have the tapedev enclosed in a 
> define section like:
> 
> define device "lto6-drive" {
>   tapedev "tape:/dev/nst1"
>   device-property "BLOCK_SIZE" "2 mbytes"
> }
> 
> and then have tpchanger reference it like this:
> 
> define changer "neo-t48" {
>   tpchanger "chg-robot:/dev/changer"
>   changerfile "/opt/amanda/etc/amanda/neo-t48-state"
>   property "tape-device" "1=lto6-drive"
>   property "use-slots" "1-48"
>   property "eject-before-unload" "yes"
>   property "eject-delay" "20s"
>   property "unload-delay" "2s"
>   property "load-poll" "5s poll 20s until 180s"
>   property "status-interval" "5s"
> }
> 
> tpchanger "neo-t48"
> 
> amcheck seems happy with those.

thanks for providing this example.

I am looking for a more basic setup: no changer, just a single tape drive. Most 
of my customers servers are set up this way, I will approach the changer-setups 
later (doing it with vtapes already, btw)

-

As always I try to follow the documentation ;-)

It says ( http://wiki.zmanda.com/man/amanda.conf.5.html ):

> tapedev string
> 
> Default: "null:". This parameter can either specify a device 
> (explicitly or by referencing a device definition

[..]

> tpchanger string
> 
> Default: not set. (deprecated)

so I have:

tapedev "tape:/dev/nst0"

in /etc/amanda/daily/amanda.conf

and no string/parameter "tpchanger" anywhere in that file.

But amcheck gives:

$ amcheck daily
Amanda Tape Server Host Check
-
NOTE: Holding disk '/mnt/amhold/daily': 112 GB disk space available, using 111 
GB
ERROR: You must specify the storage 'tpchanger'

*maybe* a bug, maybe my fault somewhere.

I even tried to define and use a storage section like that:

define storage tpchanger {
runtapes 1 # just set something for tests }

storage tpchanger

... didn't change a thing.

Re: amanda-3.4: new parameters etc

[Stefan G. Weichinger]

Am 2016-11-14 um 17:12 schrieb Jean-Francois Malouin:

> I'm just starting experimenting with amanda-3.4 new feature set so I
> can't really say anything relevant at the moment. I'm still curious at
> the new 'storage' and 'policy' stuff and will experiment with them later
> this week.
> 
> Regarding your problem, I usually have the tapedev enclosed in a define
> section like:
> 
> define device "lto6-drive" {
>   tapedev "tape:/dev/nst1"
>   device-property "BLOCK_SIZE" "2 mbytes"
> }
> 
> and then have tpchanger reference it like this:
> 
> define changer "neo-t48" {
>   tpchanger "chg-robot:/dev/changer"
>   changerfile "/opt/amanda/etc/amanda/neo-t48-state"
>   property "tape-device" "1=lto6-drive"
>   property "use-slots" "1-48"
>   property "eject-before-unload" "yes"
>   property "eject-delay" "20s"
>   property "unload-delay" "2s"
>   property "load-poll" "5s poll 20s until 180s"
>   property "status-interval" "5s"
> }
> 
> tpchanger "neo-t48"
> 
> amcheck seems happy with those.

thanks for providing this example.

I am looking for a more basic setup: no changer, just a single tape
drive. Most of my customers servers are set up this way, I will approach
the changer-setups later (doing it with vtapes already, btw)

-

As always I try to follow the documentation ;-)

It says ( http://wiki.zmanda.com/man/amanda.conf.5.html ):

> tapedev string
> 
> Default: "null:". This parameter can either specify a device (explicitly 
> or by referencing a device definition

[..]

> tpchanger string
> 
> Default: not set. (deprecated)

so I have:

tapedev "tape:/dev/nst0"

in /etc/amanda/daily/amanda.conf

and no string/parameter "tpchanger" anywhere in that file.

But amcheck gives:

$ amcheck daily
Amanda Tape Server Host Check
-
NOTE: Holding disk '/mnt/amhold/daily': 112 GB disk space available,
using 111 GB
ERROR: You must specify the storage 'tpchanger'

*maybe* a bug, maybe my fault somewhere.

I even tried to define and use a storage section like that:

define storage tpchanger {
runtapes 1 # just set something for tests
}

storage tpchanger

... didn't change a thing.

Re: amanda-3.4: new parameters etc

[Jean-Francois Malouin]

* Stefan G. Weichinger <s...@amanda.org> [20161114 09:00]:
> 
> I am trying to make my amanda.conf work with 3.4
> 
> Has anyone done that already, any experience with the new sections like
> "storage" etc?
> 
> For example amcheck tells me to define a storage called "tpchanger" when
> I have a simple config for a single tapedev:
> 
> tapedev "tape:/dev/nst0"
> 
> pls let's discuss and learn things ;-)
> 
> Stefan

I'm just starting experimenting with amanda-3.4 new feature set so I
can't really say anything relevant at the moment. I'm still curious at
the new 'storage' and 'policy' stuff and will experiment with them later
this week.

Regarding your problem, I usually have the tapedev enclosed in a define
section like:

define device "lto6-drive" {
  tapedev "tape:/dev/nst1"
  device-property "BLOCK_SIZE" "2 mbytes"
}

and then have tpchanger reference it like this:

define changer "neo-t48" {
  tpchanger "chg-robot:/dev/changer"
  changerfile "/opt/amanda/etc/amanda/neo-t48-state"
  property "tape-device" "1=lto6-drive"
  property "use-slots" "1-48"
  property "eject-before-unload" "yes"
  property "eject-delay" "20s"
  property "unload-delay" "2s"
  property "load-poll" "5s poll 20s until 180s"
  property "status-interval" "5s"
}

tpchanger "neo-t48"

amcheck seems happy with those.

cheers,
jf

RE: amanda-3.4 amtapetype: Error setting FSF_AFTER_FILEMARK

[Ochressandro Rettinger]

I had the same problem.  I tried debugging it, but couldn't figure out 
why it was failing, because the code returned was for success.  So, I turned 
the die() into a warn(), which, since it wasn't actually failing, never fired 
off.

-Sandro


-Original Message-
From: owner-amanda-us...@amanda.org [mailto:owner-amanda-us...@amanda.org] On 
Behalf Of Jean-Francois Malouin
Sent: Monday, November 14, 2016 8:06 AM
To: AMANDA users 
Subject: amanda-3.4 amtapetype: Error setting FSF_AFTER_FILEMARK

Hi,

Amanda-3.4 and a new LTO6 tape library:

~amanda/sbin/amtapetype --version
amtapetype-3.4

~amanda/sbin/amtapetype -b 2048k -t tape-lto6 -f /dev/nst1 Checking for 
FSF_AFTER_FILEMARK requirement
amtapetype: Error setting FSF_AFTER_FILEMARK: Success at 
/opt/amanda/sbin/amtapetype line 372.

Any ideas?

The 3.3.6 version happily produced an tapetype entry:

/usr/sbin/amtapetype --version
amtapetype-3.3.6

/usr/sbin/amtapetype -b 2048k -t tape-lto6 -f /dev/nst1

define tapetype tape-lto6 { 
comment "Created by amtapetype; compression disabled"
length 2459914240 kbytes
filemark 3227 kbytes
speed 156832 kps
blocksize 2048 kbytes
}
# LEOM is not supported for this drive and kernel


Thanks,
jf

amanda-3.4 amtapetype: Error setting FSF_AFTER_FILEMARK

[Jean-Francois Malouin]

Hi,

Amanda-3.4 and a new LTO6 tape library:

~amanda/sbin/amtapetype --version
amtapetype-3.4

~amanda/sbin/amtapetype -b 2048k -t tape-lto6 -f /dev/nst1
Checking for FSF_AFTER_FILEMARK requirement
amtapetype: Error setting FSF_AFTER_FILEMARK: Success at 
/opt/amanda/sbin/amtapetype line 372.

Any ideas?

The 3.3.6 version happily produced an tapetype entry:

/usr/sbin/amtapetype --version
amtapetype-3.3.6

/usr/sbin/amtapetype -b 2048k -t tape-lto6 -f /dev/nst1

define tapetype tape-lto6 { 
comment "Created by amtapetype; compression disabled"
length 2459914240 kbytes
filemark 3227 kbytes
speed 156832 kps
blocksize 2048 kbytes
}
# LEOM is not supported for this drive and kernel


Thanks,
jf

amanda-3.4: new parameters etc

[Stefan G. Weichinger]

I am trying to make my amanda.conf work with 3.4

Has anyone done that already, any experience with the new sections like
"storage" etc?

For example amcheck tells me to define a storage called "tpchanger" when
I have a simple config for a single tapedev:

tapedev "tape:/dev/nst0"

pls let's discuss and learn things ;-)

Stefan

Re: using smbclient-4.x

[Stefan G. Weichinger]

Am 2016-11-14 um 10:45 schrieb Stefan G. Weichinger:
> 
> remember amanda-3.3.9 using a recent smbclient?
> 
> I get:
> 
> smbclient: Error reading password from file descriptor 3: empty password
> 
> Has anyone found a workaround (aside from downgrading samba)?
> Is that fixed in 3.4?
> 

backported

https://github.com/zmanda/amanda/commit/c03e795ce338f01707ab0548ad9558347779e858

to amanda-3.3.9 now

Works now with samba-4.2.11 : solved for me

using smbclient-4.x

[Stefan G. Weichinger]

remember amanda-3.3.9 using a recent smbclient?

I get:

smbclient: Error reading password from file descriptor 3: empty password

Has anyone found a workaround (aside from downgrading samba)?
Is that fixed in 3.4?