From owner-freebsd-fs@FreeBSD.ORG Tue Sep 25 09:32:04 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 34A90106566B; Tue, 25 Sep 2012 09:32:04 +0000 (UTC) (envelope-from rb@gid.co.uk) Received: from mx0.gid.co.uk (mx0.gid.co.uk [194.32.164.250]) by mx1.freebsd.org (Postfix) with ESMTP id A53E18FC0A; Tue, 25 Sep 2012 09:32:03 +0000 (UTC) Received: from [194.32.164.22] (80-46-130-69.static.dsl.as9105.com [80.46.130.69]) by mx0.gid.co.uk (8.14.2/8.14.2) with ESMTP id q8P9W2eK035942; Tue, 25 Sep 2012 10:32:02 +0100 (BST) (envelope-from rb@gid.co.uk) Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=us-ascii From: Bob Bishop In-Reply-To: <20120925054023.GK1413@garage.freebsd.pl> Date: Tue, 25 Sep 2012 10:31:57 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <363B4492-ADD1-42F1-80DA-BC9DAD21EBA2@gid.co.uk> References: <20120923195357.GO1454@garage.freebsd.pl> <1735E492-3C3C-491A-82E2-884E976B4BC4@gid.co.uk> <20120923222520.GS1454@garage.freebsd.pl> <20CC6F2BF08D47ED802318697542A15D@multiplay.co.uk> <2EC5B55F-E969-4663-A753-1115D96F125C@gid.co.uk> <48D1FE59-C687-4D95-B4BF-7BC85F8B8F0A@gid.co.uk> <20120925054023.GK1413@garage.freebsd.pl> To: Pawel Jakub Dawidek X-Mailer: Apple Mail (2.1283) Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: ZFS TRIM support committed to HEAD. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2012 09:32:04 -0000 On 25 Sep 2012, at 06:40, Pawel Jakub Dawidek wrote: > On Tue, Sep 25, 2012 at 12:14:24AM +0100, Bob Bishop wrote: >> Hi, >>=20 >> Still seems to be working OK, but: >>=20 >> seagoon# zpool status >> pool: m1 >> state: ONLINE >> status: One or more devices has experienced an unrecoverable error. = An >> attempt was made to correct the error. Applications are = unaffected. >> action: Determine if the device needs to be replaced, and clear the = errors >> using 'zpool clear' or replace the device with 'zpool replace'. >> see: http://www.sun.com/msg/ZFS-8000-9P >> scan: scrub repaired 0 in 0h2m with 0 errors on Mon Sep 24 23:52:08 = 2012 >> config: >>=20 >> NAME STATE READ WRITE CKSUM >> m1 ONLINE 0 0 0 >> mirror-0 ONLINE 0 0 0 >> gpt/disk1 ONLINE 109M 0 0 >> gpt/disk0 ONLINE 109M 0 0 >>=20 >> errors: No known data errors >> seagoon# sysctl -a |grep _trim >> kstat.zfs.misc.zio_trim.zio_trim_bytes: 228731904 >> kstat.zfs.misc.zio_trim.zio_trim_success: 19406 >> kstat.zfs.misc.zio_trim.zio_trim_unsupported: 0 >> kstat.zfs.misc.zio_trim.zio_trim_failed: 0 >> seagoon#=20 >>=20 >> No device errors logged in messages, and scrub comes up clean as you = can see. The read error count is increasing, but otherwise everything = appears to work OK. >=20 > Are you sure your world and kernel are in sync? I remember seeing > similar problem when my userland was updated. I'm sure they are not. Buildworld time... > --=20 > Pawel Jakub Dawidek http://www.wheelsystems.com > FreeBSD committer http://www.FreeBSD.org > Am I Evil? Yes, I Am! http://tupytaj.pl -- Bob Bishop rb@gid.co.uk