| 1 |
On Thu, 19 Nov 2009 04:30:46 +0100, Jesús Guerrero wrote: |
| 2 |
|
| 3 |
> Even if you didn't, in my understanding, all that could cause (normally) |
| 4 |
> is a broken file system. The effects will usually depends on whatever |
| 5 |
> was happening at the moment, and at the fs you are using. |
| 6 |
|
| 7 |
As he was only reading from the drive, I doubt he could have corrupted |
| 8 |
the filesystem, let alone the partition table. |
| 9 |
|
| 10 |
> Some mount |
| 11 |
> options can influence this as well. To palliate the effects of a |
| 12 |
> catastrophic plug off without having umounted before you can use the |
| 13 |
> -osync mount option, which will enable synchronous writes (making your |
| 14 |
> device seems slower, because writes will no longer be deferred/cached |
| 15 |
> for a later oportunity). |
| 16 |
|
| 17 |
However, these increase writes to the device, particularly to the FAT, |
| 18 |
shortening the life of the drive. |
| 19 |
|
| 20 |
I suspect you did nothing wrong and that the problem is either a |
| 21 |
coincidental hardware failure or something the owner did to the stick |
| 22 |
after you returned it. Convincing the owner of that is another matter. |
| 23 |
|
| 24 |
|
| 25 |
-- |
| 26 |
Neil Bothwick |
| 27 |
|
| 28 |
Of all the people I've met you're certainly one of them |
Archives