search for: start_offset

...int set_read_limit; + unsigned int content_length_good:1; }; int mbox_set_syscall_error(struct mail_index *index, const char *function); *** mbox-index.c.orig Mon Mar 24 05:52:44 2003 --- mbox-index.c Sun Apr 20 12:41:16 2003 *************** *** 264,277 **** start_offset = ctx->input->v_offset; i_stream_set_read_limit(ctx->input, 0); ! end_offset = start_offset + ctx->content_length; ! if (ctx->content_length == 0 || !mbox_verify_end_of_body(ctx->input, end_offset)) { !...

Sorry, this time I've no core file, (I forgot to set ulimit -c unlimited before starting dovecot) Regards, Diego. --- dovecot: Dec 09 08:26:52 Panic: IMAP(user): file mbox-sync-rewrite.c: line 590 (mbox_sync_rewrite): assertion failed: (mails[idx].from_offset == start_offset) dovecot: Dec 09 08:26:52 Error: IMAP(user): Raw backtrace: /usr/libexec/dovecot/imap [0x80f739e] -> /usr/libexec/dovecot/imap [0x80f7c5f] -> /usr/libexec/dovecot/imap(i_fatal+0) [0x80f7518] -> /usr/libexec/dovecot/imap(mbox_sync_rewrite+0x6e8) [0x8094e45] -> /usr/libexec/dovecot/imap [...

...to log in over and over again.. Looking the the log file I find this... Jun 20 15:38:02 neuron imap-login: Login: sgare [IP REMOVED] Jun 20 15:38:02 neuron imap(sgare): file imap-bodystructure.c: line 263 (part_parse_headers): assertion failed: (part->physical_pos >= input->v_offset - start_offset) Jun 20 15:38:02 neuron dovecot: child 6329 (imap) killed with signal 6 Jun 20 15:38:02 neuron imap-login: Login: sgare [IP REMOVED] Jun 20 15:38:02 neuron imap(sgare): file imap-bodystructure.c: line 263 (part_parse_headers): assertion failed: (part->physical_pos >= input->v_offset - st...

...- a/fs/btrfs/extent_io.c +++ b/fs/btrfs/extent_io.c @@ -3053,6 +3053,22 @@ static inline struct page *extent_buffer_page(struct extent_buffer *eb, return p; } +void access_extent_buffer_page(struct bio_vec *vec, struct extent_buffer *eb, + unsigned long start, unsigned long len) +{ + size_t start_offset = eb->start & ((u64)PAGE_CACHE_SIZE - 1); + unsigned long i = (start_offset + start) >> PAGE_CACHE_SHIFT; + size_t offset = (start_offset + start) & + ((unsigned long)PAGE_CACHE_SIZE - 1); + + WARN_ON(start > eb->len); + WARN_ON(start + len > eb->start + eb->len);...

...tml == Changes * currently this version isn''t very extendable. For example, you can''t write your own Analyzer, Filter or Query. * changed Token#term_text to Token#text * changed Token#position_increment to Term#pos_inc * changed order of args to Token.new. Now Term.new(text, start_offset, end_offset, pos_inc=1, type="text"). NOTE: type does nothing. * changed TermVectorOffsetInfo#start_offset to TermVectorOffsetInfo#start * changed TermVectorOffsetInfo#end_offset to TermVectorOffsetInfo#end * added :id_field option to Index::Index class.

...dovecot-acls:cache_secs=10 -------------- next part -------------- List of errors: "Trying to close mailbox with open transactions" "Corrupted transaction log file Unexpected garbage at EOF" "fscking index file" "Transaction log got desynced for index" "start_offset (3872) > current sync_offset" "Fixed index file" "log_file_head_offset 3872 -> 3680" "Corrupted transaction log file record size too small" "Transaction log file marked corrupted" "file mail-index-sync-update.c: line 599: unreached" &quot...

...set are the last one returned "+1". But doing so we reduce the "acceptance criteria window". I propose to add three more fields in the struct btrfs_ioctl_search_key: + /* starting search key fields */ + __u32 start_type; + __u64 start_objectid; + __u64 start_offset; Is resposibility of the program to fill these fields during the begin of the search. If these are 0, the code set these to the min_* values. At the end of the search the kernel code stores the last key found + 1, in accordance of the "acceptance criteria". So for the next search thes...

...tents, we need to start at our start + * offset. + */ + start = block_group->key.objectid; + /* Write out the extent entries */ do { struct btrfs_free_space_entry *entry; @@ -587,6 +622,8 @@ int btrfs_write_out_cache(struct btrfs_root *root, unsigned long offset = 0; unsigned long start_offset = 0; + next_page = false; + if (index == 0) { start_offset = first_page_offset; offset = start_offset; @@ -598,7 +635,7 @@ int btrfs_write_out_cache(struct btrfs_root *root, entry = addr + start_offset; memset(addr, 0, PAGE_CACHE_SIZE); - while (1) { + while (node &&...

...!= 1113087252) dovecot: Apr 09 20:52:21 Error: 25454 IMAP(support): Lost transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log seq 1 dovecot: Apr 09 20:52:21 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: start_offset (96) > file size (24) dovecot: Apr 09 20:52:21 Error: 25454 IMAP(support): Corrupted transaction log file /mailhome/new/m/2/support/.imap/INBOX/dovecot.index.log: invalid new transaction log sequence (3 >= 3) dovecot: Apr 09 20:52:23 Error: 25454 IMAP(support): Corrupted transaction log fil...

...quot;Checking messages in folder spam" or something like that), which makes gnus just stop, or when I try to enter that folder in mutt. Jan 30 17:07:09 kalle imap(ke): file imap-bodystructure.c: line 278 (part_parse_headers): assertion failed: (part->physical_pos >= input->v_offset - start_offset) Is there something I can do to determine which message it crashed on? Maildir format, version 0.99.10.4.

..., then advances 8*size + 5 bits. First of all, shouldn't that be 5 bits for size (to match manual)? And where did that '+ 5 bits' come from? Next, and slightly unrelated question: Why does int jitter_buffer_update_delay(JitterBuffer *jitter, JitterBufferPacket *packet, spx_int32_t *start_offset); include the packet parameter? It's not used in the code, and it also makes the API slightly confusing as it's very unclear what that parameter should be :)

...". In the debugger I can see that the crash happens in search.c on line 907. The reason is that the excerpt->end field is -1. I think the reason is because in this code from search.c: for (e_start = e_end = 0; e_start < mv->size; e_start++) { const int start_offset = matches[e_start].start_offset; if (e_start > e_end) { running_score = 0.0; e_end = e_start; } while (e_end < mv->size && (matches[e_end].end_offset...

...I have a spam mailbox that if I try and open (from any client), the imap process dies and this is written to the error logs: Dec 21 18:57:11 theronge imap(mronge): file imap-bodystructure.c: line 278 (part_parse_headers): assertion failed: (part->physical_pos >= input->v_offset - start_offset) Dec 21 18:57:11 theronge dovecot: child 28911 (imap) killed with signal 6 I had this same issue with my Inbox a few weeks ago, so I moved all the e-mail out and moved each piece back in one by one, in order to determine if a piece of mail was causing the issue. As soon as all my mail was...

...c | sort -rn 7547 file index-sync.c: line 39: assertion failed: (seq_range_exists(&ibox->recent_flags, uid)) 89 file index-mail.c: line 1091: assertion failed: (! mail->data.destroying_stream) 18 file mbox-sync-rewrite.c: line 590: assertion failed: (mails[idx].from_offset == start_offset) 5 file ostream-file.c: line 533: assertion failed: ((size_t)ret == total_size || !fstream->file) 5 file mbox-lock.c: line 675: assertion failed: (lock_type == F_RDLCK || mbox->mbox_lock_type != F_RDLCK) 1 file message-parser.c: line 684: assertion failed: (ctx->part->...

pwk.linuxfan@gmx.de wrote: > On Sunday 08 July 2007 02:24, Thorvald Natvig wrote: > >> Next, and slightly unrelated question: >> Why does >> int jitter_buffer_update_delay(JitterBuffer *jitter, JitterBufferPacket >> *packet, spx_int32_t *start_offset); >> include the packet parameter? It's not used in the code, and it also >> makes the API slightly confusing as it's very unclear what that >> parameter should be :) >> > > The packet parameter is included to allow coming up iterations of the > jitter...

Still seeing a few core dumps via the deliver process and corrupted transaction log files with RC18: Jan 22 10:46:36 zahara deliver(user at host.com): Corrupted transaction log file /data/mail/host.com/us/user at home.com/dovecot.index.log: start_offset (71680) > file size (71520) Jan 22 10:46:36 zahara deliver(user at host.com): seq = 6, rec->uid = 0, first_new_seq = 6, records = 5 Jan 22 10:46:36 zahara kernel: pid 41186 (deliver), uid 127: exited on signal 6 (core dumped) Jan 22 10:50:17 zahara deliver(user at host.com): Corrupted transa...

...file message-address.c: line 262 (message_address_write): assertion failed: (addr->domain != NULL) And one that's only ever been spotted once in the last few weeks: file imap-bodystructure.c: line 278 (part_parse_headers): assertion failed: (part->physical_pos >= input->v_offset - start_offset) I'm waiting for them to happen again to provide some more info... Regards, Bernard. -- Bernard Blackham bernard at blackham dot com dot au

...I have dovecot 0.99.11 on a Linux machine running against a maildir based mailbox. I am getting the following errors in the maillog: Nov 27 23:08:14 fawad3 imap(fawad): file imap-bodystructure.c: line 278 (part_parse_headers): assertion failed: (part->physical_pos >= input->v_offset - start_offset) Nov 27 23:08:14 fawad3 dovecot: child 14202 (imap) killed with signal 6 This happens when the mail reader tries to enumerate the messages in the INBOX. I am able to read the messages whose headers have already been cached by the mail reader. It is also able to read others folders without any...

Hello, I'm currently testing dovecot/imap (Version 0.99.13). I found this in the log: imap(xxxxx): [ID 265587 mail.crit] file imap-bodystructure.c: line 278 (part_parse_headers): assertion failed: (part->physical_pos >= input->v_offset - start_offset) dovecot: [ID 684838 mail.error] child 7376 (imap) killed with signal 6 The user tried to setup a new folder (with Thunderbird) and that seemed to cause this error. What does that mean ? Should I worry about ? Martin ----------------------------------------------------------------- Martin Pre...

...:44 Error: IMAP(foobar): Corrupted index file /home/foobar/ Mail/imapd-indices/Mail/.imap/NDMP/dovecot.index: messages_count too large (5200 93696 > 3) dovecot: Mar 01 09:20:44 Error: IMAP(foobar): Corrupted transaction log file /ho me/foobar/Mail/imapd-indices/Mail/.imap/NDMP/dovecot.index.log: start_offset (61 44) > file size (1768) dovecot: Mar 01 09:20:44 Warning: IMAP(foobar): fscking index file /home/foobar/ Mail/imapd-indices/Mail/.imap/NDMP/dovecot.index dovecot: Mar 01 09:20:44 Error: child 111112 (imap) killed with signal 11 -dp #0 0x0809eaa1 in mail_index_lock_exclusive (index=...