red-lichtie

Members
  • Content Count

    3
  • Joined

  • Last visited

About red-lichtie

  • Rank
    New User
  1. I deleted the db file and it appears that btsync rescanned the tree and recreated the DB. So now to wait and see if it goes wild again. I'll report what happens either way Thanks rdebath for your help.
  2. Thanks, I tried it and the DB appears to be corrupt. sqlite> pragma integrity_check; *** in database main *** Page 192349: btreeInitPage() returns error code 11 On tree page 257370 cell 30: Child page depth differs Page 194288: btreeInitPage() returns error code 11 Page 195418: btreeInitPage() returns error code 11 ... Page 197207: btreeInitPage() returns error code 11 Page 197223: btreeInitPage() returns error code 11 Page 197208: btreeInitPage() returns error code 11 Page 197266: btreeInitPage() returns error code 11 Page 197281: btreeInitPage() returns error code 11 sqlite> Do I ju
  3. Completely dies after running for a while (day?). oom-killer kicks in and kills btsync. I tried to circumvent that yesterday my changing the oom parameters for btsync but that lead to my system completely dieing. Here is what was in the syslog the 1st time the oom-likker was called. Jul 22 06:34:11 filesrv kernel: [73164.502786] btsync invoked oom-killer: gfp_mask=0x201da, order=0, oom_adj=-17, oom_score_adj=-1000 Jul 22 06:34:11 filesrv kernel: [73164.502791] btsync cpuset=/ mems_allowed=0 Jul 22 06:34:11 filesrv kernel: [73164.502801] Pid: 2755, comm: btsync Not tainted 3.5.0-34-generic #5