[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Can't translate pathname 'x/y' to UTF-8

To: Chris Webb <chris@arachsys.com>
Subject: Re: Can't translate pathname 'x/y' to UTF-8
From: Colin Percival <cperciva@tarsnap.com>
Date: Wed, 30 Nov 2011 10:42:00 -0800
Cc: The big chief <Jacques.Piguet@bluewin.ch>, tarsnap-users@tarsnap.com
In-reply-to: <20111130183505.GC14986@arachsys.com>
References: <4ED547AD.8020105@bluewin.ch> <4ED674D4.5080805@tarsnap.com> <20111130183505.GC14986@arachsys.com>

On 11/30/11 10:35, Chris Webb wrote:
> Colin Percival <cperciva@tarsnap.com> writes:
>> Depending on how your system handles non-ASCII characters and locales Tarsnap
>> sometimes fails to convert characters to UTF-8.  This seems to be an issue on
>> Linux systems in particular.  Tarsnap is storing the path name "raw" rather
>> than as UTF-8 as a result.
> 
> Is there an easy way to force tarsnap to store all file names as literal
> byte-sequences and not attempt any character-set conversion on both backup
> and restore? It'd be a nice option if not.

I suspect that
# env LC_ALL=C tarsnap ...
will do that.

-- 
Colin Percival
Security Officer, FreeBSD | freebsd.org | The power to serve
Founder / author, Tarsnap | tarsnap.com | Online backups for the truly paranoid

References:
- Can't translate pathname 'x/y' to UTF-8
  - From: The big chief <Jacques.Piguet@bluewin.ch>
- Re: Can't translate pathname 'x/y' to UTF-8
  - From: Colin Percival <cperciva@tarsnap.com>
- Re: Can't translate pathname 'x/y' to UTF-8
  - From: Chris Webb <chris@arachsys.com>

Prev by Date: [patch] nodump breakage on linux
Next by Date: Intermittent network failures normal?
Previous by thread: Re: Can't translate pathname 'x/y' to UTF-8
Next by thread: [patch] nodump breakage on linux
Index(es):
- Date
- Thread