Re: Problem file

I don't see how this could be a Unison issue. You may certainly try
deleting the ar* and fp* files (keep a backup) but it should not make any
difference because this is not a corruption of any of those files.

I am not familiar with ntfs-3g, so can't help in debugging, but I would
start from that direction. I would recommend mounting the partition in
Windows and letting it fix any issues with the file system. Then mount
under Linux with a different NTFS driver (I don't know if any are available
in Ubuntu) and see if the problem re-appears. I can't help with any of this
but I'm sure there are people here who mount NTFS partitions under Linux
and could help.

On Tue, 20 Feb 2024 at 16:31, John Rose <[email protected]> wrote:

> Thanks, Tõivo.
>
> The concerned partition is mounted with the FSTAB entry:
>
> *UUID=0D350FB60D350FB6  /media/john/Data  ntfs-3g
> defaults,windows_names,big_writes,locale=fr_FR.utf8,uid=1000,gid=1000,fmask=0002,dmask=0002,x-gvfs-show
> 0 0*
>
> windows_names limits the characters in filenames to those accepted by
> Windows. I have thousands of files in this partition and dozens sync
> without problem, only one word-processing file (LibreOffice Writer) gives
> difficulties, and I can for the moment see nothing in either the filename,
> nor the permissions nor the content which could cause it. I prefer saving
> all my word-processing files with the doc extension to ensure compatibility
> for my Windows-user friends (certainly not docx which should never have
> been approved as an international standard competing commercially with
> open-source odt).
>
> Four ar.... files and four fp.... files were generated/modified by unison
> during this syncing, and one or more are obviously corrupted now (since the
> mysterious file shows up in unison even though no longer physically
> present. Can/should I delete some or all of these files and redo the
> archives to see the problem is solved?
>
> Best regards,
>
>     John
> Le 20/02/2024 à 12:01, Tõivo Leedjärv a écrit :
>
> Hi John,
>
> This is most likely caused by whatever filesystem driver you're using to
> mount NTFS.
>
> Unison does not create files like this. The error "Erreur d'entrée/sortie"
> (which I'm assuming is EIO) also directly points to the filesystem
> driver/FUSE/kernel/disk, not a problem with Unison.
>
> I'm sorry, I can't be more helpful as I don't know much about mounting
> NTFS under Linux.
>
>
> On Tue, 20 Feb 2024 at 11:42, John Rose <[email protected]> wrote:
>
>> Hello,
>>
>> I am using unison 2.53 under Ubuntu 22.04 LTS. Everything syncs OK except
>> one ntfs doc file which gives the error below (syncing with an ntfs
>> partition on an external SSD). There was one unison entry for the file *Requests
>> for articles.doc* which synced fine left to right and another file with
>> *.ntfs-3g-0000000001* added at the end of the filename with an X for
>> skipping. I had this same problem with this same file a couple of days ago.
>> I at that time created an new document and pasted in the content, then
>> deleted the original document and it synced fine, but the X for skipping
>> has now returned for the same file with *.ntfs-3g-0000000001* added at
>> the end of the filename. I rebooted and get the same error for this same
>> file. Both of the files (the original on both roots and the new one on the
>> external SSD) open normally, and have the normal permissions (read-write
>> for me and my group, read for others).
>>
>> The original file *Requests for articles.doc* is thus fine on both roots
>> and syncs, but on the external SSD another file was apparently been added
>> (by unison?) called *Requests for articles.doc.ntfs-3g-0000000001*. I
>> deleted this file and I still get it in the sync list with an X (even
>> though it is no longer present in either root).
>>
>> So it looks to me that the archives file has been corrupted. Why is this
>> happening and what to do?
>>
>> Thanks and best regards,
>>
>>     John
>>
>> --
>> ************
>>
>>                John B. Rose
>>                1 Bis rue des Châtre-Sacs
>>                92310 Sèvres, France
>>
>>                Email: [email protected]
>>
>> --
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>>
> --
> ************
>
>                John B. Rose
>                1 Bis rue des Châtre-Sacs
>                92310 Sèvres, France
>
>                Email: [email protected]
>
> --
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
>

-- 
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].