On 01/26/16 02:22 PM, Gunther Nitzsche wrote: > Am Montag, 25. Januar 2016 18:48:47 UTC+1 schrieb marco.van.wieringen: >> On 01/25/16 05:52 PM, Gunther Nitzsche wrote: >>> >>> I recently upgraded bareos from 14.2.2 to 15.2.2. Since that time >>> my NDMP-smtape backups (from a NetApp-device) fails with the >>> blocksize error. > >>> >> Correct NDMP blocksize has its own keyword in the client definition e.g. >> NdmpBlockSize. > .. >> >> #define SMTAPE_MIN_BLOCKSIZE 4096 /* 4 Kb */ >> #define SMTAPE_MAX_BLOCKSIZE 262144 /* 256 Kb */ > > Thanks for replying. Backup is running again with Option > NdmpBlockSize = 262144 in the client-ressource. Thanks for that. > In the status-view I cannot see any difference, so I don't know > what the system really did.. Anyway, it is running :) (hopefully > a restore would work also..) That is pretty much up to the NetAPP as we deliver the data back in the way it was provided so the blocksize is more in what size the storage box chunks its data.
> > btw: when doing an "est <client>" targeting the netapp-ressource, bareos > crashes. I know that the command doesn't make much sense on a filer (no > filedaemon), but a crash should not happen. In bareos.log I see a password- > error: > Its also not a crash but an ASSERT which is exactly what it supposed to do as you try running a command that is only implemented for a native client. > 26-Jan 14:17 <server>-dir: ERROR in authenticate.c:294 Failed ASSERT: > client->password.encoding == p_encoding_md5 > > which is strange, since the backup is running, ndmp-passwords do match. > What it complains about is that the client is using the wrong password encoding e.g. the way the password is stored after it is parsed by the config engine. For NDMP that is stored in clear text as we need to be able to allow clear and md5 authentication. A native client stores the password with md5 encoding as we never need it in a clear format. So its more a problem that we haven't added everywhere stop gaps against users doing things that are not supported. That is also the idea about asserts e.g. test for unwanted/wanted settings. But the estimate problem is fixed as part of bug 601 since last Friday. -- Marco van Wieringen [email protected] Bareos GmbH & Co. KG Phone: +49-221-63069389 http://www.bareos.com Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646 Komplementär: Bareos Verwaltungs-GmbH Geschäftsführer: Stephan Dühr, M. Außendorf, J. Steffens, P. Storz, M. v. Wieringen -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
