thanks for the info. your case looks like a duplicate of bug #62831, which is fixed in feisty now.
dosfsck -n won't change anything on the partition, so only the test run shouldn't have deleted your file, however the normal boot sequence might have, in case you didn't disable file checking in /etc/fstab. You might be able to get it back with a run of win32's scandisk (probably renamed then).
The duplicate bug #55121 still suggests that there might be more wrong in dosfstools, I'll look into this.
P.S.: I didn't get bug emails as well, was due to a bug in launchpad, which is fixed now.
Hi Kevin,
thanks for the info. your case looks like a duplicate of bug #62831, which is fixed in feisty now.
dosfsck -n won't change anything on the partition, so only the test run shouldn't have deleted your file, however the normal boot sequence might have, in case you didn't disable file checking in /etc/fstab. You might be able to get it back with a run of win32's scandisk (probably renamed then).
The duplicate bug #55121 still suggests that there might be more wrong in dosfstools, I'll look into this.
P.S.: I didn't get bug emails as well, was due to a bug in launchpad, which is fixed now.
Cheers,
Stefan.