From: Philippe De Muyter <phdm@macqel.be>
To: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC] vfat and Simon_&_Garfunkel-Wednesday_Morning,_3_a.m.
Date: Tue, 29 Sep 2009 12:25:59 +0200 [thread overview]
Message-ID: <20090929102559.GA4590@frolo.macqel> (raw)
In-Reply-To: <87vdj2ysk8.fsf@devron.myhome.or.jp>
Hi Ogawa,
On Tue, Sep 29, 2009 at 07:05:27PM +0900, OGAWA Hirofumi wrote:
> Philippe De Muyter <phdm@macqel.be> writes:
>
> > I have an IOMEGA home network hard disk that I can connect either by
> > ethernet (ftp or cifs) or by USB. Because of the ftp server mode
> > firmware, I must keep it formatted as a vfat filesystem.
> >
> > I have copied my music files on it using the ftp mode. Using the same
> > ftp mode, I can also retrieve my music files without problem, and
> > when I list them, they have the exact names that they had on my linux
> > ext3 partition.
> >
> > When I connected this disk via USB, now relying on the vfat module
> > of linux, there were some directories that I could not reread. The
> > common factor of these directories names is that they end with one or
> > more dots, e.g.
> >
> > Simon_&_Garfunkel-Wednesday_Morning,_3_a.m.
> >
> > If I issue the `ls' or `find' command, I get this strange message :
> >
> > find: ./Simon_&_Garfunkel-Wednesday_Morning,_3_a.m.: No such file or directory
> >
> > Adding printk's in `fat_search_long' revealed that on this disk, the
> > file/directory NAMES ENDING WITH DOTS ARE STORED WITH THEIR TRAILING DOTS.
> >
> > Here is a patch sketch that makes accessing my
> > Simon_&_Garfunkel-Wednesday_Morning,_3_a.m. directory possible, but I
> > don't know if storing long filenames ending with dot's should not also
> > be fixed.
>
> IIRC, Windows stripped the trailing ".". That filename can be read/used on
> Windows?
Sorry I don't use MS-Windows. I'll try to find someone who does.
But, risking repeating myself, the firmware of the IOMEGA disk (via
the ftp interface) presents the filenames with the trailing dots.
> If it can be read, I think we should consider to remove
> vfat_striptail_len() (at least for lookup path), more investigation
> would be needed though.
That's what my patch does actually. Maybe it should depend of the length
of the filename, though.
Thanks
Philippe
next prev parent reply other threads:[~2009-09-29 10:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-19 18:11 [PATCH] parport netmos 9845 & 9855 1P4S fixes Philippe De Muyter
2009-03-23 8:50 ` Philippe De Muyter
2009-03-23 13:21 ` christian pellegrin
2009-03-23 13:52 ` Philippe De Muyter
2009-03-23 14:00 ` Philippe De Muyter
2009-09-25 19:46 ` [PATCH RFC] vfat and Simon_&_Garfunkel-Wednesday_Morning,_3_a.m Philippe De Muyter
2009-09-29 10:05 ` OGAWA Hirofumi
2009-09-29 10:25 ` Philippe De Muyter [this message]
2009-09-29 22:43 ` Philippe De Muyter
2009-09-30 11:02 ` OGAWA Hirofumi
2009-09-30 22:19 ` Philippe De Muyter
2009-10-01 10:42 ` OGAWA Hirofumi
2010-02-08 9:39 ` [PATCH vfat] allow retrieving entries with trailing dots Philippe De Muyter
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=20090929102559.GA4590@frolo.macqel \
--to=phdm@macqel.be \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-kernel@vger.kernel.org \
/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