Date: Tue, 29 Jan 2019 15:28:50 -0500 From: "James B. Byrne" <byrnejb@harte-lyne.ca> To: "Polytropon" <freebsd@edvax.de> Cc: "James B. Byrne via freebsd-questions" <freebsd-questions@freebsd.org> Subject: Re: RSYNC changes file name Message-ID: <10a14c28507feee71572a2573d319fc3.squirrel@webmail.harte-lyne.ca> In-Reply-To: <20190129204033.7312742f.freebsd@edvax.de> References: <9aaa35912b122e88e667e7516ba6a865.squirrel@webmail.harte-lyne.ca> <20190129204033.7312742f.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Thank you.
Gpart reports the file system is type 12 which I believe is some
variant of FAT. MS Windows does not permit file names ending in
either a dot or a space. The filesystem silently truncates the
offending character.
I discovered this by trying to touch a file named 'seventeen.' which
showed up as 'seventeen' instead.
It would have been nice to have that munging reported.
On Tue, January 29, 2019 14:40, Polytropon wrote:
> On Tue, 29 Jan 2019 09:36:47 -0500, James B. Byrne via
> freebsd-questions wrote:
>> So the source file is recognised as having a trailing dot but the
>> resulting target file does not have it.
>
> What filesystems are involved here? Ssource is UFS or ZFS,
> I assume, but destination? Maybe it's a filesystem _name_
> restriction issue that leads to a silent automatic conversion
> (here: data loss)? Just a WAG... ;-)
>
>
>
--
*** e-Mail is NOT a SECURE channel ***
Do NOT transmit sensitive data via e-Mail
Do NOT open attachments nor follow links sent by e-Mail
James B. Byrne mailto:ByrneJB@Harte-Lyne.ca
Harte & Lyne Limited http://www.harte-lyne.ca
9 Brockley Drive vox: +1 905 561 1241
Hamilton, Ontario fax: +1 905 561 0757
Canada L8E 3C3
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?10a14c28507feee71572a2573d319fc3.squirrel>