From owner-freebsd-stable@freebsd.org Tue Oct 6 03:53:07 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4EF149B6462 for ; Tue, 6 Oct 2015 03:53:07 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-ob0-x231.google.com (mail-ob0-x231.google.com [IPv6:2607:f8b0:4003:c01::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0CFFEBEC for ; Tue, 6 Oct 2015 03:53:07 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by obbzf10 with SMTP id zf10so144811332obb.2 for ; Mon, 05 Oct 2015 20:53:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=ea8tCpHd0fnnOUcJSzRsQ0silX4aLhM+mOT8PAK0lCw=; b=oBnTGHBEiw1gL8Yxs/JaV0E/mVIyRBhgqtmUElcqoGeDD9QznZg40amAaPEY/ny008 P0tMXSmVybJBPd3PD6QnMYn5NdbPJUhKM5nzjSkvzQVm+cwqSPHwYQtJEQ7BPLpAYYuW Z4LMH3dQfnDU2FyRJtVsOblq91B3OxTz9pjqoEuI38LCaccdzP5qGDvGIkJ2aXYX31gC iQ+wqJQz3wAba4bd/pcvJ7dV7Ek3CQJ2Dx8173WqCQxJAS4dPsvy+FA8gGFL3MoIBfC9 zFDD3O1+OZleP17vbkdmFIWSJ0oPuv3R/iXJ9e4hl4d0fUfUIoHFw6M0AAsGiOWUi96C ghfQ== MIME-Version: 1.0 X-Received: by 10.182.104.130 with SMTP id ge2mr18895666obb.79.1444103586224; Mon, 05 Oct 2015 20:53:06 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.202.102.9 with HTTP; Mon, 5 Oct 2015 20:53:06 -0700 (PDT) In-Reply-To: <543b298ddfd6fffaf138c913a650519a@dweimer.net> References: <1721669289.24365403.1444083414400.JavaMail.zimbra@uoguelph.ca> <543b298ddfd6fffaf138c913a650519a@dweimer.net> Date: Mon, 5 Oct 2015 20:53:06 -0700 X-Google-Sender-Auth: SyNxHAvc5Bo8ijqfIUa5p9CQf2U Message-ID: Subject: Re: smbfs crashes since approx. 10.1-RELEASE From: Kevin Oberman To: dweimer@dweimer.net Cc: Christian Kratzer , FreeBSD-STABLE Mailing List Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Oct 2015 03:53:07 -0000 On Mon, Oct 5, 2015 at 5:00 PM, dweimer wrote: > On 2015-10-05 5:16 pm, Rick Macklem wrote: > >> Christian Kratzer wrote: >> >>> Hi, >>> >>> I run a regular rsync job that runs from cron and copies stuff that gets >>> created on a Windows smbfs share. >>> >>> Starting about 10.1-RELEASE the VM has become unstable and started >>> panicing. >>> >>> I have narrowed the issue down to the aforementioned rsync job. >>> >>> When I move the job to a different VM the the other VM starts crashing >>> and >>> the VM without the job becomes stable agin. >>> >>> I have panics and crashinfos stored in /var/crash if anybody is >>> interested: >>> >>> root@noc2:/var/crash # uname -a >>> FreeBSD noc2.cksoft.de 10.2-RELEASE FreeBSD 10.2-RELEASE #0 >>> r286666: Wed >>> Aug 12 15:26:37 UTC 2015 >>> root@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 >>> root@noc2:/var/crash # freebsd-version -u >>> 10.2-RELEASE-p5 >>> root@noc2:/var/crash # freebsd-version -k >>> 10.2-RELEASE >>> >> > Shouldn't the kernel version also be 10.2-RELEASE-p5? Perhaps the user > land being different than the kernel is causing an issue? > > root@freebsd:/home/dweimer # uname -a > FreeBSD freebsd.dweimer.local 10.2-RELEASE-p5 FreeBSD 10.2-RELEASE-p5 #1 > r288512: Fri Oct 2 13:54:14 CDT 2015 dweimer@freebsd.dweimer.local:/jails/devel/ROOT/usr/obj/jails/devel/ROOT/usr/src/sys/GENERIC > amd64 > root@freebsd:/home/dweimer # freebsd-version -u > 10.2-RELEASE-p5 > root@freebsd:/home/dweimer # freebsd-version -k > 10.2-RELEASE-p5 > > -- > Thanks, > Dean E. Weimer > http://www.dweimer.net/ Probably not. If freebsd-update is used and the update does not change the kernel, the kernel is not touched and remains at the prior level. If built from sources, even though the kernel is identical, the kernel version is bumped. I just confirmed that none of the updates to 10.2-RELEASE appear to update the kernel. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683