[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [MiNT] mv does delete when fail of fat (was: 1-18-cur trunk stability issues)
remember that a deleted file simply has the first char of &hE5
It may also be that and invalid char may have been placed in the
filename (somehow?). either way and fs chack will not show these
problems, just verifies fat pointers (to de/allocated data)
I have an EasyMiNT setup for ARAnyM with a FAT boot drive, I will give
your issue some testing..
We have had issues with FAT fs under mint reported on and off since
1.17 (usually also desktop related), so there may be a further
underlying issue that is the basis for these problems. I'll see if I
can find the 2 seperate threads I thinking of (one in the within last
12 months, another about 2 years ago - those were something to do with
folder names)
Cheers
Paul
On Wed, Nov 30, 2011 at 10:12 AM, Mark Duckworth
<mduckworth@atari-source.org> wrote:
> I had a backup so that is no big deal. I did do an fs check after this happened and there were no errors suggesting that nothing untoward happened. I think what happened is that it passed some sanity check internal to the mv program since they were different filenames and then fat truncated the dest filename which caused an error. The issue is whether or not this is fully correct or is a situation which should be handled. I imagine there are a few data loss scenarios that could play out moving data from ext2 or vfat to fat 8.3 filesystems.
>
> Thanks,
> Mark
>
>
> On Nov 29, 2011, at 4:07 PM, Paul Wratt wrote:
>
>> I suggest:
>> 1) do some tests (with dummy files of coarse)
>> 2) check drive with "undelete tool" as it may still be there
>> 3) confirm on another machine/distro (Gentoo) (someone else maybe?)
>>
>> If you can verify it deletes on fail on other partition type, that
>> would be bonus
>>
>> That will at least isolate the issue (it may just be the mint fat driver)
>