From owner-freebsd-fs@FreeBSD.ORG Mon May 27 05:10:20 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 96C9CC1E for ; Mon, 27 May 2013 05:10:20 +0000 (UTC) (envelope-from ngrundmann@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) by mx1.freebsd.org (Postfix) with ESMTP id 4412A182 for ; Mon, 27 May 2013 05:10:19 +0000 (UTC) Received: from mailout-de.gmx.net ([10.1.76.33]) by mrigmx.server.lan (mrigmx002) with ESMTP (Nemesis) id 0Md1Gm-1UxoLp0RBi-00IAPc for ; Mon, 27 May 2013 07:10:19 +0200 Received: (qmail invoked by alias); 27 May 2013 05:10:18 -0000 Received: from i59F56C7C.versanet.de (EHLO [192.168.1.10]) [89.245.108.124] by mail.gmx.net (mp033) with SMTP; 27 May 2013 07:10:18 +0200 X-Authenticated: #5821560 X-Provags-ID: V01U2FsdGVkX19mWOo7YbVmoC7u/h3bHqKfbBMiU3I0a+qIanYJYo TQQ8j27fay3IjZ Message-ID: <51A2EABA.9080306@gmx.de> Date: Mon, 27 May 2013 07:10:18 +0200 From: Norbert User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130201 Thunderbird/17.0.2 MIME-Version: 1.0 To: freebsd-fs@freebsd.org Subject: FreeBSD problem with rsync, sshfs and MooseFS Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 May 2013 05:10:20 -0000 Hello, I am checking to use MooseFS a "backbone" distributed filesystem on servers and clients. Most things are working fine - setup was very easy. But one problem I discovered was using rsync - and it came up with rdiff-backup as well! Long lasting copies with tar or scp worked fine... The mounting of the filesystem is done over fusefs-ssh... So what was the first panic after installing fuse4bsd and the "standard" kmod module: current process = 1234 (rsync) ... #0 0xffffffff808680fe at kdb_backtrace+0x5e #1 0xffffffff80832cb7 at panic+0x187 #2 0xffffffff80b18400 at trap_fatal+0x290 #3 0xffffffff80b18749 at trap_pfault+0x1f9 #4 0xffffffff80b18c0f at trap+0x3df #5 0xffffffff80b0313f at calltrap+0x8 #6 0xffffffff80b17cf0 at amd64_syscall+0x450 #7 0xffffffff80b03427 at Zfast_syscall+0xf7 see also: http://www.freebsd.org/cgi/query-pr.cgi?pr=167362 and: http://forums.pcbsd.org/showthread.php?p=104651 Then I got the information to use an experimental kmod verion 0.4.4 (see http://people.freebsd.org/~flo/fusefs-kmod.tar.bz2), which I compiled and installed. Now it was much better - but instead of immediately dying the panic was after running rdiff-backup for 10 minutes... that is much better - but not ok... :-( I got the panic message: May 23 14:12:47 HOST kernel: Fatal trap 12: page fault while in kernel mode May 23 14:12:47 HOST kernel: cpuid = 0; apic id = 00 May 23 14:12:47 HOST kernel: fault virtual address = 0x64 May 23 14:12:47 HOST kernel: fault code = supervisor read data, page not present May 23 14:12:47 HOST kernel: instruction pointer = 0x20:0xffffffff818541a4 May 23 14:12:47 HOST kernel: stack pointer = 0x28:0xffffff822d3467b0 May 23 14:12:47 HOST kernel: frame pointer = 0x28:0xffffff822d346870 May 23 14:12:47 HOST kernel: code segment = base 0x0, limit 0xfffff, type 0x1b May 23 14:12:47 HOST kernel: = DPL 0, pres 1, long 1, def32 0, gran 1 May 23 14:12:47 HOST kernel: processor eflags = interrupt enabled, resume, IOPL = 0 May 23 14:12:47 HOST kernel: current process = 3624 (python2.7) May 23 14:12:47 HOST kernel: trap number = 12 May 23 14:12:47 HOST kernel: panic: page fault May 23 14:12:47 HOST kernel: cpuid = 0 May 23 14:12:47 HOST kernel: KDB: stack backtrace: May 23 14:12:47 HOST kernel: #0 0xffffffff809208a6 at kdb_backtrace+0x66 May 23 14:12:47 HOST kernel: #1 0xffffffff808ea8be at panic+0x1ce May 23 14:12:47 HOST kernel: #2 0xffffffff80bd8240 at trap_fatal+0x290 May 23 14:12:47 HOST kernel: #3 0xffffffff80bd857d at trap_pfault+0x1ed May 23 14:12:47 HOST kernel: #4 0xffffffff80bd8b9e at trap+0x3ce May 23 14:12:47 HOST kernel: #5 0xffffffff80bc315f at calltrap+0x8 May 23 14:12:47 HOST kernel: #6 0xffffffff80c687f1 at VOP_CREATE_APV+0x31 May 23 14:12:47 HOST kernel: #7 0xffffffff809604e0 at uipc_bind+0x380 May 23 14:12:47 HOST kernel: #8 0xffffffff8095a95e at kern_bind+0xde May 23 14:12:47 HOST kernel: #9 0xffffffff8095a9d1 at sys_bind+0x41 May 23 14:12:47 HOST kernel: #10 0xffffffff80bd7ae6 at amd64_syscall+0x546 May 23 14:12:47 HOST kernel: #11 0xffffffff80bc3447 at Xfast_syscall+0xf7 May 23 14:12:47 HOST kernel: Uptime: 3h8m41s May 23 14:12:47 HOST kernel: Automatic reboot in 15 seconds - press a key on the console to abort May 23 14:12:47 HOST kernel: Rebooting... Oh, I forgot: I am using FreeBSD 9.1 on AMD64... My question: has anyone an idea how to proceed, some help or a workaround? That would be very nice :-) I don't have time to do testing on a debugging kernel and analyse core dumps - sorry Thanks, Norbert