[Bug 580855] Re: Ubuntu One sync daemon continuously hashing
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/580855 Title: Ubuntu One sync daemon continuously hashing -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 580855] Re: Ubuntu One sync daemon continuously hashing
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 the original file has gone away. I updated my branch to make the inotify processor synthesize a delete event for this case. I left the check I put in as it just seems safer. I was, for example, able to trigger the bug by setting the file to be totally unreadable after touching it. ** Attachment added: annoy the sync daemon by renaming a non-ignored file to an ignored file https://bugs.launchpad.net/ubuntu/+source/ubuntuone-client/+bug/580855/+attachment/1496976/+files/annoy.py -- Ubuntu One sync daemon continuously hashing https://bugs.launchpad.net/bugs/580855 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 580855] Re: Ubuntu One sync daemon continuously hashing
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 you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 580855] Re: Ubuntu One sync daemon continuously hashing
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 and then rename pattern is pretty typical of apps that save documents. I got it to happen using rsync, which also uses temporary files which are then renamed. One way to fix it is to check that the file is still accessible before re-attmempting the hash. I have small patch here, sans tests, which at least fixes it for me. https://code.launchpad.net/~dave-krondo/ubuntuone-client/lucid- updates-580855 -- Ubuntu One sync daemon continuously hashing https://bugs.launchpad.net/bugs/580855 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
