From owner-freebsd-stable@FreeBSD.ORG Mon Jan 21 15:03:34 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id AF98930F for ; Mon, 21 Jan 2013 15:03:34 +0000 (UTC) (envelope-from ian@FreeBSD.org) Received: from duck.symmetricom.us (duck.symmetricom.us [206.168.13.214]) by mx1.freebsd.org (Postfix) with ESMTP id ADCA97EF for ; Mon, 21 Jan 2013 15:03:33 +0000 (UTC) Received: from damnhippie.dyndns.org (daffy.symmetricom.us [206.168.13.218]) by duck.symmetricom.us (8.14.6/8.14.6) with ESMTP id r0LF3Wr0012331 for ; Mon, 21 Jan 2013 08:03:32 -0700 (MST) (envelope-from ian@FreeBSD.org) Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id r0LF38SD011776; Mon, 21 Jan 2013 08:03:08 -0700 (MST) (envelope-from ian@FreeBSD.org) Subject: Re: time issues and ZFS From: Ian Lepore To: Daniel Braniss In-Reply-To: References: Content-Type: text/plain; charset="us-ascii" Date: Mon, 21 Jan 2013 08:03:08 -0700 Message-ID: <1358780588.32417.414.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-stable@FreeBSD.org, Ronald Klop X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jan 2013 15:03:34 -0000 On Mon, 2013-01-21 at 13:33 +0200, Daniel Braniss wrote: > After many trials (and errors), here are some facts: > > host: DELL PowerEdge R710, 16GB, > mfi0: > mfid0: 14305280MB (29297213440 sectors) RAID volume 'r5' is optimal > mfi1: > mfid1: 12393472MB (25381830656 sectors) RAID volume 'Virtual Disk 0' is > optimal > > we have NO problems with FreeBSD-8.3-STABLE, but with 9.1-STABLE, the real-time > clock slows down when doing some zfs stuff like send|receive, typing 'date' > when less that 1000s went by seems to crorrect the problem, > ntpd kicks in and on track again. > > I have a cron job just logging date every 5 minutes, and the loghost sees: > > |-- local time on loghost | time on problematic host > Jan 20 19:56:19 store-02.cs.huji.ac.il Jan 20 19:56:19 danny: Sun Jan 20 > 19:56:19 IST 2013 -- ok > Jan 20 20:15:00 store-02.cs.huji.ac.il Jan 20 20:15:00 danny: Sun Jan 20 > 20:15:00 IST 2013 -- ok > Jan 20 21:30:00 store-02.cs.huji.ac.il Jan 20 20:21:06 danny: Sun Jan 20 > 20:21:06 IST 2013 -- off by 1:09 > Jan 20 21:33:53 store-02.cs.huji.ac.il Jan 20 20:25:00 danny: Sun Jan 20 > 20:25:00 IST 2013 -- off by 1:08 > Jan 20 21:38:54 store-02.cs.huji.ac.il Jan 20 20:30:00 danny: Sun Jan 20 > 20:30:00 IST 2013 -- off by 1:09 > ... > Jan 20 22:03:54 store-02.cs.huji.ac.il Jan 20 20:55:00 danny: Sun Jan 20 > 20:55:00 IST 2013 -- diff is now constant > .. > Jan 20 22:04:13 store-02.cs.huji.ac.il Jan 20 20:55:19 ntpd[1848]: time > correction of 4134 seconds exceeds sanity limit (1000); set clock manually to > the correct UTC time. > ... > Jan 20 22:58:53 store-02.cs.huji.ac.il Jan 20 21:50:00 danny: Sun Jan 20 > 21:50:00 IST 2013 > > > strangely, when running 8.3, ACPI-fast is chosen: > kern.timecounter.choice: TSC(-100) HPET(900) ACPI-fast(1000) i8254(0) > dummy(-1000000) > but with 9.1 TSC-low gets chosen: > kern.timecounter.choice: TSC-low(1000) ACPI-fast(900) HPET(950) i8254(0) > dummy(-1000000) > > so I did sysctl kern.timecounter.hardware=ACPI-fast, but the same happens - > unless it can't be changed after boot. > > I realy need help here! > > thanks, > danny What's the output of sysctl kern.eventtimer? Does the bad behavior change if you set kern.eventimer.periodic=1? -- Ian