search for: 1h21m

Displaying 4 results from an estimated 4 matches for "1h21m".

Did you mean: 121m
2017 Dec 29
2
notmuch: Xapian exception during database creation
Running notmuch from git on Debian testing[1] with the mail and database sitting on a ZFS filesystem, adding mail to a new database: > agrajag-testing ~/s/notmuch % ./notmuch new > Found 605510 total files (that's not much mail). > add_file: A Xapian exception occurred36m 37s remaining). > A Xapian exception occurred adding message: Unexpected end of posting list for
2007 Dec 14
0
scrub percentage complete decreasing, but without snaps.
...go scrub: scrub in progress, 0.02% done, 33h17m to go scrub: scrub in progress, 0.00% done, 44h39m to go scrub: scrub in progress, 0.00% done, 43h17m to go scrub: scrub in progress, 0.00% done, 35h6m to go scrub: scrub in progress, 1.97% done, 1h6m to go scrub: scrub in progress, 4.16% done, 1h21m to go scrub: scrub in progress, 3.91% done, 1h15m to go scrub: scrub in progress, 1.62% done, 1h10m to go scrub: scrub in progress, 0.41% done, 2h6m to go scrub: scrub in progress, 0.02% done, 31h18m to go config: NAME STATE READ WRITE CKSUM export ONLINE...
2017 Dec 31
1
notmuch: Xapian exception during database creation
...o go about debugging this? > > Building xapian-core configured with --enable-assertions is worth > trying, as it might catch the problem earlier. I'll try these things, thanks. > You could also try running it under valgrind, though that may take some > time if it normally takes 1h21m. valgrind complained about a couple of things in debugger.cc, but they seem both innocuous and unrelated. > If that doesn't help, either we need to find a way to reproduce this > which isn't using sensitive data, or add more consistency checks to the > code to try to pin down wha...
2017 Dec 29
0
notmuch: Xapian exception during database creation
...> to my employer :-( > > Any suggestions on how to go about debugging this? Building xapian-core configured with --enable-assertions is worth trying, as it might catch the problem earlier. You could also try running it under valgrind, though that may take some time if it normally takes 1h21m. If that doesn't help, either we need to find a way to reproduce this which isn't using sensitive data, or add more consistency checks to the code to try to pin down what's going on. Cheers, Olly