public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: The Peach <smartart@tiscali.it>
To: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Cc: linux-kernel@vger.kernel.org
Subject: Re: bug? VFAT copy problem
Date: Wed, 22 Nov 2006 23:21:24 +0100	[thread overview]
Message-ID: <20061122232124.09695d57@localhost> (raw)
In-Reply-To: <87zmaj1cpv.fsf@duaron.myhome.or.jp>

On Thu, 23 Nov 2006 04:51:56 +0900
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp> wrote:

> The both of patch and option should be needed. Because the following
> filename is not shortname, shortname option doesn't affect.
> 
> If you test shortname=winnt without patch, it should still show the
> problem of following filename, but it should be rare case though.
> 
> Can you test it?

unfortunately not, the files have been renamed and renaming them back I can't reproduce the magical effect they did before.
Now I will try to rescan for any kind of files with long names and see if with the option on and without the patch it will re-generate that kind of errors they gave me.
I must thank you a lot, maybe a bottle of wine will do it ;)
anyway I didn't get why some files will copy with the right case and other don't. Was it a problem with the dentry table randomly failing in saving the filename? the shortname option in the Docs isn't well accurate in explaining the meaning of "Windows X rule for display/create", I will investigate after having checked the 32 GB of files. thanks again.

-- 
Matteo 'Peach' Pescarin

ICQ UIN = 71110111
Jabber ID = smartart@unstable.nl
Web Site = http://www.smartart.it
GeCHI = http://www.gechi.it

  reply	other threads:[~2006-11-22 22:21 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-20 15:42 bug? VFAT copy problem The Peach
2006-11-20 17:32 ` OGAWA Hirofumi
2006-11-20 17:49   ` The Peach
2006-11-21 15:46     ` OGAWA Hirofumi
2006-11-22 14:02       ` [OT] " Sergio Monteiro Basto
2006-11-22 14:53         ` DervishD
2006-11-22 16:07           ` OGAWA Hirofumi
2006-11-22 18:21             ` DervishD
2006-11-23  0:56           ` Sergio Monteiro Basto
2006-11-23  9:13             ` DervishD
2006-11-23 11:26               ` The Peach
2006-11-23 15:43                 ` DervishD
2006-11-23 11:38               ` OGAWA Hirofumi
2006-11-23 11:50                 ` [OT] " Renato S. Yamane
2006-11-23 11:59                   ` OGAWA Hirofumi
2006-11-23 19:21                     ` Sergio Monteiro Basto
2006-11-22 15:30       ` The Peach
2006-11-22 16:15         ` OGAWA Hirofumi
2006-11-22 19:10           ` The Peach
2006-11-22 19:29             ` OGAWA Hirofumi
2006-11-22 19:38               ` The Peach
2006-11-22 19:51                 ` OGAWA Hirofumi
2006-11-22 22:21                   ` The Peach [this message]
2006-11-23 11:32                     ` OGAWA Hirofumi
2006-11-23  3:50       ` junjiec
2006-11-23 11:08         ` OGAWA Hirofumi

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=20061122232124.09695d57@localhost \
    --to=smartart@tiscali.it \
    --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