search for: unflushed

Hi, Is it possible to perform a search without flushing the index? I've got an application that updates the index every 4 hours but I need to be able to search the new data fairly quickly after the index is updated. The problem revolves around the fact that the update is often much less than 10 000 documents so it isn't being flushed until quite a bit latter. I realise I can do a flush

Greets, WRT this discussion: http://lists.xapian.org/pipermail/xapian-discuss/2009-November/007300.html Richard recommends calling flush() before closing a index database segment, etc. Well, I can confirm that calling flush() is *required* before calling close() since close() on it's own does not commit/flush any pending writes/whatever unless the Perl script terminates, etc. So, for a

Hello, I have two servers where I can push VMs from one to the other by issuing the command virsh migrate --live --persistent --copy-storage-all --verbose \ test6 qemu+ssh://kvmhost2/system on kvmhost1. I can get the VM back by issuing the equivalent command on kvmhost2: virsh migrate --live --persistent --copy-storage-all --verbose \ test6 qemu+ssh://kvmhost1/system virsh

I seem to be seeing cases where I call db.delete_document(somedocid) with no error, then flush() and delete the database object, but the document is still there after process exit. The write lock is normally deleted, so it appears that the database close finished normally. If I then then call delete_document(somedocid) from another command/process, this time it goes away. I've been seeing

Hi, I am using the Xapian-0.8.0 snapshot from 15-Apr-2004 02:14, and I am using the same Xapian::WritableDatabase instance for indexing and searching. Currently each search causes a database flush, which is slow. How can I avoid this flush? It seems that I have to modify Xapian to either - search only the already flushed data (eventually missing some hits) or - search the un-flushed data, too.

Hello, I get hanging rsync-processes while synchronisize windows to linux, starting on linux. The problem is not new, I found some mails in this list (archive) and on http://www.mikerubel.org/computers/rsync_snapshots/#Bugs too. Example of the command: rsync -e 'ssh -i /backup/data/servers/identities/backup.W2000Server -p 22 -x -oForwardAgent=no -oClearAllForwardings=yes' --archive

...e75c 100644 --- a/usr/klibc/stdio/fwrite.c +++ b/usr/klibc/stdio/fwrite.c @@ -59,6 +59,7 @@ size_t _fwrite(const void *buf, size_t count, FILE *file) size_t bytes = 0; size_t pf_len, pu_len; const char *p = buf; + const char *q; /* We divide the data into two chunks, flushed (pf) and unflushed (pu) depending on buffering mode @@ -67,23 +68,16 @@ size_t _fwrite(const void *buf, size_t count, FILE *file) switch (f->bufmode) { case _IOFBF: pf_len = 0; - pu_len = count; break; case _IOLBF: - pf_len = count; - pu_len = 0; - - while (pf_len && p[pf_len-1] != '\...

...re doing the blockcopy; you may also have to manually coordinate quiescing the disks through the guest agent if you want your backup to be bootable from a stable point in guest I/O (the copy you are creating via migration is equivalent to what you get when you yank the power cord; the disk may have unflushed pending I/O that you lose, unless you involve the guest agent to quiesce data operations). > > The goal is to get a backup copy of a running system onto a second > system (kvmhost2). > The copy (snapshot) from kvmhost2 can then be copied to a backup server, > and can be used for a...

Hello List, i am using Ubuntu Server 6.06 with the smbldap installer script from majen.net/smbldap/ I am using VMWare to run my test systems (Ubuntu server and Windows Domain Clients) After producing a power supply failure (stopping my Ubuntu and windows client by the stop button in vmware) and starting them up again i can see a delta in my ldap database: Before Power failure:

...t actually have a usable qcow2 file. How is it not usable? When you break sync at the conclusion of a blockcopy, the image that you no longer use is an accurate snapshot of the state of the disk at the time you broke sync; but whether or not that is useful to a guest depends on how much influence unflushed I/O that was still in guest memory at the time you broke sync will have on your data. > > I find lots of discussion online about getting the steps to work, but as > yet find nothing about using the resulting file. > > What am I missing here? > > libvirt (1.2.2) and qemu (2....

I am experimenting with the blockcopy command, and after figuring out how to integrate qemu-nbd, nbd-client and dumpxml/undefine/blockcopy/define/et. al. I have one remaining question: What's the point? The "replication" disk file is not, from what I can ascertain, bootable. I expect this operation to create a pristine copy of my source qcow2 file (at a given point in time)

Well.... you might remember that I have had problems will my NFS fileserver that run ext3 with data=journal. The filesystem corruption now seems too be solved with the patch (plus amendment) that I posted, so I am happy about that... but there is more. I have known for a while that ext3 doesn't behave very well when the journal fills up. If it finds that the journal is full, and the

Sean, thanks for reminding this, Alp did commit a class derived from raw_svector_ostream conatining an internal SmallString he called small_string_ostream. The commit was reverted after a day due to a disagreement about the commit approval and apparently abandoned. http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20140623/223393.html

Hi, I''ve added some preliminary support for VT-d for paravirtualized guests. This must be enabled using an ''iommu_pv'' boot parameter (disabled by default). I''ve added some python bindigs to allow xend to assign PCI devices to IOMMU for PV guests. For HVM guests this is handled in ioemu. Not sure if it makes sense to handle both cases in one place. The

I am [trying to] perform a test prior to moving my data to solaris and zfs. Things are going very poorly. Please suggest what I might do to understand what is going on, report a meaningful bug report, fix it, whatever! Both to learn what the compression could be, and to induce a heavy load to expose issues, I am running with compress=gzip-9. I have two machines, both identical 800MHz P3 with