similar to: I stream read - stale NFS file handle

Hello. I've got a quartet of IBM x3630 M3 with one that is frequently hard locking under heavy NFS load. I am running 9.0-RELEASE with all the patches from freebsd-update. My problem machine has 8 16 core clients, each doing IO intensive tasks connected to it via a Procurve and the onboard igb0 interface. Mostly network reads, typically 10MB read per MB written. When the machine locks

Dear all R2.10 WinXP I have a dataset dealing with the way different wheat cultivars build their yield. Wheat ears are organised in spikelets where the spikelets can be numbered from the bottom, with even numbers on one side and odd on the other. I know how many kernels there were in each spikelet after some months spent counting them... Now I want to illustrate the differences between the

Hi, I am going to merge latest batch of the nullfs improvements into stable/9. This will bring up significant performance enchancements due to use of the shared locks for lookups if the lower layer supports it, much better caching on the nullfs layer, and proper handling of the text segments on the nullfs. Also, it should improve the error recovery and some corner cases with locking.

Hi, my FreeBSD-9/stable machine (FreeBSD freebsd-tower.goebo.site 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #2 r241044M: Sat Sep 29 12:52:01 CEST 2012 lbo@freebsd-tower.goebo.site:/usr/obj/usr/src/sys/GENERIC i386) crashes reproducibly when rsync-ing files to an NFSv4 share on the FreeBSD machine. The crash makes the system reboot. The crash creates files in /var/crash which may be obtained

TB --- 2003-08-09 16:00:11 - starting RELENG_4 tinderbox run for i386/i386 TB --- 2003-08-09 16:00:11 - checking out the source tree TB --- cd /home/des/tinderbox/RELENG_4/i386/i386 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_4 src TB --- 2003-08-09 16:00:11 - /usr/bin/cvs returned exit code 1 TB --- 2003-08-09 16:00:11 - ERROR: unable to check out the source tree TB ---

I think I've read somewhere about panic during early root mount, fsck etc.. Perhaps this might be related: Full dmesg: http://people.freebsd.org/~ariff/misc/dmesg.boot.amd64 [....] acquiring duplicate lock of same type: "vnode interlock" 1st vnode interlock @ kern/vfs_vnops.c:791 2nd vnode interlock @ kern/vfs_subr.c:2018 KDB: stack backtrace: witness_checkorder() at

On Solaris 9, using: default_mail_env = mbox:~/mail:INBOX=/var/mail/%u Here is a listing of ~/mail with UW IMAP: .: total 8 drwx------ 2 testu3 sysadmin 512 Mar 14 14:40 . drwxr-xr-x 4 testu3 sysadmin 512 Mar 14 14:40 .. -rw------- 1 testu3 sysadmin 496 Mar 14 14:40 Drafts -rw------- 1 testu3 sysadmin 496 Mar 14 14:40 Sent Items with Dovecot: .: total 16

Hi all. I have problem compiling xapian php bindings. I am using debian sarge. I have installed php4-dev before compilation. I am getting the following errors: boomer:~/xapian/xapian-bindings-0.9.0# make make all-recursive make[1]: Entering directory `/root/xapian/xapian-bindings-0.9.0' Making all in php4 make[2]: Entering directory `/root/xapian/xapian-bindings-0.9.0/php4' make

Hello, since updating two of our backup mailservers from dovecot 1.1.16 to 1.2.4 i get the following errors from dovecot-deliver when receiving (smtp) mail. Oct 16 00:10:42 mail3 dovecot: deliver(user): write_full(/home/r/user/.temp.backupmail.22774.d17050a07b2108e8) failed: Stale NFS file handle Oct 16 00:10:42 mail3 dovecot: deliver(user): copy: i_stream_read() failed: Stale NFS file handle Oct

Hello, We have seen a few of these panics in 1.1.6. It seems to happen when pine is being used and a POP3 check occurs at the same time (but not always), but I'm not positive this is always the case: --- Nov 22 11:10:32 lexiconn2 dovecot: Panic: POP3(techjm): file istream.c: line 76 (i_stream_read): assertion failed: (_stream-> skip != _stream->pos) Nov 22 11:10:32 lexiconn2

On 07/05/17 13:25, Aki Tuomi wrote: >> I use mbox compressed by gzip as read-only folder (using zlib plugin). >> >> I have errors in logs: >> Panic: file istream-zlib.c: line 416 (i_stream_zlib_seek): assertion >> failed: (ret == -1) ... >> The bug appeared in 2.2.26 and still can be reproduced (in 2.2.31) >> >> Using 'git bisect' was not

Hello, I have some jails running on ZFS, so I have to mount devfs's into them. For this purpose, I have some similar lines in /etc/fstab: devfs /pool/jail/ldap/dev devfs rw 0 0 Where /pool is a ZFS filesystem. This has worked until today -when I upgraded from a previous 7-STABLE (FreeBSD 7.0-STABLE #16: Fri Mar 7 14:30:08 CET 2008) to today's STABLE- but not

Hi, got the following with beta4 while uploading messages from a local mbox to the dovecot server in my LAN, tested with mutt and sylpheed, the same action works with 1.2.11: Mar 29 13:42:46 [dovecot] imap(juergen): Panic: stream doesn't support seeking backwards Mar 29 13:42:46 [dovecot] imap(juergen): Raw backtrace: /usr/lib/dovecot/libdovecot.so.0 [0xb76b7ec4] ->

Hello, I use mbox compressed by gzip as read-only folder (using zlib plugin). I have errors in logs: Panic: file istream-zlib.c: line 416 (i_stream_zlib_seek): assertion failed: (ret == -1) and can't read messages in MUA. IMAP commands to reproduce a bug: 1 SELECT "compressed.gz" 2 UID fetch 2 BODY.PEEK[] # sleep 5 3 UID fetch 2 BODY.PEEK[] # repeat sleep/fetch until assert (a

Hi, its me again. I still cant use any 1.1 edition because of recurrent panics... At the moment i try 1.1.7, i have again panics and problems with Next message unexpectedly lost dovecot -n # 1.1.7: /etc/dovecot.conf # OS: Linux 2.6.24.4 i686 SUSE LINUX 10.1 (i586) protocols: imap imaps pop3 pop3s ssl_ca_file: /path/path/*.servername.com.bundle.crt ssl_cert_file: /path/path/*.servername.com.crt

Hi, I have a couple of people bumping into an issue with their imap process crashing - from the users perspective, their mail client (thunderbird) just stops recieving new mail. It still seems to be possible for them to read their mail using squirell mail. When it crashes, it leaves behind a log message like this on the server: Aug 12 15:52:25 fury dovecot: imap-login: Login:

Hi, i've just upgraded to dovecot-1.2.8 (from 1.2.4) and do now get the following errors when deliver gets hands on mails with some attachments. # tail -n 1 /var/log/messages Dec 14 19:00:36 mail3 dovecot: deliver(user): Panic: file istream.c: line 96 (i_stream_read): assertion failed: (stream->eof) The MTA is postfix running inside a FreeBSD 7.2-STABLE jail. The homes where deliver

> > Is this behavior cured, or do you continue to see it? > No, the behavior isn't cured. We still continue to see it with various clients. I have posted a couple of truss outputs, but so far no resolution. Sorry for the slow response. I've been "fighting other fires". Jackie > Jackie Hunt wrote: > >> On Mon, 2007-09-03 at 12:37 +0200, Robert

Hello! Dovecot 2.2.34 (874deae) Pigeonhole version 0.4.22 (22940fb7) After the update to pigeonhole version 0.4.22 the following configuration does not work. With version 0.4.21 it works. dovecot.conf (only sieve configuration) --------------------------------------------------------------- managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope

Hello, We're having a problem in Dovecot 1.1.8 with a failed assertion on certain mbox format mailboxes. It happens both with deliver when it attempts to delier to the mailbox, and with IMAP connections for the affected box (though I'm not sure what they're doing at the time). Mar 3 12:55:26 <snip> dovecot: Panic: IMAP(<snip>): file istream.c: line 81 (i_stream_read):