Activity log for bug #702309

Date Who What changed Old value New value Message
2011-01-13 11:29:34 Otto Kekäläinen bug added bug
2011-01-13 11:30:42 Otto Kekäläinen tags apport-collected
2011-01-13 11:30:46 Otto Kekäläinen description My machine ran out of hard drive space and I noticed that I had 1343 files (22 GB in total size) in /tmp. All of the files were named like tmpXXXXXX, e.g. tmpzwFV1p. Running lsof reviled that the the files were created (and kept open) by the process "ubuntuone". Background: I'm running Lucid with all updates and I have a paid 4x20GB U1 account with 20GB+ of stuff and I recently added a folder (~/Kuvat) with 40 GB of files that has uploaded only partially. Account registered to otto at sange.fi. Analysis: I restarted my machine (and Linux automatically cleans up the /tmp directory) and documented what happens: 1. When the computer starts, the contents of /tmp is normal. 2. When the computer is on, u1sdtool -s starts with State: LOCAL_RESCAN 3. Then u1sdtool -s shows State: SERVER_RESCAN 4. Then u1sdtool -s shows State: QUEUE_MANAGER 5. At this point just one file is created /tmp/tmpCb3SoN. When the state is QUEUE_MANAGER, uploading should happen and u1sdtool --waiting-content lists 6000+ files, but there is no outgoing network traffic. 6. After a few hours the uploading finally starts. Outgoing network traffic is at level 120-150 KB/s. 7. At the same time more and more files start to appear in /tmp directory. See how it grows by looking at http://otto.kekalainen.net/u1-bugs/tmp-files0.txt, http://otto.kekalainen.net/u1-bugs/tmp-files1.txt, http://otto.kekalainen.net/u1-bugs/tmp-files2.txt and http://otto.kekalainen.net/u1-bugs/tmp-files3.txt. 8. lsof | grep tmp/tmp proves the files are opened by process ubuntuone. See how it grows in http://otto.kekalainen.net/u1-bugs/lsof01.txt and http://otto.kekalainen.net/u1-bugs/lsof02.txt 9. Finally the filesystem gets full. Listing http://otto.kekalainen.net/u1-bugs/filesystem-full.txt reveals also the file sizes. They seem to match the file size of files in ~/Kuvat. 10. Now u1sdtool --waiting-content shows only one file at the time: otto@shuttle:/tmp$ u1sdtool --waiting-content operation='Upload' node_id='81ca5875-91a3-4b49-827f-48aad081f1fb' share_id='492ae22d-006c-4044-b457-e0a6b6a9ceca' path='/home/otto/Kuvat/2010-marraskuu/IMG_3590.JPG' otto@shuttle:/tmp$ u1sdtool --waiting-content operation='Upload' node_id='6c1e799d-4584-4164-9c62-262053688138' share_id='492ae22d-006c-4044-b457-e0a6b6a9ceca' path='/home/otto/Kuvat/Sekalaista/Joulu 2008/00115.jpg' otto@shuttle:/tmp$ u1sdtool --waiting-content operation='Upload' node_id='ae9f7fd2-bff6-48d9-8508-0a8e6e0b831b' share_id='492ae22d-006c-4044-b457-e0a6b6a9ceca' path='/home/otto/Kuvat/Sekalaista/Pariisi 2009/IMG_8016.JPG' 11. However when I open at one.ubuntu.com > My Storage / ~/Kuvat / Sekalaista / Joulu 2008, there is no file 00115.jpg 12. Network traffic shows that uploading is happening. 13. Some other programs start to bug when the filesystem is full. Computer becomes unusable. My machine ran out of hard drive space and I noticed that I had 1343 files (22 GB in total size) in /tmp. All of the files were named like tmpXXXXXX, e.g. tmpzwFV1p. Running lsof reviled that the the files were created (and kept open) by the process "ubuntuone". Background: I'm running Lucid with all updates and I have a paid 4x20GB U1 account with 20GB+ of stuff and I recently added a folder (~/Kuvat) with 40 GB of files that has uploaded only partially. Account registered to otto at sange.fi. Analysis: I restarted my machine (and Linux automatically cleans up the /tmp directory) and documented what happens: 1. When the computer starts, the contents of /tmp is normal. 2. When the computer is on, u1sdtool -s starts with State: LOCAL_RESCAN 3. Then u1sdtool -s shows State: SERVER_RESCAN 4. Then u1sdtool -s shows State: QUEUE_MANAGER 5. At this point just one file is created /tmp/tmpCb3SoN. When the state is QUEUE_MANAGER, uploading should happen and u1sdtool --waiting-content lists 6000+ files, but there is no outgoing network traffic. 6. After a few hours the uploading finally starts. Outgoing network traffic is at level 120-150 KB/s. 7. At the same time more and more files start to appear in /tmp directory. See how it grows by looking at http://otto.kekalainen.net/u1-bugs/tmp-files0.txt, http://otto.kekalainen.net/u1-bugs/tmp-files1.txt, http://otto.kekalainen.net/u1-bugs/tmp-files2.txt and http://otto.kekalainen.net/u1-bugs/tmp-files3.txt. 8. lsof | grep tmp/tmp proves the files are opened by process ubuntuone. See how it grows in http://otto.kekalainen.net/u1-bugs/lsof01.txt and http://otto.kekalainen.net/u1-bugs/lsof02.txt 9. Finally the filesystem gets full. Listing http://otto.kekalainen.net/u1-bugs/filesystem-full.txt reveals also the file sizes. They seem to match the file size of files in ~/Kuvat. 10. Now u1sdtool --waiting-content shows only one file at the time: otto@shuttle:/tmp$ u1sdtool --waiting-content operation='Upload' node_id='81ca5875-91a3-4b49-827f-48aad081f1fb' share_id='492ae22d-006c-4044-b457-e0a6b6a9ceca' path='/home/otto/Kuvat/2010-marraskuu/IMG_3590.JPG' otto@shuttle:/tmp$ u1sdtool --waiting-content operation='Upload' node_id='6c1e799d-4584-4164-9c62-262053688138' share_id='492ae22d-006c-4044-b457-e0a6b6a9ceca' path='/home/otto/Kuvat/Sekalaista/Joulu 2008/00115.jpg' otto@shuttle:/tmp$ u1sdtool --waiting-content operation='Upload' node_id='ae9f7fd2-bff6-48d9-8508-0a8e6e0b831b' share_id='492ae22d-006c-4044-b457-e0a6b6a9ceca' path='/home/otto/Kuvat/Sekalaista/Pariisi 2009/IMG_8016.JPG' 11. However when I open at one.ubuntu.com > My Storage / ~/Kuvat / Sekalaista / Joulu 2008, there is no file 00115.jpg 12. Network traffic shows that uploading is happening. 13. Some other programs start to bug when the filesystem is full. Computer becomes unusable. --- Architecture: amd64 DistroRelease: Ubuntu 10.04 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100223.2) Package: ubuntuone-client 1.2.2-0ubuntu2 PackageArchitecture: all ProcEnviron: LANG=fi_FI.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-27.49-generic 2.6.32.26+drm33.12 Tags: lucid UbuntuOneUserSyncdaemonConfig: [bandwidth_throttling] read_limit = 2097152 write_limit = 2097152 on = False Uname: Linux 2.6.32-27-generic x86_64 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
2011-01-13 11:30:50 Otto Kekäläinen attachment added Dependencies.txt https://bugs.edge.launchpad.net/bugs/702309/+attachment/1792447/+files/Dependencies.txt
2011-01-13 11:30:54 Otto Kekäläinen attachment added UbuntuOneClientPackages.txt https://bugs.edge.launchpad.net/bugs/702309/+attachment/1792448/+files/UbuntuOneClientPackages.txt
2011-01-13 11:31:00 Otto Kekäläinen attachment added UbuntuOneOAuthLoginLog.txt https://bugs.edge.launchpad.net/bugs/702309/+attachment/1792449/+files/UbuntuOneOAuthLoginLog.txt
2011-01-13 11:31:05 Otto Kekäläinen attachment added UbuntuOnePreferencesLog.txt https://bugs.edge.launchpad.net/bugs/702309/+attachment/1792450/+files/UbuntuOnePreferencesLog.txt
2011-01-13 11:31:15 Otto Kekäläinen attachment added UbuntuOneSyncdaemonExceptionsLog.txt https://bugs.edge.launchpad.net/bugs/702309/+attachment/1792451/+files/UbuntuOneSyncdaemonExceptionsLog.txt
2011-01-13 11:32:52 Otto Kekäläinen description My machine ran out of hard drive space and I noticed that I had 1343 files (22 GB in total size) in /tmp. All of the files were named like tmpXXXXXX, e.g. tmpzwFV1p. Running lsof reviled that the the files were created (and kept open) by the process "ubuntuone". Background: I'm running Lucid with all updates and I have a paid 4x20GB U1 account with 20GB+ of stuff and I recently added a folder (~/Kuvat) with 40 GB of files that has uploaded only partially. Account registered to otto at sange.fi. Analysis: I restarted my machine (and Linux automatically cleans up the /tmp directory) and documented what happens: 1. When the computer starts, the contents of /tmp is normal. 2. When the computer is on, u1sdtool -s starts with State: LOCAL_RESCAN 3. Then u1sdtool -s shows State: SERVER_RESCAN 4. Then u1sdtool -s shows State: QUEUE_MANAGER 5. At this point just one file is created /tmp/tmpCb3SoN. When the state is QUEUE_MANAGER, uploading should happen and u1sdtool --waiting-content lists 6000+ files, but there is no outgoing network traffic. 6. After a few hours the uploading finally starts. Outgoing network traffic is at level 120-150 KB/s. 7. At the same time more and more files start to appear in /tmp directory. See how it grows by looking at http://otto.kekalainen.net/u1-bugs/tmp-files0.txt, http://otto.kekalainen.net/u1-bugs/tmp-files1.txt, http://otto.kekalainen.net/u1-bugs/tmp-files2.txt and http://otto.kekalainen.net/u1-bugs/tmp-files3.txt. 8. lsof | grep tmp/tmp proves the files are opened by process ubuntuone. See how it grows in http://otto.kekalainen.net/u1-bugs/lsof01.txt and http://otto.kekalainen.net/u1-bugs/lsof02.txt 9. Finally the filesystem gets full. Listing http://otto.kekalainen.net/u1-bugs/filesystem-full.txt reveals also the file sizes. They seem to match the file size of files in ~/Kuvat. 10. Now u1sdtool --waiting-content shows only one file at the time: otto@shuttle:/tmp$ u1sdtool --waiting-content operation='Upload' node_id='81ca5875-91a3-4b49-827f-48aad081f1fb' share_id='492ae22d-006c-4044-b457-e0a6b6a9ceca' path='/home/otto/Kuvat/2010-marraskuu/IMG_3590.JPG' otto@shuttle:/tmp$ u1sdtool --waiting-content operation='Upload' node_id='6c1e799d-4584-4164-9c62-262053688138' share_id='492ae22d-006c-4044-b457-e0a6b6a9ceca' path='/home/otto/Kuvat/Sekalaista/Joulu 2008/00115.jpg' otto@shuttle:/tmp$ u1sdtool --waiting-content operation='Upload' node_id='ae9f7fd2-bff6-48d9-8508-0a8e6e0b831b' share_id='492ae22d-006c-4044-b457-e0a6b6a9ceca' path='/home/otto/Kuvat/Sekalaista/Pariisi 2009/IMG_8016.JPG' 11. However when I open at one.ubuntu.com > My Storage / ~/Kuvat / Sekalaista / Joulu 2008, there is no file 00115.jpg 12. Network traffic shows that uploading is happening. 13. Some other programs start to bug when the filesystem is full. Computer becomes unusable. --- Architecture: amd64 DistroRelease: Ubuntu 10.04 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100223.2) Package: ubuntuone-client 1.2.2-0ubuntu2 PackageArchitecture: all ProcEnviron: LANG=fi_FI.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-27.49-generic 2.6.32.26+drm33.12 Tags: lucid UbuntuOneUserSyncdaemonConfig: [bandwidth_throttling] read_limit = 2097152 write_limit = 2097152 on = False Uname: Linux 2.6.32-27-generic x86_64 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare My machine ran out of hard drive space and I noticed that I had 1343 files (22 GB in total size) in /tmp. All of the files were named like tmpXXXXXX, e.g. tmpzwFV1p. Running lsof reviled that the the files were created (and kept open) by the process "ubuntuone". Background: I'm running Lucid with all updates and I have a paid 4x20GB U1 account with 20GB+ of stuff and I recently added a folder (~/Kuvat) with 40 GB of files that has uploaded only partially. Account registered to otto at sange.fi. Analysis: I restarted my machine (and Linux automatically cleans up the /tmp directory) and documented what happens: 1. When the computer starts, the contents of /tmp is normal. 2. When the computer is on, u1sdtool -s starts with State: LOCAL_RESCAN 3. Then u1sdtool -s shows State: SERVER_RESCAN 4. Then u1sdtool -s shows State: QUEUE_MANAGER 5. At this point just one file is created /tmp/tmpCb3SoN. When the state is QUEUE_MANAGER, uploading should happen and u1sdtool --waiting-content lists 6000+ files, but there is no outgoing network traffic. 6. After a few hours the uploading finally starts. Outgoing network traffic is at level 120-150 KB/s. 7. At the same time more and more files start to appear in /tmp directory. See how it grows by looking at http://otto.kekalainen.net/u1-bugs/tmp-files0.txt, http://otto.kekalainen.net/u1-bugs/tmp-files1.txt, http://otto.kekalainen.net/u1-bugs/tmp-files2.txt and http://otto.kekalainen.net/u1-bugs/tmp-files3.txt. 8. lsof | grep tmp/tmp proves the files are opened by process ubuntuone. See how it grows in http://otto.kekalainen.net/u1-bugs/lsof01.txt and http://otto.kekalainen.net/u1-bugs/lsof02.txt 9. Finally the filesystem gets full. Listing http://otto.kekalainen.net/u1-bugs/filesystem-full.txt reveals also the file sizes. They seem to match the file size of files in ~/Kuvat. 10. Now u1sdtool --waiting-content shows only one file at the time: otto@shuttle:/tmp$ u1sdtool --waiting-content operation='Upload' node_id='81ca5875-91a3-4b49-827f-48aad081f1fb' share_id='492ae22d-006c-4044-b457-e0a6b6a9ceca' path='/home/otto/Kuvat/2010-marraskuu/IMG_3590.JPG' otto@shuttle:/tmp$ u1sdtool --waiting-content operation='Upload' node_id='6c1e799d-4584-4164-9c62-262053688138' share_id='492ae22d-006c-4044-b457-e0a6b6a9ceca' path='/home/otto/Kuvat/Sekalaista/Joulu 2008/00115.jpg' otto@shuttle:/tmp$ u1sdtool --waiting-content operation='Upload' node_id='ae9f7fd2-bff6-48d9-8508-0a8e6e0b831b' share_id='492ae22d-006c-4044-b457-e0a6b6a9ceca' path='/home/otto/Kuvat/Sekalaista/Pariisi 2009/IMG_8016.JPG' 11. However when I open at one.ubuntu.com > My Storage / ~/Kuvat / Sekalaista / Joulu 2008, there is no file 00115.jpg 12. Network traffic shows that uploading is happening. 13. Some other programs start to bug when the filesystem is full. Computer becomes unusable. I can reproduce this on my machine every time I restart it and wait a few hours.
2011-01-13 11:42:22 Otto Kekäläinen attachment added syncdaemon.log https://bugs.launchpad.net/ubuntuone-client/+bug/702309/+attachment/1792467/+files/syncdaemon.log
2011-01-19 11:46:10 Otto Kekäläinen ubuntuone-client: status New Confirmed
2011-10-07 08:30:08 THOMAS GWILT bug added subscriber THOMAS GWILT