Re: Unison sync not working

Quek Kim Chuah <[email protected]> writes:

> Thank you for the reply. I will reply in blue.

All my text is the same color because I'm reading in plain text!  But I
can tell what I wrote.
>
>  - where are you syncing to and from?
> I am syncing local folder "Downloads" in my Fedora 43 to another 128GB SA=
TA
> SSD install in the same pc. Also trying to sync to another external drive
> with 2 128GB SATA SSD installed in external ssd enclosure.

Then this is local sync, with only one unison running, and no ssh to a remo=
te.

>   - what version of unison (on both computers, if remote is involved)?
> Unison 2.53.7 (ocaml 5.3.0)

That's almost up to date.  2.53.8 was released in November.  Often I ask
people to upgrade but so far there are no hints that there is a problem
in .7 fixed in .8, that is relevant.

>   - the kinds of fileystems

Wow, but it sounds like ~/Downloads is on btrfs, and one of the
destinations is ext4 and some are FAT32.

>   - the error as text rather than an image
> I don't know what it means

I'm reading mail in plain text and I'm not seeing your images.  It's
likely that there are people on this list with vision issues.  I
generally expect things that are fundamentally to be text to be text,
not screenshots.  Someone else might be willing to help you based on
screenshots.

>   - the results of you trying to simplify by syncing locally, by
>     disabling the watcher, and by using the CLI, if you are using the
>     GUI.

> The syncing is done using Terminal, unison work && unison ~/Downloads
> /run/media/jq/128\ WESTERN && unison ~/Downloads /run/media/jq/128\ KINGS=
TO

That's good you are already using the command line without the watcher.

You are vastly far from havinng a reason to file an issue, but the
explanation of how to turn on debugging and get debug output should be
helpful to you

  https://urldefense.com/v3/__https://github.com/bcpierce00/unison/wiki/Rep=
orting-Bugs-and-Feature-Requests__;!!IBzWLUs!US68pFi_dkuOGh4tq9OebIfm4T_T1i=
Rjod9d9aHz-LOQENVTEBqqNpQobIRw-paZvQrv88JFo023vL2TTA$=20

You have not cut/pasted the text of what unison prints when you run it.
So I have no idea what's happening.

>   - what changed yesterday about your OS :-)
> Nothing change on the OS itself. I just went Gnome Disk Management to "Ed=
it
> Mount Options", turn off "User Session Defaults" to enable "Mount at syst=
em
> startup", then on "Identify As -
>
> That is all I have done =F0=9F=98=80.

So what happened when you undid this?  I don't expect that if you make
random changes that you don't understand, that nothing bad will happen.
Unison's sync/archve/etc. does not expect that structural changes will
happen to established roots.

Have you verified that you can read/write the filesystem on the other
disk?  Unison has no magic and just does regular system calls.

You should understand that FAT32 is a deficient filesystem, lacking user
identities and permissions compared to UNIX norms, and that mounting
FAT32 thus involves the OS making assumptions and accomodations.

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