Facundo, I agree, I'm pretty sure I also made the change to generate
FS_FILE_DELETED
when you rename in my patch, but it's been so long I can't remember exactly. I
guess that's
the only change you need to fix it then?
--
You received this bug notification because you are a member of Ubuntu
I have some more information about this problem. It's easy to trigger this bug
with the attached code.
They key is to rename a non-ignored file to an ignored file (like one that ends
with ~). The inotify processor
currently ignores this possibility so the rest of the state machine never
learns
By the way, lyx saves files by writing to a temp file and then renaming it to
the backup file, which ends with ~,
which explains why this happens so often with lyx.
--
Ubuntu One sync daemon continuously hashing
https://bugs.launchpad.net/bugs/580855
You received this bug notification because
This seems to be caused by a loop:
1. File gets created.
2. File gets written.
3. Metadata gets created.
4. File gets renamed.
5. Hash queue fails (file no longer there)
Step 5 causes the file to be re-sent to the hash queue, which
keeps failing as the file is gone. This create a file
