Hi Craig,
Thanks for your reply
On Wed, Sep 2, 2020 at 1:49 PM Craig Barratt via BackupPC-users <
backuppc-users@lists.sourceforge.net> wrote:
> The "tar" errors are from smbclient. Unfortunately the output format of
> smb messages have changed many times over the years. I'm happy to accept
> PRs for detecting additional errors it reports if someone wants to
> submit something.
>
OK, I'll try to send a PR with the details.
> As Jeff points out, rsync is a far better option. It has built in support
> for charset conversion, which is required for Windows machines since their
> file systems don't use utf-8.
>
> But that said smbclient should be able to do charset conversion. What
> settings do you have for "dos charset" and "unix charset" in your smb.conf
> on the backuppc server?
>
Exactly, that's what I read on the docs: "If you are using smbclient on a
WinXX machine, smbclient will convert to the "unix charset" setting in
smb.conf..." I've been playing with different settings for those two
smb.conf options, but didn't have luck so left them at their default value:
dos charset = CP850
unix charset = UTF-8
Just as a side note: an old Win2k8 32bit server seems to work. Just newer
ones (w2k10, w2k12 server, etc) show this behavior.
Craig
>
M
> On Wed, Sep 2, 2020 at 9:22 AM <backu...@kosowsky.org> wrote:
>
>> Mariano Aliaga wrote at about 11:34:55 -0300 on Wednesday, September 2,
>> 2020:
>> > Hi,
>> >
>> > On Wed, Sep 2, 2020 at 11:28 AM <backu...@kosowsky.org> wrote:
>> >
>> > > G.W. Haywood via BackupPC-users wrote at about 14:22:50 +0100 on
>> > > Wednesday, September 2, 2020:
>> > > > Hi there,
>> > > >
>> > > > On Wed, 2 Sep 2020, Mariano Aliaga wrote:
>> > > > > ...
>> > > > > tar:974 Fatal: Can't translate pathname './Ajuste Inflaci?n
>> > > A?o2019.xps' to UTF-8
>> > > > > ...
>> > > > > ... So I wonder if this is a known bug, it's smbclient,
>> backuppc,
>> > > > > tar or what? Is there some known workaround? I'd appreciate any
>> help
>> > > > > you could give.
>> > > >
>> > > > I think it's a message from 'tar'. (That's because that's what it
>> > > says. :)
>> > > >
>> > > > It's not what I'd call a bug, it's the unfortunate result of the
>> many
>> > > > changes to the capabilities of both utilties and filesystems over
>> the
>> > > > time that they've been in use. There can be ambiguities when
>> strings
>> > > > are translated between some character sets, and you really don't
>> want
>> > > > that kind of ambiguity in file names.
>> > > >
>> > > > What's your output from 'locale'?
>> > > >
>> > > > Just a stab in the dark but you might try UTF-16, as mentioned
>> here:
>> > > >
>> > > >
>> https://forums.freebsd.org/threads/tar-cant-translate-pathname.32262/
>> > > >
>> > > > Life was so simple when everything was done with 7-bit ASCII
>> codes...
>> > > >
>> > > > --
>> > > >
>> > > > 73,
>> > > > Ged.
>> > > >
>> > >
>> > > Agree with Ged... I have had similar issues with rsync over time
>> > > But two further items:
>> > > 1. Does the entire tar backup fail or does it just skip the offending
>> > > paths?
>> > >
>> >
>> > The entire (smb) backup fails.
>> That doesn't typically happen with rsync as it typically "skips" the
>> file.
>> What happens when you try to manually 'tar' the file?
>> Do you get the same error?
>> If you are tarring multiple files, does the entire manual tar fail?
>>
>> Is there any reason you can't use rsync?
>> It's typically faster, more robust, and more full-featured (e.g., it
>> can backup more file types along with ACLs & xattrs) whereas tar has
>> more limitations...
>> >
>> >
>> > > 2. (This one is for Craig) It would be good if the error summaries
>> > > could better reflect the errors encountered by the transport
>> > > method. In this case, tar has a 'fatal' error,
>> > > tar:974 Fatal: Can't translate pathname './Ajuste Inflación
>> Año
>> > > but the summary line says:
>> > > tarExtract: Done: 0 errors, 7 filesExist, 289563505 sizeExist,
>> > > 285326858 sizeExistComp, 7 filesTotal, 289563505 sizeTotal, 0
>> > > filesNew, 0 sizeNew, 0 sizeNewComp, 110 inodeLast
>> > >
>> > > It's never been clear to me which 'errors' get counted and which
>> > > don't...
>> > >
>> > >
>> > > _______________________________________________
>> > > BackupPC-users mailing list
>> > > BackupPC-users@lists.sourceforge.net
>> > > List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
>> > > Wiki: https://github.com/backuppc/backuppc/wiki
>> > > Project: https://backuppc.github.io/backuppc/
>> > >
>> > _______________________________________________
>> > BackupPC-users mailing list
>> > BackupPC-users@lists.sourceforge.net
>> > List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
>> > Wiki: https://github.com/backuppc/backuppc/wiki
>> > Project: https://backuppc.github.io/backuppc/
>>
>>
>> _______________________________________________
>> BackupPC-users mailing list
>> BackupPC-users@lists.sourceforge.net
>> List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
>> Wiki: https://github.com/backuppc/backuppc/wiki
>> Project: https://backuppc.github.io/backuppc/
>>
> _______________________________________________
> BackupPC-users mailing list
> BackupPC-users@lists.sourceforge.net
> List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
> Wiki: https://github.com/backuppc/backuppc/wiki
> Project: https://backuppc.github.io/backuppc/
>
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/
