From: "Andrea Pusceddu" <a.pusceddu@remosa-valves.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [USB-STORAGE] Repeatable lost files problem
Date: Thu, 15 Jan 2004 12:30:47 +0100 [thread overview]
Message-ID: <400687F7.20318.60C885D@localhost> (raw)
In-Reply-To: <20040114195507.GA1533@one-eyed-alien.net>
[....]
> I'm guessing that the player is attempting to perform
> some sort of special test on the data. If the file doesn't conform, or if
> the filesystem is 'different' in some way, it obliterates the offending
> material.
[....]
Dear Matthew,
thank you for your reply. One thing I really can't understand is HOW can a file copied
from linux be different from the same file copied from Windows, once it has been
"wrote" into same the usb drive; it's really odd, isn't it? It seems kind of FUD to
discourage Linux users :)
If we were able to find out that difference it could be possible to "emulate" the way
windows flags the copied files (just guessing, I'm not a kernel hacker..)
If you believe that this odd behavior is worth a further investigation, I'm available for
your tests, I could run diagnostic tools, try out new drivers, and so on.
The MP3 player supports the firmware upgrading, but in the producer web site that
particular device is not listed.
It's annoying, honestly only Windows support was mentioned in the player handbook so
I knew I could meet problems with my Debian box, but once I saw the chipset was
supported, and I mounted in on /dev/sda, and I downloaded my data from it... :)
Do you think that it's worth to try out with the 2.6 Kernel, or there aren't any important
changes related to usb-storage that may help?
Thank you again for the great work you are doing with usb-storage, and for the time you
spent reading my messages.
Best Regards,
Andrea
prev parent reply other threads:[~2004-01-15 11:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-14 9:13 [USB-STORAGE] Repeatable lost files problem Andrea Pusceddu
2004-01-14 19:55 ` Matthew Dharm
2004-01-15 11:30 ` Andrea Pusceddu [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=400687F7.20318.60C885D@localhost \
--to=a.pusceddu@remosa-valves.com \
--cc=callmeishmael@tiscali.it \
--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