public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: "Thomas Weißschuh" <thomas@t-8ch.de>
Cc: tjcw@cantab.net, linux-kernel@vger.kernel.org
Subject: Re: vfat file system does not allow a space at the end of a directory name
Date: Mon, 31 Jul 2023 10:26:01 -0400	[thread overview]
Message-ID: <20230731142601.GA903325@mit.edu> (raw)
In-Reply-To: <196f7191-5820-4480-99d3-e7ffc66e9c98@t-8ch.de>

On Mon, Jul 31, 2023 at 07:55:39AM +0200, Thomas Weißschuh wrote:
> On 2023-07-30 23:33:03+0100, Chris Ward wrote:
> > I had a zip file (from downloading pictures from Google Photos) where
> > some of the directory names had a space at the end. This unzipped fine
> > on an ext4 file system, but gave errors when unpacking onto a USB key
> > which had a FAT file system.
>
> AFAIK this is a limitation in the FAT filesystem itself.
> 
> The problem is that FAT stores filenames in fixed width fields.
> Unused space in these fields is filled with ' '.
> This means that storing "foo", "foo " or "foo ". would all result in the
> exact same result and it will be impossible to figure out the correct
> one afterwards.

Yeah, I'd argue that this is a misfeature in Google Photos; its
product manager should strongly consider stripping trailing spaces
from picture titles.

Disclosure: I work for Google but not anywhere near the Google Photos
product team, and this is my own opinion not Google's.  Feel free to
file product feedback in the Google Photos app, though.  :-)

						- Ted

      reply	other threads:[~2023-07-31 14:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-30 22:33 vfat file system does not allow a space at the end of a directory name Chris Ward
2023-07-31  5:55 ` Thomas Weißschuh
2023-07-31 14:26   ` Theodore Ts'o [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230731142601.GA903325@mit.edu \
    --to=tytso@mit.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thomas@t-8ch.de \
    --cc=tjcw@cantab.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox