Re: Most compatible way to prepare USB stick
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, Oct 20, 2016 at 11:36:57PM +0100, Mr Smiley wrote:
> I have a satellite receiver that records to an external USB device
> which has to be formatted to Fat32. Every few weeks it says it can't
> find a compatible fat32 device. If I connect the usb device (either
> usb stick or external hard disk) to a windows machine and copy any
> file to the same folder, so it creates a xxxxxcopy1.xxx and then
> delete that same file. Reconnecting the device to the receiver it
> sees the device as a valid fat32 and everybody’s happy.
>
> If i do the same on my debian system, create say using touch and
> then delete, the receiver still refuses to see it. Only a windows
> machine can get it working again.
>
> The closest I’ve come to an answer is that Linux can't fully use the
> windows method of long file names properly.
Another possible explanation is that something is corrupting the
file system. Since FAT (especially on removable devices) is very
prone to corruption (people pull out the medium all the time without
giving the file system drivers a chance to flush their buffers),
Windows has evolved a strategy to do a file system repair behind
the scenes whenever things get modified.
That means that from time to time a file or three might disappear
silently, but Windows users are a hardy species, capable of taking
a fair amount of abuse.
Have you ever, under Linux, tried fsck.vfat?
> So there is a major difference in the way Linux and windows handle
> file naming. The file names look the same on both Linux and windows,
> but behind the scenes they are not.
You'd need more evidence to convince me of that. Among other things,
fat (and even the Rube-Goldbergian vfat) are stable since long, and
(by current standards) relatively simple.
regards
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlgJ06gACgkQBcgs9XrR2kbBXwCfUUysF7qXEtRRrDzmqJpHas14
iWEAn3P2RL2fx4YGQNiFaksN0cdZ+1I9
=j/Sk
-----END PGP SIGNATURE-----
Reply to: