gcmm corrupting fat32 partition

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Run gcmm
2.Select usb as destination
3.Backup something
4.Have a damaged partition

What is the expected output? What do you see instead?
The saves should be saved to the first fat32 partition of my two(one fat32, the 
other ntfs).
Instead my first partition is damaged and displays weird symbols for its 
content that has wrong file information too, also the size of the whole fat32 
partition is now wrong.

What version of the product are you using? On what operating system?
Latest, 1.4c

Please provide any additional information below.
-

Original issue reported on code.google.com by VincenzP...@googlemail.com on 10 Jul 2014 at 7:33

[GoogleCodeExporter]

I'm very sorry, I hope you didn't lose too much data (or anything important).

SD and USB FAT32 mounting is handled by libfat, so the issue isn't directly 
related with GCMM.

When I coded usb support was only because it was essentially the same as the SD 
card/sd geckko and very little work was needed, but I had pendrives in mind, 
not partitioned hard disks.

Still, libfat should work with the first partition of the device and ignore the 
others. I'll try to reproduce your problem to discard it being your usb device 
fault, if it happens with my devices too I'll recompile with the latest 
libraries and see if the problem persists.

Aside from that there's little I can do apart from recommending using an SD 
card or a pendrive instead of a hard disk drive.

Original comment by sulokuTDCmago@gmail.com on 10 Jul 2014 at 11:20

[GoogleCodeExporter]

I made couple of tests and gcmm didn't corrupt anything at my side. I tested 
with two devices with the same configuration as you (1 fat32 and 1 ntfs 
partion). So the problem is either with your device, plain bad luck or there's 
something else that led to the corruption of your filesystem and partition 
table, but as I said that has more to do with libfat tham gcmm.

Original comment by sulokuTDCmago@gmail.com on 12 Jul 2014 at 5:14

[GoogleCodeExporter]

OK, it's alright. I didn't loose any really important data, but it was still 
frustrating. Besides that I previously dumped to a SD card and in the same run 
dumped to the HDD I don't know any additional influencing factors too, but I 
guess it really was simply bad luck. Sorry if I made an issue report that 
wasn't even your fault and made you do some extra work because of something 
that wasn't even associated with your source code.

Original comment by VincenzP...@googlemail.com on 12 Jul 2014 at 5:28

[GoogleCodeExporter]

Don't worry, it could still be my fault, but since this is the first report 
I've ever heard of a corruption, but it is also true that most people might use 
the SD card, but being the same code for both devices is puzzling.

I hope you don't encounter the same problem again.

Original comment by sulokuTDCmago@gmail.com on 14 Jul 2014 at 10:05

• Changed state: Invalid