From owner-freebsd-fs@FreeBSD.ORG Sun Jul 11 08:19:10 2010 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A39791065676; Sun, 11 Jul 2010 08:19:10 +0000 (UTC) (envelope-from remko@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 7BD668FC0C; Sun, 11 Jul 2010 08:19:10 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o6B8JAFW077319; Sun, 11 Jul 2010 08:19:10 GMT (envelope-from remko@freefall.freebsd.org) Received: (from remko@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o6B8JAWk077315; Sun, 11 Jul 2010 08:19:10 GMT (envelope-from remko) Date: Sun, 11 Jul 2010 08:19:10 GMT Message-Id: <201007110819.o6B8JAWk077315@freefall.freebsd.org> To: remko@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: remko@FreeBSD.org Cc: Subject: Re: misc/148490: zfs: zpool attach - resilver bidirectionally, and reports incorrect time 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: Sun, 11 Jul 2010 08:19:10 -0000 Old Synopsis: zpool attach - resilver bidirectionally, and reports incorrect time New Synopsis: zfs: zpool attach - resilver bidirectionally, and reports incorrect time Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: remko Responsible-Changed-When: Sun Jul 11 08:18:55 UTC 2010 Responsible-Changed-Why: reassign to zfs team http://www.freebsd.org/cgi/query-pr.cgi?pr=148490 From owner-freebsd-fs@FreeBSD.ORG Sun Jul 11 21:20:09 2010 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E2665106564A for ; Sun, 11 Jul 2010 21:20:09 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id B8EC78FC08 for ; Sun, 11 Jul 2010 21:20:09 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o6BLK9Nc045827 for ; Sun, 11 Jul 2010 21:20:09 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o6BLK9gp045826; Sun, 11 Jul 2010 21:20:09 GMT (envelope-from gnats) Date: Sun, 11 Jul 2010 21:20:09 GMT Message-Id: <201007112120.o6BLK9gp045826@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Martin Matuska Cc: Subject: Re: kern/148490: [zfs]: zpool attach - resilver bidirectionally, and reports incorrect time X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Martin Matuska List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Jul 2010 21:20:10 -0000 The following reply was made to PR kern/148490; it has been noted by GNATS. From: Martin Matuska To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/148490: [zfs]: zpool attach - resilver bidirectionally, and reports incorrect time Date: Sun, 11 Jul 2010 23:11:20 +0200 The fix for this problem is part of the upcoming upgrade of ZFS to v15. A patch for 8-STABLE and 8.1-RELEASE users will be provided. From owner-freebsd-fs@FreeBSD.ORG Sun Jul 11 22:39:56 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DD31F106564A for ; Sun, 11 Jul 2010 22:39:56 +0000 (UTC) (envelope-from zw_uk@hotmail.com) Received: from bay0-omc4-s28.bay0.hotmail.com (bay0-omc4-s28.bay0.hotmail.com [65.54.190.230]) by mx1.freebsd.org (Postfix) with ESMTP id C9A888FC19 for ; Sun, 11 Jul 2010 22:39:56 +0000 (UTC) Received: from BAY150-W47 ([65.54.190.199]) by bay0-omc4-s28.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Sun, 11 Jul 2010 15:38:55 -0700 Message-ID: X-Originating-IP: [81.5.176.185] From: S M To: Date: Sun, 11 Jul 2010 22:38:56 +0000 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 11 Jul 2010 22:38:55.0953 (UTC) FILETIME=[D88B5410:01CB2149] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: ZFS - Unable to replace replacing drive 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: Sun, 11 Jul 2010 22:39:56 -0000 Hi all=2C Can anyone help with a ZFS problem I've been having? I have a single ZFS po= ol as shown below: # zpool status pool: vault state: DEGRADED scrub: resilver completed after 0h8m with 0 errors on Sun Jul 11 22:18:27 = 2010 config: NAME STATE READ WRITE CKSUM vault DEGRADED 0 0 0 mirror ONLINE 0 0 0 da0.eli ONLINE 0 0 0 da8.eli ONLINE 0 0 0 ad4.eli ONLINE 0 0 0 mirror DEGRADED 0 0 0 da1.eli ONLINE 0 0 0 10.0M resilv= ered replacing UNAVAIL 0 7.42K 0 insufficient= replicas 176228571956779269 UNAVAIL 0 7.79K 0 was /dev/ad6= .eli 1650754158582652028 UNAVAIL 0 7.81K 0 was /dev/da9= 9.eli da9.eli ONLINE 0 0 0 10.0M resilv= ered errors: No known data errors However I can't seem to get rid of the replacing drives. What happened was = that I tried to replace /dev/ad6.eli with /dev/da99.eli (because ad6.eli br= oke) and da99.eli was also faulty and so failed the replace. How do I get rid of them? The array is otherwise healthy.... # zpool offline vault 176228571956779269 cannot offline 176228571956779269: no valid replicas # zpool offline vault 1650754158582652028 cannot offline 1650754158582652028: no valid replicas # zpool detach vault 1650754158582652028 cannot detach 1650754158582652028: no valid replicas # zpool detach vault 176228571956779269 cannot detach 176228571956779269: no valid replicas replace doeesn't work either. ZDB returns: vault version=3D14 name=3D'vault' state=3D0 txg=3D173963 pool_guid=3D14228437791114878229 hostid=3D4269824854 hostname=3D'vault.internal' vdev_tree type=3D'root' id=3D0 guid=3D14228437791114878229 children[0] type=3D'mirror' id=3D0 guid=3D15203813302661836458 metaslab_array=3D23 metaslab_shift=3D34 ashift=3D12 asize=3D2000394125312 is_log=3D0 children[0] type=3D'disk' id=3D0 guid=3D7238937831460639650 path=3D'/dev/da0.eli' whole_disk=3D0 DTL=3D51 children[1] type=3D'disk' id=3D1 guid=3D14125934351009663627 path=3D'/dev/da8.eli' whole_disk=3D0 DTL=3D53 children[2] type=3D'disk' id=3D2 guid=3D8553277371515810839 path=3D'/dev/ad4.eli' whole_disk=3D0 DTL=3D169 children[1] type=3D'mirror' id=3D1 guid=3D14672070090293526603 metaslab_array=3D118 metaslab_shift=3D34 ashift=3D12 asize=3D2000394125312 is_log=3D0 children[0] type=3D'disk' id=3D0 guid=3D4020825290461516758 path=3D'/dev/da1.eli' whole_disk=3D0 DTL=3D123 children[1] type=3D'replacing' id=3D1 guid=3D496235429895718168 whole_disk=3D0 children[0] type=3D'disk' id=3D0 guid=3D176228571956779269 path=3D'/dev/ad6.eli' whole_disk=3D0 not_present=3D1 DTL=3D54 children[1] type=3D'disk' id=3D1 guid=3D1650754158582652028 path=3D'/dev/da99.eli' whole_disk=3D0 not_present=3D1 DTL=3D168 children[2] type=3D'disk' id=3D2 guid=3D5694121814811722857 path=3D'/dev/da9.eli' whole_disk=3D0 DTL=3D120 uname -a: FreeBSD vault.internal 8.1-PRERELEASE FreeBSD 8.1-PRERELEASE #4: = Thu Jul 1 09:47:23 UTC 2010 sm@vault.internal:/usr/obj/usr/src/sys/vau= lt amd64 How do I fix this? ZFS says that the array is degraded but it isn't really= =2C I just can't get rid of this. =20 _________________________________________________________________ http://clk.atdmt.com/UKM/go/197222280/direct/01/ We want to hear all your funny=2C exciting and crazy Hotmail stories. Tell = us now= From owner-freebsd-fs@FreeBSD.ORG Mon Jul 12 00:25:41 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1C2EB1065672 for ; Mon, 12 Jul 2010 00:25:41 +0000 (UTC) (envelope-from eingorn777@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id D83BC8FC13 for ; Mon, 12 Jul 2010 00:25:40 +0000 (UTC) Received: by iwn35 with SMTP id 35so5091836iwn.13 for ; Sun, 11 Jul 2010 17:25:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=/4eYCbvEOYhdLJAfz8/fnAwHiUNfmDptvVtZiPCkFN8=; b=Pc9cjgo087eE+Ge2YID8L+CuuAzV3Wxl0Z8Khqp7CznDP2Z/MxMfR6vh/0/gc3KPxm J0GNFVU95+TSYlBmR6FgTB8sqfsxmRjfpNHtGyOLzKGoEhjrk+qOKHC5gnHt3iUDSTzk efJsFMKkYKLrYCON5ebIk3iJWzmzyMi+2DP0I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=KWKKNcDJduUS1EyKM3U5aMTT4+y3fVMbROoLc2gDw2jQT5LOb8i95snzKfieAzuv/T I/oVPo8GFquCI1V4YiU+G0g/GgPqYIxpKkhrOSfXmyJ9AcvOKpljuDOVfGnJCWfwFl/H awo4LzlG7kAA/I8EApSxADpG0IONvTOAh9XKs= MIME-Version: 1.0 Received: by 10.231.171.18 with SMTP id f18mr9153396ibz.9.1278892807770; Sun, 11 Jul 2010 17:00:07 -0700 (PDT) Received: by 10.231.35.133 with HTTP; Sun, 11 Jul 2010 17:00:07 -0700 (PDT) Date: Mon, 12 Jul 2010 00:00:07 +0000 Message-ID: From: Dmitry Lunts To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: fsdb&smartctl&/var/log/messages 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: Mon, 12 Jul 2010 00:25:41 -0000 Hello,all! The question is as follows. 1).When I try to upgrade some port or merely execute the command pkgdb -uF I get the error: Input/output error - /var/db/pkg/kdeutils-3.5.10_5/+CONTENTS 2)$sudo cat /var/log/messages|grep DMA|tail -2 gives: Jul 12 03:07:06 dim007 kernel: ad6: FAILURE - READ_DMA status=3D51 error=3D40 LBA=3D4007967 Jul 12 03:07:09 dim007 kernel: ad6: FAILURE - READ_DMA status=3D51 error=3D40 LBA=3D4007967 3)From the output of $cat /etc/fstab and $sudo bsdlabel ad6s1: # size offset fstype [fsize bsize bps/cpg] a: 1048576 0 4.2BSD 2048 16384 8 b: 1048576 1048576 swap c: 100663227 0 unused 0 0 # "raw" part, don'= t edit d: 2097152 2097152 4.2BSD 2048 16384 28552 e: 655360 4194304 4.2BSD 2048 16384 40968 f: 37748736 4849664 4.2BSD 2048 16384 28552 g: 58064827 42598400 4.2BSD 2048 16384 28552 I can conclude that LBA=3D4007967 falls into /dev/ad6s1d partition mounted = as /var Next: 4) $sudo fsdb -r /dev/ad6s1d ** /dev/ad6s1d (NO WRITE) Examining file system `/dev/ad6s1d' Last Mounted on /var current inode: directory I=3D2 MODE=3D40755 SIZE=3D512 BTIME=3DJan 1 15:07:34 2009 [0 nsec] MTIME=3DJul 12 03:03:19 2010 [0 nsec] CTIME=3DJul 12 03:03:19 2010 [0 nsec] ATIME=3DJul 10 01:09:22 2010 [0 nsec] OWNER=3Droot GRP=3Dwheel LINKCNT=3D27 FLAGS=3D0 BLKCNT=3D4 GEN=3D5e655284 Offset of bad LBA sector within /dev/ad6s1d (i.e., /var) partition is: (bad LBA sector-63-offset of /dev/ad6s1d=3D4007967-63-2097152=3D1910752 (se= e the output of bsdlabel above) 5) Searching for inode: fsdb (inum: 2)>findblk 1910752 1910752: data block of inode 117934 6)Searching for file: $sudo find /var -inum 117934 /var/db/pkg/kdeutils-3.5.10_5/+CONTENTS which exactly corresponds to error message from pkgdb -uF (see item 1) above) On the other hand, the following script executes without errors: $export i=3D4007967 $ while [ $i -lt 4007976 ] / #checking 10 sectors > do echo $i > dd if=3D/dev/ad6 of=3D/dev/null bs=3D512 count=3D1 skip=3D$i > let i+=3D1 > done 4007967 1+0 records in 1+0 records out 512 bytes transferred in 0.008722 secs (58702 bytes/sec) 4007968 So, no errors. 7)Moreover, following commands give quite another number of bad LBA secror: $sudo smartctl -t long /dev/ad6 $sudo smartctl -l selftest /dev/ad6 smartctl 5.39.1 2010-01-28 r3054 [FreeBSD 7.3-RELEASE-p1 i386] (local build= ) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net =3D=3D=3D START OF READ SMART DATA SECTION =3D=3D=3D SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed: read failure 90% 7376 4007996 8) In this case LBA_of_first_error=3D4007996 (not 4007967!) is different from bad sector number previousely discovered from /var/log/messages 9) again, trying to read bad sectors: $ export i=3D4007996 $ while [ $i -lt 4008006 ] #again checking 10 sectors > do echo $i > dd if=3D/dev/ad6 of=3D/dev/null bs=3D512 count=3D1 skip=3D$i > let i+=3D1 > done 4007996 dd: /dev/ad6: Input/output error 0+0 records in 0+0 records out 0 bytes transferred in 2.704641 secs (0 bytes/sec) 4007997 10) And what's more: offset of LBA_of_first_error within /dev/ad6s1d is 4007996-63-2097152=3D1910781 fsdb->findblk returns nothing: fsdb (inum: 2)> findblk 1910781 fsdb (inum: 2)> So, the puzzle is: from one hand, pkgdb -uF, /var/log/messages, fsdb point to the same bad sector (4007967) and filename this sector belongs to (and even cat /var/db/pkg/kdeutils-3.5.10_5/+CONTENTS returns Input/Output error), but low level reading of bad sector returns without a sign of error. >From the other hand, smartctl long test performed immediately after low level read test with dd gives quite another number of bad sector (4007996) which in turn doesn't belong to any file. And what makes me completely lost is that the tests in items 1)-10) were repeated two times and gave the same results! So where are 29 (4007996-4007967) sectors lost? Could anyone give me a hint where I'm wrong? TIA, Dmitry --=20 =D0=A1 =D1=83=D0=B2=D0=B0=D0=B6=D0=B5=D0=BD=D0=B8=D0=B5=D0=BC, =D0=94=D0=BC= =D0=B8=D1=82=D1=80=D0=B8=D0=B9 Best regards, Dmitry email: eingorn777@gmail.com From owner-freebsd-fs@FreeBSD.ORG Mon Jul 12 01:02:48 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CDBAD106566C for ; Mon, 12 Jul 2010 01:02:48 +0000 (UTC) (envelope-from stevenschlansker@gmail.com) Received: from mail-pw0-f54.google.com (mail-pw0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 9E0338FC15 for ; Mon, 12 Jul 2010 01:02:45 +0000 (UTC) Received: by pwj9 with SMTP id 9so1760499pwj.13 for ; Sun, 11 Jul 2010 18:02:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=TNpqvWPLXCcNv/WXPgDxOhhdi4RrLyZzvPBaqvvMN/s=; b=PuNqMGtr0tFrBlIGNBh+Tc5Km+SFEZBGz0a20mEXezRZcOq5lDshb79t9mYYV60gSe DpHaj6RN8waR7Tj5fVWpNCzD5cHM0UGJwiFOaPI2jj9l96CcxHmozQyZqvLfjPIf7gPo XZ4sWIVagLlxjceHJOJ1pJ3mspOQ2KydaQcAA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=n73GMGnyspkNhfrGZrG6sYj9OGWP4qgpYcbvCKgB7YaPdsA4fmLcGUMVUPtdTeD7Js C1EBK3rGcVluHuuzNvpGdAycN3TqQjARV/eF4WgAVfS8X0LXE4B7YpKlEFW7Bcdb4bkx HSQXsrDFhpGxA3szPYlASvNjU3Pt20KQDemBA= Received: by 10.114.81.11 with SMTP id e11mr15178895wab.140.1278896565609; Sun, 11 Jul 2010 18:02:45 -0700 (PDT) Received: from 70-7-74-157.pools.spcsdns.net (70-7-74-157.pools.spcsdns.net [70.7.74.157]) by mx.google.com with ESMTPS id s5sm59131394wak.12.2010.07.11.18.02.42 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 11 Jul 2010 18:02:44 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1078) Content-Type: text/plain; charset=us-ascii From: Steven Schlansker In-Reply-To: Date: Sun, 11 Jul 2010 18:02:44 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <40EB15F2-5479-4884-AFE4-3D26BAF2C4A7@gmail.com> References: To: S M X-Mailer: Apple Mail (2.1078) Cc: freebsd-fs@freebsd.org Subject: Re: ZFS - Unable to replace replacing drive 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: Mon, 12 Jul 2010 01:02:48 -0000 It's a total pain that it doesn't work as you expect. Last time this happened to me, I fixed it by dd'ing a zfs label from one = of the failed drives (only needed to grab a few KB, which it managed to = do even though it was broken) onto a new drive and then letting it = finish the resilver process. If your dead drives are still alive enough to grab the metadata from, = that could solve your problem. On Jul 11, 2010, at 3:38 PM, S M wrote: >=20 > Hi all, >=20 > Can anyone help with a ZFS problem I've been having? I have a single = ZFS pool as shown below: >=20 > # zpool status > pool: vault > state: DEGRADED > scrub: resilver completed after 0h8m with 0 errors on Sun Jul 11 = 22:18:27 2010 > config: >=20 > NAME STATE READ WRITE CKSUM > vault DEGRADED 0 0 0 > mirror ONLINE 0 0 0 > da0.eli ONLINE 0 0 0 > da8.eli ONLINE 0 0 0 > ad4.eli ONLINE 0 0 0 > mirror DEGRADED 0 0 0 > da1.eli ONLINE 0 0 0 10.0M = resilvered > replacing UNAVAIL 0 7.42K 0 = insufficient replicas > 176228571956779269 UNAVAIL 0 7.79K 0 was = /dev/ad6.eli > 1650754158582652028 UNAVAIL 0 7.81K 0 was = /dev/da99.eli > da9.eli ONLINE 0 0 0 10.0M = resilvered >=20 > errors: No known data errors >=20 > However I can't seem to get rid of the replacing drives. What happened = was that I tried to replace /dev/ad6.eli with /dev/da99.eli (because = ad6.eli broke) and da99.eli was also faulty and so failed the replace. >=20 > How do I get rid of them? The array is otherwise healthy.... >=20 > # zpool offline vault 176228571956779269 > cannot offline 176228571956779269: no valid replicas > # zpool offline vault 1650754158582652028 > cannot offline 1650754158582652028: no valid replicas > # zpool detach vault 1650754158582652028 > cannot detach 1650754158582652028: no valid replicas > # zpool detach vault 176228571956779269 > cannot detach 176228571956779269: no valid replicas >=20 > replace doeesn't work either. >=20 > ZDB returns: >=20 > vault > version=3D14 > name=3D'vault' > state=3D0 > txg=3D173963 > pool_guid=3D14228437791114878229 > hostid=3D4269824854 > hostname=3D'vault.internal' > vdev_tree > type=3D'root' > id=3D0 > guid=3D14228437791114878229 > children[0] > type=3D'mirror' > id=3D0 > guid=3D15203813302661836458 > metaslab_array=3D23 > metaslab_shift=3D34 > ashift=3D12 > asize=3D2000394125312 > is_log=3D0 > children[0] > type=3D'disk' > id=3D0 > guid=3D7238937831460639650 > path=3D'/dev/da0.eli' > whole_disk=3D0 > DTL=3D51 > children[1] > type=3D'disk' > id=3D1 > guid=3D14125934351009663627 > path=3D'/dev/da8.eli' > whole_disk=3D0 > DTL=3D53 > children[2] > type=3D'disk' > id=3D2 > guid=3D8553277371515810839 > path=3D'/dev/ad4.eli' > whole_disk=3D0 > DTL=3D169 > children[1] > type=3D'mirror' > id=3D1 > guid=3D14672070090293526603 > metaslab_array=3D118 > metaslab_shift=3D34 > ashift=3D12 > asize=3D2000394125312 > is_log=3D0 > children[0] > type=3D'disk' > id=3D0 > guid=3D4020825290461516758 > path=3D'/dev/da1.eli' > whole_disk=3D0 > DTL=3D123 > children[1] > type=3D'replacing' > id=3D1 > guid=3D496235429895718168 > whole_disk=3D0 > children[0] > type=3D'disk' > id=3D0 > guid=3D176228571956779269 > path=3D'/dev/ad6.eli' > whole_disk=3D0 > not_present=3D1 > DTL=3D54 > children[1] > type=3D'disk' > id=3D1 > guid=3D1650754158582652028 > path=3D'/dev/da99.eli' > whole_disk=3D0 > not_present=3D1 > DTL=3D168 > children[2] > type=3D'disk' > id=3D2 > guid=3D5694121814811722857 > path=3D'/dev/da9.eli' > whole_disk=3D0 > DTL=3D120 >=20 >=20 > uname -a: FreeBSD vault.internal 8.1-PRERELEASE FreeBSD 8.1-PRERELEASE = #4: Thu Jul 1 09:47:23 UTC 2010 = sm@vault.internal:/usr/obj/usr/src/sys/vault amd64 >=20 > How do I fix this? ZFS says that the array is degraded but it isn't = really, I just can't get rid of this. > =20 > _________________________________________________________________ > http://clk.atdmt.com/UKM/go/197222280/direct/01/ > We want to hear all your funny, exciting and crazy Hotmail stories. = Tell us now_______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" From owner-freebsd-fs@FreeBSD.ORG Mon Jul 12 07:03:12 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5C273106566B for ; Mon, 12 Jul 2010 07:03:12 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) by mx1.freebsd.org (Postfix) with ESMTP id DF9FC8FC1E for ; Mon, 12 Jul 2010 07:03:11 +0000 (UTC) Received: from elsa.codelab.cz (localhost.codelab.cz [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 5828319E02D; Mon, 12 Jul 2010 09:03:09 +0200 (CEST) Received: from [192.168.1.2] (r5bb235.net.upc.cz [86.49.61.235]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 0059119E027; Mon, 12 Jul 2010 09:03:06 +0200 (CEST) Message-ID: <4C3ABE2A.50802@quip.cz> Date: Mon, 12 Jul 2010 09:03:06 +0200 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1.10) Gecko/20100504 SeaMonkey/2.0.5 MIME-Version: 1.0 To: Dmitry Lunts References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: fsdb&smartctl&/var/log/messages 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: Mon, 12 Jul 2010 07:03:12 -0000 Dmitry Lunts wrote: > Hello,all! > The question is as follows. > 1).When I try to upgrade some port or merely execute the command pkgdb -uF > I get the error: > Input/output error - /var/db/pkg/kdeutils-3.5.10_5/+CONTENTS > > 2)$sudo cat /var/log/messages|grep DMA|tail -2 > gives: > Jul 12 03:07:06 dim007 kernel: ad6: FAILURE - READ_DMA > status=51 error=40 LBA=4007967 > Jul 12 03:07:09 dim007 kernel: ad6: FAILURE - READ_DMA > status=51 error=40 LBA=4007967 > > 3)From the output of > $cat /etc/fstab and > $sudo bsdlabel ad6s1: > # size offset fstype [fsize bsize bps/cpg] > a: 1048576 0 4.2BSD 2048 16384 8 > b: 1048576 1048576 swap > c: 100663227 0 unused 0 0 # "raw" part, don't > edit > d: 2097152 2097152 4.2BSD 2048 16384 28552 > e: 655360 4194304 4.2BSD 2048 16384 40968 > f: 37748736 4849664 4.2BSD 2048 16384 28552 > g: 58064827 42598400 4.2BSD 2048 16384 28552 > I can conclude that LBA=4007967 falls into /dev/ad6s1d partition mounted as > /var > > Next: > 4) $sudo fsdb -r /dev/ad6s1d > ** /dev/ad6s1d (NO WRITE) > Examining file system `/dev/ad6s1d' > Last Mounted on /var > current inode: directory > I=2 MODE=40755 SIZE=512 > BTIME=Jan 1 15:07:34 2009 [0 nsec] > MTIME=Jul 12 03:03:19 2010 [0 nsec] > CTIME=Jul 12 03:03:19 2010 [0 nsec] > ATIME=Jul 10 01:09:22 2010 [0 nsec] > OWNER=root GRP=wheel LINKCNT=27 FLAGS=0 BLKCNT=4 GEN=5e655284 > > Offset of bad LBA sector within /dev/ad6s1d (i.e., /var) partition is: > (bad LBA sector-63-offset of /dev/ad6s1d=4007967-63-2097152=1910752 (see the > output of bsdlabel above) > > 5) Searching for inode: > fsdb (inum: 2)>findblk 1910752 > 1910752: data block of inode 117934 > > 6)Searching for file: > $sudo find /var -inum 117934 > /var/db/pkg/kdeutils-3.5.10_5/+CONTENTS > which exactly corresponds to error message from pkgdb -uF (see item 1) > above) [...] > 10) And what's more: > offset of LBA_of_first_error within /dev/ad6s1d is > 4007996-63-2097152=1910781 > fsdb->findblk returns nothing: > fsdb (inum: 2)> findblk 1910781 > fsdb (inum: 2)> > > So, the puzzle is: > from one hand, pkgdb -uF, /var/log/messages, fsdb point to the same bad > sector (4007967) and filename > this sector belongs to > (and even cat /var/db/pkg/kdeutils-3.5.10_5/+CONTENTS returns Input/Output > error), > but low level reading of bad sector returns without a sign of error. >> From the other hand, smartctl long test performed immediately after low > level read test with dd > gives quite another number of bad sector (4007996) which in turn doesn't > belong to any file. > > And what makes me completely lost is that > the tests in items 1)-10) were repeated two times and gave the same > results! > So where are 29 (4007996-4007967) sectors lost? > Could anyone give me a hint where I'm wrong? I had similar problem in the past. You can find more about it here http://lists.freebsd.org/pipermail/freebsd-current/2010-March/015987.html Miroslav Lachman From owner-freebsd-fs@FreeBSD.ORG Mon Jul 12 09:29:56 2010 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3229E1065676; Mon, 12 Jul 2010 09:29:56 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 09C2A8FC22; Mon, 12 Jul 2010 09:29:56 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o6C9TtdN007634; Mon, 12 Jul 2010 09:29:55 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o6C9TtK8007630; Mon, 12 Jul 2010 09:29:55 GMT (envelope-from linimon) Date: Mon, 12 Jul 2010 09:29:55 GMT Message-Id: <201007120929.o6C9TtK8007630@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-amd64@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/148504: [zfs] ZFS' zpool does not allow replacing drives to be offlined or removed 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: Mon, 12 Jul 2010 09:29:56 -0000 Old Synopsis: ZFS' zpool does not allow replacing drives to be offlined or removed New Synopsis: [zfs] ZFS' zpool does not allow replacing drives to be offlined or removed Responsible-Changed-From-To: freebsd-amd64->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Mon Jul 12 09:29:43 UTC 2010 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=148504 From owner-freebsd-fs@FreeBSD.ORG Mon Jul 12 09:41:26 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 017821065695 for ; Mon, 12 Jul 2010 09:41:26 +0000 (UTC) (envelope-from freebsd-fs@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id AF5368FC27 for ; Mon, 12 Jul 2010 09:41:25 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1OYFVs-0000g1-Ge for freebsd-fs@freebsd.org; Mon, 12 Jul 2010 11:41:24 +0200 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 12 Jul 2010 11:41:24 +0200 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 12 Jul 2010 11:41:24 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-fs@freebsd.org From: Ivan Voras Date: Mon, 12 Jul 2010 11:41:27 +0200 Lines: 30 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.9) Gecko/20100518 Thunderbird/3.0.4 In-Reply-To: X-Enigmail-Version: 1.0.1 Subject: Re: ZFS - Unable to replace replacing drive 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: Mon, 12 Jul 2010 09:41:26 -0000 On 07/12/10 00:38, S M wrote: > > Hi all, > > Can anyone help with a ZFS problem I've been having? I have a single ZFS pool as shown below: > > # zpool status > pool: vault > state: DEGRADED > scrub: resilver completed after 0h8m with 0 errors on Sun Jul 11 22:18:27 2010 > config: > > NAME STATE READ WRITE CKSUM > vault DEGRADED 0 0 0 > mirror ONLINE 0 0 0 > da0.eli ONLINE 0 0 0 > da8.eli ONLINE 0 0 0 > ad4.eli ONLINE 0 0 0 > mirror DEGRADED 0 0 0 > da1.eli ONLINE 0 0 0 10.0M resilvered > replacing UNAVAIL 0 7.42K 0 insufficient replicas > 176228571956779269 UNAVAIL 0 7.79K 0 was /dev/ad6.eli > 1650754158582652028 UNAVAIL 0 7.81K 0 was /dev/da99.eli > da9.eli ONLINE 0 0 0 10.0M resilvered > > errors: No known data errors What structure is this supposed to be? A stripe of two three-way mirrors? And you did "zpool replace vault /dev/ad6.eli /dev/da99.eli" ? From owner-freebsd-fs@FreeBSD.ORG Mon Jul 12 10:20:27 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0248E1065672 for ; Mon, 12 Jul 2010 10:20:27 +0000 (UTC) (envelope-from to.my.trociny@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 7FA298FC17 for ; Mon, 12 Jul 2010 10:20:26 +0000 (UTC) Received: by bwz12 with SMTP id 12so2724743bwz.13 for ; Mon, 12 Jul 2010 03:20:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:cc:subject:references :x-comment-to:date:in-reply-to:message-id:user-agent:mime-version :content-type; bh=9mQdbyX0LPfII9xvrAwfBLOZOsm5b65sH/DSDCJ9I+A=; b=m4SBiMYqRPZ1b/EydWx1+6+45puPX2toMh7q+emHwVhZy8vAou2RjKiUqrx6qBncBV UYn1OigS09d3V7XePy1f86EsDKYm4zMOQno0B9f+THTyzF/weZDkOPwkPOeEbHHAInEG 9V5keOHDiX19ccoK6q703s3byateaimwJmP+s= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:subject:references:x-comment-to:date:in-reply-to :message-id:user-agent:mime-version:content-type; b=GIg1xViulOeYmp3UNp6twOASGGiKDISinuXqWJjl9vHhRa1/2P84BSnXlNN2UI/i4Q CEJmPmK9c6vqqDInclG1cX1lTZAcVXcrM7R6njpq3WvMpnMjzwwoTBtldlXDwS54u92i wMMfW+2ytTrsWQxmKNyhrf6kdxlksIORYrS2k= Received: by 10.204.84.230 with SMTP id k38mr10282330bkl.160.1278930025301; Mon, 12 Jul 2010 03:20:25 -0700 (PDT) Received: from localhost ([95.69.169.55]) by mx.google.com with ESMTPS id 24sm17839273bkr.19.2010.07.12.03.20.23 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 12 Jul 2010 03:20:23 -0700 (PDT) From: Mikolaj Golub To: Dmitry Lunts References: X-Comment-To: Dmitry Lunts Date: Mon, 12 Jul 2010 13:20:21 +0300 In-Reply-To: (Dmitry Lunts's message of "Mon, 12 Jul 2010 00:00:07 +0000") Message-ID: <86aapxc87u.fsf@kopusha.home.net> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-fs@freebsd.org Subject: Re: fsdb&smartctl&/var/log/messages 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: Mon, 12 Jul 2010 10:20:27 -0000 On Mon, 12 Jul 2010 00:00:07 +0000 Dmitry Lunts wrote: DL> So, the puzzle is: DL> from one hand, pkgdb -uF, /var/log/messages, fsdb point to the same bad DL> sector (4007967) and filename DL> this sector belongs to DL> (and even cat /var/db/pkg/kdeutils-3.5.10_5/+CONTENTS returns Input/Output DL> error), DL> but low level reading of bad sector returns without a sign of error. >>From the other hand, smartctl long test performed immediately after low DL> level read test with dd DL> gives quite another number of bad sector (4007996) which in turn doesn't DL> belong to any file. DL> And what makes me completely lost is that DL> the tests in items 1)-10) were repeated two times and gave the same DL> results! DL> So where are 29 (4007996-4007967) sectors lost? As for me it looks like the following might has happened. Your filesystem block size is 16384 bytes. When reading +CONTENTS fs sent a request to the driver to read a block -- starting from 4007967 sector of 16384 / 512 = 32 sectors. For one of these sectors (4007996) disk returned error. The driver reported about the error printing the address of the first sector of failed request. -- Mikolaj Golub From owner-freebsd-fs@FreeBSD.ORG Mon Jul 12 11:06:58 2010 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CBCC6106566B for ; Mon, 12 Jul 2010 11:06:58 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id B99548FC2C for ; Mon, 12 Jul 2010 11:06:58 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o6CB6wWt093983 for ; Mon, 12 Jul 2010 11:06:58 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o6CB6wv3093981 for freebsd-fs@FreeBSD.org; Mon, 12 Jul 2010 11:06:58 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 12 Jul 2010 11:06:58 GMT Message-Id: <201007121106.o6CB6wv3093981@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-fs@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-fs@FreeBSD.org 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: Mon, 12 Jul 2010 11:06:58 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/148504 fs [zfs] ZFS' zpool does not allow replacing drives to be o kern/148490 fs [zfs]: zpool attach - resilver bidirectionally, and re o kern/148368 fs [zfs] ZFS hanging forever on 8.1-PRERELEASE o kern/148204 fs [nfs] UDP NFS causes overload o kern/148138 fs [zfs] zfs raidz pool commands freeze o kern/147903 fs [zfs] [panic] Kernel panics on faulty zfs device o kern/147790 fs [zfs] zfs set acl(mode|inherit) fails on existing zfs o kern/147420 fs [ufs] [panic] ufs_dirbad, nullfs, jail panic (corrupt o kern/147292 fs [nfs] [patch] readahead missing in nfs client options o kern/146708 fs [ufs] [panic] Kernel panic in softdep_disk_write_compl o kern/146528 fs [zfs] Severe memory leak in ZFS on i386 o kern/146502 fs [nfs] FreeBSD 8 NFS Client Connection to Server o kern/146375 fs [nfs] [patch] Typos in macro variables names in sys/fs o kern/145778 fs [zfs] [panic] panic in zfs_fuid_map_id (known issue fi s kern/145712 fs [zfs] cannot offline two drives in a raidz2 configurat s kern/145424 fs [zfs] [patch] move source closer to v15 o kern/145411 fs [xfs] [panic] Kernel panics shortly after mounting an o kern/145309 fs [disklabel]: Editing disk label invalidates the whole o kern/145272 fs [zfs] [panic] Panic during boot when accessing zfs on o kern/145246 fs [ufs] dirhash in 7.3 gratuitously frees hashes when it o kern/145238 fs [zfs] [panic] kernel panic on zpool clear tank o kern/145229 fs [zfs] Vast differences in ZFS ARC behavior between 8.0 o kern/145189 fs [nfs] nfsd performs abysmally under load o kern/144929 fs [ufs] [lor] vfs_bio.c + ufs_dirhash.c o kern/144458 fs [nfs] [patch] nfsd fails as a kld p kern/144447 fs [zfs] sharenfs fsunshare() & fsshare_main() non functi o kern/144416 fs [panic] Kernel panic on online filesystem optimization s kern/144415 fs [zfs] [panic] kernel panics on boot after zfs crash o kern/144234 fs [zfs] Cannot boot machine with recent gptzfsboot code o kern/143825 fs [nfs] [panic] Kernel panic on NFS client o kern/143345 fs [ext2fs] [patch] extfs minor header cleanups to better o kern/143212 fs [nfs] NFSv4 client strange work ... o kern/143184 fs [zfs] [lor] zfs/bufwait LOR o kern/142924 fs [ext2fs] [patch] Small cleanup for the inode struct in o kern/142914 fs [zfs] ZFS performance degradation over time o kern/142878 fs [zfs] [vfs] lock order reversal o kern/142597 fs [ext2fs] ext2fs does not work on filesystems with real o kern/142489 fs [zfs] [lor] allproc/zfs LOR o kern/142466 fs Update 7.2 -> 8.0 on Raid 1 ends with screwed raid [re o kern/142401 fs [ntfs] [patch] Minor updates to NTFS from NetBSD o kern/142306 fs [zfs] [panic] ZFS drive (from OSX Leopard) causes two o kern/142068 fs [ufs] BSD labels are got deleted spontaneously o kern/141897 fs [msdosfs] [panic] Kernel panic. msdofs: file name leng o kern/141463 fs [nfs] [panic] Frequent kernel panics after upgrade fro o kern/141305 fs [zfs] FreeBSD ZFS+sendfile severe performance issues ( o kern/141091 fs [patch] [nullfs] fix panics with DIAGNOSTIC enabled o kern/141086 fs [nfs] [panic] panic("nfs: bioread, not dir") on FreeBS o kern/141010 fs [zfs] "zfs scrub" fails when backed by files in UFS2 o kern/140888 fs [zfs] boot fail from zfs root while the pool resilveri o kern/140661 fs [zfs] [patch] /boot/loader fails to work on a GPT/ZFS- o kern/140640 fs [zfs] snapshot crash o kern/140134 fs [msdosfs] write and fsck destroy filesystem integrity o kern/140068 fs [smbfs] [patch] smbfs does not allow semicolon in file o kern/139725 fs [zfs] zdb(1) dumps core on i386 when examining zpool c o kern/139715 fs [zfs] vfs.numvnodes leak on busy zfs o bin/139651 fs [nfs] mount(8): read-only remount of NFS volume does n o kern/139597 fs [patch] [tmpfs] tmpfs initializes va_gen but doesn't u o kern/139564 fs [zfs] [panic] 8.0-RC1 - Fatal trap 12 at end of shutdo o kern/139407 fs [smbfs] [panic] smb mount causes system crash if remot o kern/139363 fs [nfs] diskless root nfs mount from non FreeBSD server o kern/138790 fs [zfs] ZFS ceases caching when mem demand is high o kern/138421 fs [ufs] [patch] remove UFS label limitations o kern/138202 fs mount_msdosfs(1) see only 2Gb f kern/137037 fs [zfs] [hang] zfs rollback on root causes FreeBSD to fr o kern/136968 fs [ufs] [lor] ufs/bufwait/ufs (open) o kern/136945 fs [ufs] [lor] filedesc structure/ufs (poll) o kern/136944 fs [ffs] [lor] bufwait/snaplk (fsync) o kern/136873 fs [ntfs] Missing directories/files on NTFS volume o kern/136865 fs [nfs] [patch] NFS exports atomic and on-the-fly atomic o kern/136470 fs [nfs] Cannot mount / in read-only, over NFS o kern/135546 fs [zfs] zfs.ko module doesn't ignore zpool.cache filenam o kern/135469 fs [ufs] [panic] kernel crash on md operation in ufs_dirb o kern/135050 fs [zfs] ZFS clears/hides disk errors on reboot o kern/134491 fs [zfs] Hot spares are rather cold... o kern/133676 fs [smbfs] [panic] umount -f'ing a vnode-based memory dis o kern/133614 fs [panic] panic: ffs_truncate: read-only filesystem o kern/133174 fs [msdosfs] [patch] msdosfs must support utf-encoded int f kern/133150 fs [zfs] Page fault with ZFS on 7.1-RELEASE/amd64 while w o kern/132960 fs [ufs] [panic] panic:ffs_blkfree: freeing free frag o kern/132397 fs reboot causes filesystem corruption (failure to sync b o kern/132331 fs [ufs] [lor] LOR ufs and syncer o kern/132237 fs [msdosfs] msdosfs has problems to read MSDOS Floppy o kern/132145 fs [panic] File System Hard Crashes o kern/131441 fs [unionfs] [nullfs] unionfs and/or nullfs not combineab o kern/131360 fs [nfs] poor scaling behavior of the NFS server under lo o kern/131342 fs [nfs] mounting/unmounting of disks causes NFS to fail o bin/131341 fs makefs: error "Bad file descriptor" on the mount poin o kern/130920 fs [msdosfs] cp(1) takes 100% CPU time while copying file o kern/130229 fs [iconv] usermount fails on fs that need iconv o kern/130210 fs [nullfs] Error by check nullfs o kern/129760 fs [nfs] after 'umount -f' of a stale NFS share FreeBSD l o kern/129488 fs [smbfs] Kernel "bug" when using smbfs in smbfs_smb.c: o kern/129231 fs [ufs] [patch] New UFS mount (norandom) option - mostly o kern/129152 fs [panic] non-userfriendly panic when trying to mount(8) o kern/129059 fs [zfs] [patch] ZFS bootloader whitelistable via WITHOUT f kern/128829 fs smbd(8) causes periodic panic on 7-RELEASE o kern/127420 fs [gjournal] [panic] Journal overflow on gmirrored gjour o kern/127029 fs [panic] mount(8): trying to mount a write protected zi o kern/126287 fs [ufs] [panic] Kernel panics while mounting an UFS file o kern/125895 fs [ffs] [panic] kernel: panic: ffs_blkfree: freeing free s kern/125738 fs [zfs] [request] SHA256 acceleration in ZFS p kern/124621 fs [ext3] [patch] Cannot mount ext2fs partition f bin/124424 fs [zfs] zfs(8): zfs list -r shows strange snapshots' siz o kern/123939 fs [msdosfs] corrupts new files o kern/122380 fs [ffs] ffs_valloc:dup alloc (Soekris 4801/7.0/USB Flash o bin/122172 fs [fs]: amd(8) automount daemon dies on 6.3-STABLE i386, o bin/121898 fs [nullfs] pwd(1)/getcwd(2) fails with Permission denied o bin/121779 fs [ufs] snapinfo(8) (and related tools?) only work for t o bin/121366 fs [zfs] [patch] Automatic disk scrubbing from periodic(8 o bin/121072 fs [smbfs] mount_smbfs(8) cannot normally convert the cha f kern/120991 fs [panic] [fs] [snapshot] System crashes when manipulati o kern/120483 fs [ntfs] [patch] NTFS filesystem locking changes o kern/120482 fs [ntfs] [patch] Sync style changes between NetBSD and F f kern/119735 fs [zfs] geli + ZFS + samba starting on boot panics 7.0-B o kern/118912 fs [2tb] disk sizing/geometry problem with large array o kern/118713 fs [minidump] [patch] Display media size required for a k o bin/118249 fs mv(1): moving a directory changes its mtime o kern/118107 fs [ntfs] [panic] Kernel panic when accessing a file at N o bin/117315 fs [smbfs] mount_smbfs(8) and related options can't mount o kern/117314 fs [ntfs] Long-filename only NTFS fs'es cause kernel pani o kern/117158 fs [zfs] zpool scrub causes panic if geli vdevs detach on o bin/116980 fs [msdosfs] [patch] mount_msdosfs(8) resets some flags f o conf/116931 fs lack of fsck_cd9660 prevents mounting iso images with o kern/116913 fs [ffs] [panic] ffs_blkfree: freeing free block p kern/116608 fs [msdosfs] [patch] msdosfs fails to check mount options o kern/116583 fs [ffs] [hang] System freezes for short time when using o kern/116170 fs [panic] Kernel panic when mounting /tmp o kern/115645 fs [snapshots] [panic] lockmgr: thread 0xc4c00d80, not ex o bin/115361 fs [zfs] mount(8) gets into a state where it won't set/un o kern/114955 fs [cd9660] [patch] [request] support for mask,dirmask,ui o kern/114847 fs [ntfs] [patch] [request] dirmask support for NTFS ala o kern/114676 fs [ufs] snapshot creation panics: snapacct_ufs2: bad blo o bin/114468 fs [patch] [request] add -d option to umount(8) to detach o kern/113852 fs [smbfs] smbfs does not properly implement DFS referral o bin/113838 fs [patch] [request] mount(8): add support for relative p o bin/113049 fs [patch] [request] make quot(8) use getopt(3) and show o kern/112658 fs [smbfs] [patch] smbfs and caching problems (resolves b o kern/111843 fs [msdosfs] Long Names of files are incorrectly created o kern/111782 fs [ufs] dump(8) fails horribly for large filesystems s bin/111146 fs [2tb] fsck(8) fails on 6T filesystem o kern/109024 fs [msdosfs] mount_msdosfs: msdosfs_iconv: Operation not o kern/109010 fs [msdosfs] can't mv directory within fat32 file system o bin/107829 fs [2TB] fdisk(8): invalid boundary checking in fdisk / w o kern/106107 fs [ufs] left-over fsck_snapshot after unfinished backgro o kern/106030 fs [ufs] [panic] panic in ufs from geom when a dead disk o kern/104406 fs [ufs] Processes get stuck in "ufs" state under persist o kern/104133 fs [ext2fs] EXT2FS module corrupts EXT2/3 filesystems o kern/103035 fs [ntfs] Directories in NTFS mounted disc images appear o kern/101324 fs [smbfs] smbfs sometimes not case sensitive when it's s o kern/99290 fs [ntfs] mount_ntfs ignorant of cluster sizes o kern/97377 fs [ntfs] [patch] syntax cleanup for ntfs_ihash.c o kern/95222 fs [iso9660] File sections on ISO9660 level 3 CDs ignored o kern/94849 fs [ufs] rename on UFS filesystem is not atomic o kern/94769 fs [ufs] Multiple file deletions on multi-snapshotted fil o kern/94733 fs [smbfs] smbfs may cause double unlock o kern/93942 fs [vfs] [patch] panic: ufs_dirbad: bad dir (patch from D o kern/92272 fs [ffs] [hang] Filling a filesystem while creating a sna f kern/91568 fs [ufs] [panic] writing to UFS/softupdates DVD media in o kern/91134 fs [smbfs] [patch] Preserve access and modification time a kern/90815 fs [smbfs] [patch] SMBFS with character conversions somet o kern/88657 fs [smbfs] windows client hang when browsing a samba shar o kern/88266 fs [smbfs] smbfs does not implement UIO_NOCOPY and sendfi o kern/87859 fs [smbfs] System reboot while umount smbfs. o bin/86765 fs [patch] bsdlabel(8) assigning wrong fs type. o kern/86587 fs [msdosfs] rm -r /PATH fails with lots of small files o kern/85326 fs [smbfs] [panic] saving a file via samba to an overquot o kern/84589 fs [2TB] 5.4-STABLE unresponsive during background fsck 2 o kern/80088 fs [smbfs] Incorrect file time setting on NTFS mounted vi o kern/73484 fs [ntfs] Kernel panic when doing `ls` from the client si o bin/73019 fs [ufs] fsck_ufs(8) cannot alloc 607016868 bytes for ino o kern/71774 fs [ntfs] NTFS cannot "see" files on a WinXP filesystem o kern/68978 fs [panic] [ufs] crashes with failing hard disk, loose po o kern/65920 fs [nwfs] Mounted Netware filesystem behaves strange o kern/65901 fs [smbfs] [patch] smbfs fails fsx write/truncate-down/tr o kern/61503 fs [smbfs] mount_smbfs does not work as non-root o kern/55617 fs [smbfs] Accessing an nsmb-mounted drive via a smb expo o kern/53137 fs [ffs] [panic] background fscking causing ffs_valloc pa o kern/51685 fs [hang] Unbounded inode allocation causes kernel to loc o kern/51583 fs [nullfs] [patch] allow to work with devices and socket o kern/36566 fs [smbfs] System reboot with dead smb mount and umount o kern/33464 fs [ufs] soft update inconsistencies after system crash o kern/18874 fs [2TB] 32bit NFS servers export wrong negative values t 182 problems total. From owner-freebsd-fs@FreeBSD.ORG Mon Jul 12 11:47:27 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2A583106566C for ; Mon, 12 Jul 2010 11:47:27 +0000 (UTC) (envelope-from zw_uk@hotmail.com) Received: from bay0-omc4-s12.bay0.hotmail.com (bay0-omc4-s12.bay0.hotmail.com [65.54.190.214]) by mx1.freebsd.org (Postfix) with ESMTP id 15D728FC13 for ; Mon, 12 Jul 2010 11:47:26 +0000 (UTC) Received: from BAY150-W17 ([65.54.190.199]) by bay0-omc4-s12.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 12 Jul 2010 04:35:26 -0700 Message-ID: X-Originating-IP: [81.5.176.176] From: S M To: Date: Mon, 12 Jul 2010 11:35:27 +0000 Importance: Normal In-Reply-To: <40EB15F2-5479-4884-AFE4-3D26BAF2C4A7@gmail.com> References: , <40EB15F2-5479-4884-AFE4-3D26BAF2C4A7@gmail.com> MIME-Version: 1.0 X-OriginalArrivalTime: 12 Jul 2010 11:35:26.0859 (UTC) FILETIME=[52E365B0:01CB21B6] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: RE: ZFS - Unable to replace replacing drive 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: Mon, 12 Jul 2010 11:47:27 -0000 > What structure is this supposed to be? A stripe of two three-way mirrors= ? > And you did "zpool replace vault /dev/ad6.eli /dev/da99.eli" ? Hi Ivan and all=2C Yes=2C this was meant to be 2x vdevs which are striped=2C each vdev being a= 3 way mirror.=20 Yes=2C /dev/ad6.eli was a problem drive so I plugged /dev/da99.eli into the= LSI controller and=2C as you said=2C ran zpool replace vault /dev/ad6.eli = /dev/da99.eli. Then that drive failed too (coincidence?) but now I can't ge= t rid of the replacing drives. I've tried all manner of combinations of commands to remove them=2C even tr= ied finding another drive=2C changing device.hints to rename that as da99 (= which then comes up as FAULTED but the same problem as above happens).=20 Stephen - I had a look at dd'ing the drive to get enough zfs metadata out t= o trick zpool into accepting the drive and trying to resilver=2C but the pr= oblem is that the drive is too far gone - when I plug it in=2C it just comp= letely hangs the LSI controller=2C followed by screenfuls of geli errors an= d timeout errors. When I plug it into the motherboard controller=2C it does= n't even detect it properly. I can't even get to a point of being able to r= un seatools against it=2C so that drive is going to get replaced. One thing I've noticed is that the zfs implementation doesn't appear to lik= e using the degraded vdev=3B I thought it tended to favour blank drives to = even everything out but it seems to be using the full vdev where it can - i= s that purely because of the degraded vdev? If so is there anything I can d= o to restore it? I don't have enough drives to back up the pool and remake = it=2C and that's not a permanent fix anyway. Cheers Stu =20 _________________________________________________________________ http://clk.atdmt.com/UKM/go/197222280/direct/01/ Do you have a story that started on Hotmail? Tell us now= From owner-freebsd-fs@FreeBSD.ORG Mon Jul 12 12:25:03 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 55A00106566C for ; Mon, 12 Jul 2010 12:25:03 +0000 (UTC) (envelope-from zw_uk@hotmail.com) Received: from bay0-omc4-s17.bay0.hotmail.com (bay0-omc4-s17.bay0.hotmail.com [65.54.190.219]) by mx1.freebsd.org (Postfix) with ESMTP id 4381D8FC08 for ; Mon, 12 Jul 2010 12:25:02 +0000 (UTC) Received: from BAY150-W17 ([65.54.190.199]) by bay0-omc4-s17.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 12 Jul 2010 05:25:02 -0700 Message-ID: X-Originating-IP: [81.5.176.176] From: S M To: Date: Mon, 12 Jul 2010 12:25:02 +0000 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 12 Jul 2010 12:25:02.0468 (UTC) FILETIME=[407D4C40:01CB21BD] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: zfs on 4k sector disks 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: Mon, 12 Jul 2010 12:25:03 -0000 I found that playing with either: (sysctl) vfs.zfs.txg.write_limit_override or (boot/loader.conf) vfs.zfs.txg.timeout=3D5 (boot/loader.conf) vfs.zfs.txg.synctime=3D5 Helped with the write problem. What seems to happen is that zfs' calculatio= ns go slightly wrong if you have a lot of RAM and therefore zfs buffers too= much=2C forcing so many writes that you lose all read IO for a few seconds= .... =20 _________________________________________________________________ http://clk.atdmt.com/UKM/go/197222280/direct/01/ Do you have a story that started on Hotmail? Tell us now= From owner-freebsd-fs@FreeBSD.ORG Mon Jul 12 12:47:49 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 752CE106566B for ; Mon, 12 Jul 2010 12:47:49 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta09.westchester.pa.mail.comcast.net (qmta09.westchester.pa.mail.comcast.net [76.96.62.96]) by mx1.freebsd.org (Postfix) with ESMTP id 1F4988FC15 for ; Mon, 12 Jul 2010 12:47:48 +0000 (UTC) Received: from omta09.westchester.pa.mail.comcast.net ([76.96.62.20]) by qmta09.westchester.pa.mail.comcast.net with comcast id h0SQ1e0040SCNGk590npju; Mon, 12 Jul 2010 12:47:49 +0000 Received: from koitsu.dyndns.org ([98.248.41.155]) by omta09.westchester.pa.mail.comcast.net with comcast id h0no1e0013LrwQ23V0noBa; Mon, 12 Jul 2010 12:47:49 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id C58A19B425; Mon, 12 Jul 2010 05:47:46 -0700 (PDT) Date: Mon, 12 Jul 2010 05:47:46 -0700 From: Jeremy Chadwick To: S M Message-ID: <20100712124746.GA9328@icarus.home.lan> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-fs@freebsd.org Subject: Re: zfs on 4k sector disks 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: Mon, 12 Jul 2010 12:47:49 -0000 On Mon, Jul 12, 2010 at 12:25:02PM +0000, S M wrote: > > I found that playing with either: > > (sysctl) vfs.zfs.txg.write_limit_override > > or > > (boot/loader.conf) vfs.zfs.txg.timeout=5 > (boot/loader.conf) vfs.zfs.txg.synctime=5 > > Helped with the write problem. What seems to happen is that zfs' calculations go slightly wrong if you have a lot of RAM and therefore zfs buffers too much, forcing so many writes that you lose all read IO for a few seconds.... This has little to do with 4KB sector disks, as it applies to 512-byte sector disks too. Some references: http://lists.freebsd.org/pipermail/freebsd-fs/2009-December/007343.html http://lists.freebsd.org/pipermail/freebsd-fs/2009-December/007355.html The values chosen (in your case, "5") greatly depend on the model and type of hard disk used. I stress the word "greatly". Others reading this mail should take that into consideration. The default values (meaning out-of-the-box) for these tunables is as follows (taken from RELENG_8's source as of a few minutes ago). I'm also including what source files were used to verify said claims. For a description of what these do, see sysctl -d. vfs.zfs.txg.synctime = 5 - src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dsl_pool.c - src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/txg.c vfs.zfs.txg.timeout = 30 - src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/txg.c vfs.zfs.txg.write_limit_override = 0 - src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dsl_pool.c - src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/txg.c The defaults may vary per person, based on what source branch/tag they use (ex. RELENG_8 vs. RELENG_8_0 vs. RELENG_7) and what build date your kernel is (since what's in /usr/src might not match the running kernel). To see if these values have changed over time (e.g. in an older release they may have been different), one should refer to cvsweb or equivalent. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-fs@FreeBSD.ORG Mon Jul 12 14:51:44 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B4C61106566B for ; Mon, 12 Jul 2010 14:51:44 +0000 (UTC) (envelope-from to.my.trociny@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 3C3668FC1E for ; Mon, 12 Jul 2010 14:51:43 +0000 (UTC) Received: by bwz12 with SMTP id 12so2922761bwz.13 for ; Mon, 12 Jul 2010 07:51:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:cc:subject:references :x-comment-to:date:in-reply-to:message-id:user-agent:mime-version :content-type:content-transfer-encoding; bh=vp3wDZwshkGtKGkmVu/WSEObqJgOIXYETo9Lbe9gmlg=; b=N45PEORSih1xsPE32U2xvdn81jlco2ch1GHigEVDD+enwcwcGZzgTTSaJiE3/B2q+R 25q3TSBppF0Yomer42jS7jBhj650a09ekTvvAuY4NxSBBm+FfDea7SLSS0HgnNQq53PL 8n0i/obW3wGIiNYW8VtaZhtz2KKJVAVPpQaEk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:subject:references:x-comment-to:date:in-reply-to :message-id:user-agent:mime-version:content-type :content-transfer-encoding; b=QogmB+lpKAhdjaUkribTNGN2cEkygWV4D5S5la5k3EJL3rGVEfRDblBZI0ya9qNgiJ M+jcPF0yZlH2gcoFloHcXJfGMD9LILqFY5P6Rvy9tLHt7RrndldRoaJJ3BcMFOe3oEam 1yuFu/ENRl1U/FwuDyU23dnxONjRrlj2rO/vE= Received: by 10.204.178.146 with SMTP id bm18mr9770125bkb.99.1278946302375; Mon, 12 Jul 2010 07:51:42 -0700 (PDT) Received: from localhost ([95.69.169.55]) by mx.google.com with ESMTPS id o20sm18854122bkw.3.2010.07.12.07.51.40 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 12 Jul 2010 07:51:40 -0700 (PDT) From: Mikolaj Golub To: Dmitry Lunts References: <86aapxc87u.fsf@kopusha.home.net> X-Comment-To: Dmitry Lunts Date: Mon, 12 Jul 2010 17:51:39 +0300 In-Reply-To: (Dmitry Lunts's message of "Mon, 12 Jul 2010 15:04:07 +0400") Message-ID: <86630kda84.fsf@kopusha.home.net> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Cc: freebsd-fs@freebsd.org Subject: Re: fsdb&smartctl&/var/log/messages 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: Mon, 12 Jul 2010 14:51:44 -0000 On Mon, 12 Jul 2010 15:04:07 +0400 Dmitry Lunts wrote: DL> Mikolaj, thanks for your reply! >> As for me it looks like the following might has happened. Your filesystem >> block size is 16384 bytes. When reading +CONTENTS fs sent a request to the >> driver to read a block -- starting from 4007967 sector of 16384 / 512 = 32 >> sectors. For one of these sectors (4007996) disk returned error. The driver >> reported about the error printing the address of the first sector of failed >> request. >> >> -- >> Mikolaj Golub >> DL> Looks reasonable, but nevertheless DL> it's still unclear why fsdb->findblk /dev/ad6s1d> DL> returns nothing? Playing a little with fsdb it looks like it will find only the first 4 sectors of any inode's block (for fs with block size = 16K and fragment size = 2K), so those that belong to the first fragment of the block. DL> And one more question. What if I try to remap this bad LBA sector (with dd) DL> ? DL> Will package database be irreversibly damaged, DL> or pkgdb -uF will cure it? DL> (Sorry,I'm not sophisticated in FreeBSD very much) DL> TIA, DL> -- DL> ó Õ×ÁÖÅÎÉÅÍ, äÍÉÔÒÉÊ DL> Best regards, Dmitry DL> email: eingorn777@gmail.com -- Mikolaj Golub From owner-freebsd-fs@FreeBSD.ORG Mon Jul 12 15:03:49 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 625BC1065675 for ; Mon, 12 Jul 2010 15:03:49 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta09.emeryville.ca.mail.comcast.net (qmta09.emeryville.ca.mail.comcast.net [76.96.30.96]) by mx1.freebsd.org (Postfix) with ESMTP id 4AE038FC12 for ; Mon, 12 Jul 2010 15:03:48 +0000 (UTC) Received: from omta17.emeryville.ca.mail.comcast.net ([76.96.30.73]) by qmta09.emeryville.ca.mail.comcast.net with comcast id h1bA1e0081afHeLA933oKs; Mon, 12 Jul 2010 15:03:48 +0000 Received: from koitsu.dyndns.org ([98.248.41.155]) by omta17.emeryville.ca.mail.comcast.net with comcast id h33n1e00F3LrwQ28d33orb; Mon, 12 Jul 2010 15:03:48 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 8D0B19B425; Mon, 12 Jul 2010 08:03:47 -0700 (PDT) Date: Mon, 12 Jul 2010 08:03:47 -0700 From: Jeremy Chadwick To: Dmitry Lunts Message-ID: <20100712150347.GA12747@icarus.home.lan> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-fs@freebsd.org Subject: Re: fsdb&smartctl&/var/log/messages 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: Mon, 12 Jul 2010 15:03:49 -0000 (Lots of snipping applied) On Mon, Jul 12, 2010 at 12:00:07AM +0000, Dmitry Lunts wrote: > [...] > Input/output error - /var/db/pkg/kdeutils-3.5.10_5/+CONTENTS > [...] > > Jul 12 03:07:06 dim007 kernel: ad6: FAILURE - READ_DMA > status=51 error=40 LBA=4007967 > Jul 12 03:07:09 dim007 kernel: ad6: FAILURE - READ_DMA > status=51 error=40 LBA=4007967 > [...] > $sudo smartctl -t long /dev/ad6 > $sudo smartctl -l selftest /dev/ad6 > smartctl 5.39.1 2010-01-28 r3054 [FreeBSD 7.3-RELEASE-p1 i386] (local build) > Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net > > === START OF READ SMART DATA SECTION === > SMART Self-test log structure revision number 1 > Num Test_Description Status Remaining LifeTime(hours) > LBA_of_first_error > # 1 Extended offline Completed: read failure 90% 7376 > 4007996 Please provide the output from: smartctl -a /dev/ad6 And be sure that the formatting is retained. Your above output indicates that your mail client is wrapping at 80 characters (or around there), and makes reading the output difficult. I'm asking for this because of this statement: > [...] > but low level reading of bad sector returns without a sign of error. > [...] Thanks. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-fs@FreeBSD.ORG Mon Jul 12 19:42:16 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A850C1065673 for ; Mon, 12 Jul 2010 19:42:16 +0000 (UTC) (envelope-from to.my.trociny@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 34EE18FC0C for ; Mon, 12 Jul 2010 19:42:15 +0000 (UTC) Received: by bwz12 with SMTP id 12so3128905bwz.13 for ; Mon, 12 Jul 2010 12:42:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date :message-id:user-agent:mime-version:content-type; bh=8qHD1eDNyfCLJk3+3TP69kyrCNDzvKB9BdoDK/8nh7Y=; b=wyyoLyMbi7Df4HYTVGTuTvU86gfel6OPaHO94fWUeragD+sEVpK86awK2W9MXOpAxD Acgs45DNW5bBPPn2rCN1+UcTMaEvp2r7kUMl5zxahyc3goGNtYo1eaowat7uPqdhgYtZ q6KK8tCpAtDYsj3Hqjzs9/SpGLCZQPc2iURhg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:message-id:user-agent:mime-version :content-type; b=TsLBRF88D1FiGjp9L82rQfIyr4Ag4wly4tCFSA5bvR/Rxeeha9E6DZn4bCrzN+Oao0 OUlBgg+UT3B89C1kA9E0l9uLGcaqkfgGf5BZiC6RHC5UOXeuE5Z3yf9Q1ov04JZHCsZn 8V4NVENvTEZOqVzGt/XC4YNP+/1s/kAIXt42g= Received: by 10.204.46.23 with SMTP id h23mr10963349bkf.75.1278963734586; Mon, 12 Jul 2010 12:42:14 -0700 (PDT) Received: from localhost ([95.69.169.55]) by mx.google.com with ESMTPS id bq20sm19922209bkb.4.2010.07.12.12.42.13 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 12 Jul 2010 12:42:13 -0700 (PDT) From: Mikolaj Golub To: freebsd-fs@freebsd.org Date: Mon, 12 Jul 2010 22:42:11 +0300 Message-ID: <86tyo4bi7g.fsf@kopusha.home.net> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (berkeley-unix) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Subject: ata-disk.c:ad_init(): max_iosize might be uninitialized? 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: Mon, 12 Jul 2010 19:42:16 -0000 --=-=-= Hi, It might be a wrong list but I have not found freebsd-ata@ or freebsd-disk@ list -). I just have looked accidentally at ad_init() in dev/ata/ata-disk.c and it looks like there is at least theoretical possibility that atadev->max_iosize remains uninitialized (if ata_controlcmd(ATA_SET_MULTI) fails). Shouldn't be like in the patch below? -- Mikolaj Golub --=-=-= Content-Type: text/x-patch Content-Disposition: inline; filename=ata-disk.c.ad_init.patch Index: sys/dev/ata/ata-disk.c =================================================================== --- sys/dev/ata/ata-disk.c (revision 209954) +++ sys/dev/ata/ata-disk.c (working copy) @@ -406,6 +406,8 @@ ad_init(device_t dev) if (!ata_controlcmd(dev, ATA_SET_MULTI, 0, 0, secsperint)) atadev->max_iosize = secsperint * DEV_BSIZE; + else + atadev->max_iosize = DEV_BSIZE; } else atadev->max_iosize = DEV_BSIZE; --=-=-=-- From owner-freebsd-fs@FreeBSD.ORG Mon Jul 12 20:06:01 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9D352106566C for ; Mon, 12 Jul 2010 20:06:01 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 248848FC1E for ; Mon, 12 Jul 2010 20:06:00 +0000 (UTC) Received: by bwz12 with SMTP id 12so3142759bwz.13 for ; Mon, 12 Jul 2010 13:06:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=mobDwTrg+r/+SMBW53Fj28pWkdzu0o88pOQ3FsnQ9jA=; b=nAPPJrlY43odD2IFVj2Y9seoFOb35hlh5a+iXCJ6Szx41jyKFBHAPjL2YyRZUqIn5W l+6h8HyBVaYX8bx7J8E1Ezk/CO4vASwA1BkZHVUxlkeCUHBxNIIsQn6HXxVkvZlB6vRZ HoWQTfkDEBfLD4LF/IbrBBIeGtlsMbmMfLsR0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=i8n828DV1IBa8zv47WKssBpsP47d3zRjikJuxoafNfgfH92W67iTiWu9UjH+ueekOM JbhBtpKuhnLQRnPFhiycHHhRfdrUDDznxLUzxMaegT9XBulY2YjkaNPY0OwOyZ1F62+h mnVyge/78vdY2NMaJcFLFaBD62oiiFOzyAu3A= Received: by 10.204.178.82 with SMTP id bl18mr11041320bkb.118.1278965158299; Mon, 12 Jul 2010 13:05:58 -0700 (PDT) Received: from mavbook.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226]) by mx.google.com with ESMTPS id y2sm20007678bkx.8.2010.07.12.13.05.56 (version=SSLv3 cipher=RC4-MD5); Mon, 12 Jul 2010 13:05:56 -0700 (PDT) Sender: Alexander Motin Message-ID: <4C3B75A1.4020905@FreeBSD.org> Date: Mon, 12 Jul 2010 23:05:53 +0300 From: Alexander Motin User-Agent: Thunderbird 2.0.0.24 (X11/20100402) MIME-Version: 1.0 To: Mikolaj Golub , freebsd-fs@freebsd.org References: In-Reply-To: X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 7bit Cc: Subject: Re: ata-disk.c:ad_init(): max_iosize might be uninitialized? 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: Mon, 12 Jul 2010 20:06:01 -0000 Hi. Mikolaj Golub wrote: > It might be a wrong list but I have not found freebsd-ata@ or freebsd-disk@ > list -). > > I just have looked accidentally at ad_init() in dev/ata/ata-disk.c and it > looks like there is at least theoretical possibility that atadev->max_iosize > remains uninitialized (if ata_controlcmd(ATA_SET_MULTI) fails). Shouldn't be > like in the patch below? It is not very obvious, but it is initialized in ata_add_child(). -- Alexander Motin From owner-freebsd-fs@FreeBSD.ORG Mon Jul 12 20:33:40 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6E779106564A; Mon, 12 Jul 2010 20:33:40 +0000 (UTC) (envelope-from to.my.trociny@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 851918FC12; Mon, 12 Jul 2010 20:33:38 +0000 (UTC) Received: by bwz12 with SMTP id 12so3158382bwz.13 for ; Mon, 12 Jul 2010 13:33:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:cc:subject:references :x-comment-to:date:in-reply-to:message-id:user-agent:mime-version :content-type; bh=mHJ6eKwMq67PpXpAvn725Bvk45MUf9aTXh+YHmJEvsk=; b=ngvXb3thyWBlFSTNQnyF2+MaMdum8LZxq4YyyvYdkg5W3N373KA/bdCw7LBxeI/ueJ yK7p1Pmw+cx8Zfzpna8xrV6zxa48BKxV55apcGPVjyQqeVKyOULEWOa32hzMRojfVsPk z/qOh7jmIZ/Pq8FMWJcdk0217GQF4btNrsbVo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:subject:references:x-comment-to:date:in-reply-to :message-id:user-agent:mime-version:content-type; b=XprJwQl0iEhUp1XQPfnC+FVY2LzTVpYr/T4gA9TSNr1R5BBoXsX7UsXJITzHi1RLKl +NVft1EoeJdi2KJmJk7eHWTwldOSgeRi6xI6qRk7zwYwH0ACrQ3Bj3HsrY2bZMtx2ysY QtC0pDUs25+ysVAGBZ0eVjJuHkPfW9li8f+4w= Received: by 10.204.59.2 with SMTP id j2mr11127646bkh.199.1278966818061; Mon, 12 Jul 2010 13:33:38 -0700 (PDT) Received: from localhost ([95.69.169.55]) by mx.google.com with ESMTPS id 24sm20099699bkr.19.2010.07.12.13.33.36 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 12 Jul 2010 13:33:37 -0700 (PDT) From: Mikolaj Golub To: Alexander Motin References: <4C3B75A1.4020905@FreeBSD.org> X-Comment-To: Alexander Motin Date: Mon, 12 Jul 2010 23:33:34 +0300 In-Reply-To: <4C3B75A1.4020905@FreeBSD.org> (Alexander Motin's message of "Mon, 12 Jul 2010 23:05:53 +0300") Message-ID: <86lj9gbftt.fsf@kopusha.home.net> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-fs@freebsd.org Subject: Re: ata-disk.c:ad_init(): max_iosize might be uninitialized? 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: Mon, 12 Jul 2010 20:33:40 -0000 On Mon, 12 Jul 2010 23:05:53 +0300 Alexander Motin wrote: AM> Hi. AM> Mikolaj Golub wrote: >> It might be a wrong list but I have not found freebsd-ata@ or freebsd-disk@ >> list -). >> >> I just have looked accidentally at ad_init() in dev/ata/ata-disk.c and it >> looks like there is at least theoretical possibility that atadev->max_iosize >> remains uninitialized (if ata_controlcmd(ATA_SET_MULTI) fails). Shouldn't be >> like in the patch below? AM> It is not very obvious, but it is initialized in ata_add_child(). Ah, I see. Thank you :-). But then "else atadev->max_iosize = DEV_BSIZE;" part in ad_init() looks like unnecessary and rather confusing (it suggests that max_iosize is initialized by this funtion. -- Mikolaj Golub From owner-freebsd-fs@FreeBSD.ORG Mon Jul 12 20:37:17 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 22FF11065677 for ; Mon, 12 Jul 2010 20:37:17 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 9CE2D8FC15 for ; Mon, 12 Jul 2010 20:37:16 +0000 (UTC) Received: by bwz12 with SMTP id 12so3160487bwz.13 for ; Mon, 12 Jul 2010 13:37:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=Lunt+DetAzBOeujn+q36ZNfIghBFZie85Hi9xLvrfFc=; b=MhzdDdpx8Q+CyUryhS+nUBK8rRNkTdEyhAEQEJKYV5cS8Podj/tHiTQnB20nI4hHBE myJ9sT2SPYAsNpMEBDcxApFbMgfLvTrtSloUOavblxYSZxND6IORTGeUisqKHs4hv62u gDFsP/GsTvtJ/pFsH2D+NIog6NYuyMpw4p8xk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=OZCrH7JPQA72pJ5FADvDmMKUnB3uehgYdm1UpWk3SKLwNzHc0Q83bL1oGx3gmFuehy uefq/sSR72f5ZjOdiwN9AZ5rByRfcIpUIfc124aXiDUqzYHvG6mf2pT4oA4dTRpfaw2+ MjcBME2Ag/VkdnD9fr/Z243m1yQej5nDL+MDc= Received: by 10.204.82.130 with SMTP id b2mr10867302bkl.12.1278967035351; Mon, 12 Jul 2010 13:37:15 -0700 (PDT) Received: from mavbook.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226]) by mx.google.com with ESMTPS id f10sm20109402bkl.17.2010.07.12.13.37.13 (version=SSLv3 cipher=RC4-MD5); Mon, 12 Jul 2010 13:37:14 -0700 (PDT) Sender: Alexander Motin Message-ID: <4C3B7CF7.6090308@FreeBSD.org> Date: Mon, 12 Jul 2010 23:37:11 +0300 From: Alexander Motin User-Agent: Thunderbird 2.0.0.24 (X11/20100402) MIME-Version: 1.0 To: Mikolaj Golub References: <4C3B75A1.4020905@FreeBSD.org> <86lj9gbftt.fsf@kopusha.home.net> In-Reply-To: <86lj9gbftt.fsf@kopusha.home.net> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: ata-disk.c:ad_init(): max_iosize might be uninitialized? 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: Mon, 12 Jul 2010 20:37:17 -0000 Mikolaj Golub wrote: > On Mon, 12 Jul 2010 23:05:53 +0300 Alexander Motin wrote: > > AM> Hi. > > AM> Mikolaj Golub wrote: > >> It might be a wrong list but I have not found freebsd-ata@ or freebsd-disk@ > >> list -). > >> > >> I just have looked accidentally at ad_init() in dev/ata/ata-disk.c and it > >> looks like there is at least theoretical possibility that atadev->max_iosize > >> remains uninitialized (if ata_controlcmd(ATA_SET_MULTI) fails). Shouldn't be > >> like in the patch below? > > AM> It is not very obvious, but it is initialized in ata_add_child(). > > Ah, I see. Thank you :-). But then "else atadev->max_iosize = DEV_BSIZE;" part > in ad_init() looks like unnecessary and rather confusing (it suggests that > max_iosize is initialized by this funtion. Probably so. And thinking a bit more I've got to idea that you were not completely wrong initially. If device was reset after initial probe and then reinitialization failed, atadev->max_iosize probably should be reduced to stay on safe side. -- Alexander Motin From owner-freebsd-fs@FreeBSD.ORG Tue Jul 13 03:10:23 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EDCCE106564A for ; Tue, 13 Jul 2010 03:10:23 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta05.westchester.pa.mail.comcast.net (qmta05.westchester.pa.mail.comcast.net [76.96.62.48]) by mx1.freebsd.org (Postfix) with ESMTP id A4BC98FC17 for ; Tue, 13 Jul 2010 03:10:23 +0000 (UTC) Received: from omta09.westchester.pa.mail.comcast.net ([76.96.62.20]) by qmta05.westchester.pa.mail.comcast.net with comcast id gzRq1e0030SCNGk55FAPCe; Tue, 13 Jul 2010 03:10:23 +0000 Received: from koitsu.dyndns.org ([98.248.41.155]) by omta09.westchester.pa.mail.comcast.net with comcast id hFAN1e0013LrwQ23VFANTT; Tue, 13 Jul 2010 03:10:23 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id B35849B425; Mon, 12 Jul 2010 20:10:20 -0700 (PDT) Date: Mon, 12 Jul 2010 20:10:20 -0700 From: Jeremy Chadwick To: Dmitry Lunts Message-ID: <20100713031020.GA38051@icarus.home.lan> References: <20100712150347.GA12747@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-fs@freebsd.org Subject: Re: fsdb&smartctl&/var/log/messages 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, 13 Jul 2010 03:10:24 -0000 (Re-adding the mailing list to the CC list) On Tue, Jul 13, 2010 at 05:15:32AM +0400, Dmitry Lunts wrote: > OK. See below. The output is too long, so General SMART values are skipped. > > [...] > > ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE > 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 > 187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always - 1297 > 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 3 > 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 3 > [...] > ATA Error Count: 1287 (device log contains only the most recent five errors) > [...] And here lies your problem. You have 3 LBAs on your drive which experienced errors during their lifetime and couldn't be automatically corrected. They're labelled as "pending" until some write operations to those LBAs are attempted (and there's no guarantee that will work either (more on that later). Attribute 187 is one I haven't seen before (I don't use Seagate drives), but it indicates the number of read or write transactions to the disk itself which *could not* be auto-corrected with hardware ECC. It's a counter, so it's very possible continuous access to the bad LBAs could be responsible for the counter being so high. Now what's interesting is that your SMART self-test log indicates you actually have 4 bad LBAs: 4007996, 102121619, 110518042, and 195230321: > Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error > # 1 Extended offline Completed: read failure 90% 7391 4007996 > # 2 Extended offline Completed: read failure 90% 7376 195230321 > # 3 Extended offline Completed: read failure 90% 7369 4007996 > # 4 Extended offline Completed: read failure 90% 7346 4007996 > # 6 Extended offline Completed: read failure 90% 7329 110518042 > # 7 Selective offline Completed: read failure 90% 7302 102121619 > # 8 Extended offline Completed: read failure 90% 7301 102121619 > # 9 Extended offline Completed: read failure 90% 7297 102121619 > #10 Selective offline Completed: read failure 90% 6817 195230321 > #11 Selective offline Completed: read failure 90% 6817 195230321 > #12 Extended offline Completed: read failure 50% 6817 195230321 > #15 Extended offline Completed: read failure 50% 5035 195230321 First thing first: I hope you have backups. I realise you're trying to work out what files got damaged, but the easiest way to do that is to attempt to read the files -- try using rsync or cpdup on all the filesystems (write the data to /dev/null) and look for I/O errors. At this point my recommendation to you is simple: replace/RMA the disk. Really. You have I/O errors across three completely non-sequential areas of the disk (maybe dust?). If you don't replace the drive, you're going to end up dealing with this again in the future. I hope you've been doing backups. :-) You can (and should) also run Seagate's SeaTools for DOS utility on the drive -- do an extended/long/thorough test (which will test all the sectors). This is a vendor-specific test which often does things at a much lower level than even SMART. I'm willing to bet the test fails, or at least will give you indication of what you already know. It may also let you remap the LBAs (I know WDs utility can do this). That said, here be dragons. I'm not responsible for what happens after you try this, and I haven't done this in a very VERY long time. Have you tried writing zeros over the LBA where the bad blocks are located? This often will get the drive to attempt a remap. E.g.: dd if=/dev/zero of=/dev/ad6 bs=512 count=1 seek={whatever} sync Be sure to note the of= parameter there refers to the entire drive and not a slice. If it does work, both Attribute 197 and 198 should change to 0. Be sure to run "smartctl -t offline /dev/ad6" too, since some Offline attributes don't always get updated. Also, your calculation formula earlier contains "-63" which I believe is due to the offset of the slices. Except in your bsdlabel output, the "c" slice actually starts at 0, not 63. Are you sure this formula is correct? Let me know what becomes of all this, I'm highly interested. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-fs@FreeBSD.ORG Wed Jul 14 12:26:42 2010 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9AEDD106564A; Wed, 14 Jul 2010 12:26:42 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 72B1B8FC0A; Wed, 14 Jul 2010 12:26:42 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o6ECQgbV077901; Wed, 14 Jul 2010 12:26:42 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o6ECQg8m077897; Wed, 14 Jul 2010 12:26:42 GMT (envelope-from linimon) Date: Wed, 14 Jul 2010 12:26:42 GMT Message-Id: <201007141226.o6ECQg8m077897@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: bin/148296: [zfs] [loader] [patch] Very slow probe in /usr/src/sys/boot/zfs/zfs.c 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: Wed, 14 Jul 2010 12:26:42 -0000 Old Synopsis: [zfs] [loader] Very slow probe in /usr/src/sys/boot/zfs/zfs.c New Synopsis: [zfs] [loader] [patch] Very slow probe in /usr/src/sys/boot/zfs/zfs.c Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Wed Jul 14 12:26:15 UTC 2010 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=148296 From owner-freebsd-fs@FreeBSD.ORG Wed Jul 14 13:10:03 2010 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EBBBC1065741 for ; Wed, 14 Jul 2010 13:10:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id EEC3B8FC1B for ; Wed, 14 Jul 2010 13:10:02 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o6EDA2Cg014071 for ; Wed, 14 Jul 2010 13:10:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o6EDA2xH014069; Wed, 14 Jul 2010 13:10:02 GMT (envelope-from gnats) Date: Wed, 14 Jul 2010 13:10:02 GMT Message-Id: <201007141310.o6EDA2xH014069@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Andriy Gapon Cc: Subject: Re: bin/148296: [zfs] [loader] [patch] Very slow probe in /usr/src/sys/boot/zfs/zfs.c X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Andriy Gapon List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jul 2010 13:10:04 -0000 The following reply was made to PR bin/148296; it has been noted by GNATS. From: Andriy Gapon To: bug-followup@freebsd.org, olgeni@freebsd.org Cc: Subject: Re: bin/148296: [zfs] [loader] [patch] Very slow probe in /usr/src/sys/boot/zfs/zfs.c Date: Wed, 14 Jul 2010 16:07:56 +0300 Another thing that most likely can be improved - if the whole disk is found to be a vdev of a ZFS pool, then it doesn't make sense to try to probe partitions/slices on the disk. Or does it? But that's an extra. The patch looks perfect. -- Andriy Gapon From owner-freebsd-fs@FreeBSD.ORG Wed Jul 14 14:40:05 2010 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4B50D1065673 for ; Wed, 14 Jul 2010 14:40:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 214F08FC20 for ; Wed, 14 Jul 2010 14:40:05 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o6EEe5bk091927 for ; Wed, 14 Jul 2010 14:40:05 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o6EEe5QP091926; Wed, 14 Jul 2010 14:40:05 GMT (envelope-from gnats) Date: Wed, 14 Jul 2010 14:40:05 GMT Message-Id: <201007141440.o6EEe5QP091926@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Jimmy Olgeni Cc: Subject: Re: bin/148296: [zfs] [loader] [patch] Very slow probe in /usr/src/sys/boot/zfs/zfs.c X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Jimmy Olgeni List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jul 2010 14:40:05 -0000 The following reply was made to PR bin/148296; it has been noted by GNATS. From: Jimmy Olgeni To: Andriy Gapon Cc: bug-followup@FreeBSD.org Subject: Re: bin/148296: [zfs] [loader] [patch] Very slow probe in /usr/src/sys/boot/zfs/zfs.c Date: Wed, 14 Jul 2010 16:15:49 +0200 (CEST) Hello, This should do it, but I don't have the right configuration to test it now. However, the "else continue" should bail out of the loop if a vdev was spotted in the top level device. --- zfs.c.orig 2010-06-14 04:09:06.000000000 +0200 +++ zfs.c 2010-07-14 16:04:49.808159404 +0200 @@ -412,16 +412,23 @@ */ if (vdev_probe(vdev_read, (void*) (uintptr_t) fd, 0)) close(fd); + else + continue; + + for (slice = 1; slice <= 4; slice++) { + sprintf(devname, "disk%ds%d:", unit, slice); + fd = open(devname, O_RDONLY); + if (fd == -1) + continue; + if (vdev_probe(vdev_read, (void*) (uintptr_t) fd, 0)) + close(fd); + } for (slice = 1; slice <= 128; slice++) { sprintf(devname, "disk%dp%d:", unit, slice); fd = open(devname, O_RDONLY); - if (fd == -1) { - sprintf(devname, "disk%ds%d:", unit, slice); - fd = open(devname, O_RDONLY); - if (fd == -1) - continue; - } + if (fd == -1) + break; if (vdev_probe(vdev_read, (void*) (uintptr_t) fd, 0)) close(fd); } -- jimmy From owner-freebsd-fs@FreeBSD.ORG Wed Jul 14 15:40:04 2010 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 871EA1065672 for ; Wed, 14 Jul 2010 15:40:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 5CE778FC15 for ; Wed, 14 Jul 2010 15:40:04 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o6EFe46g042957 for ; Wed, 14 Jul 2010 15:40:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o6EFe4gV042956; Wed, 14 Jul 2010 15:40:04 GMT (envelope-from gnats) Date: Wed, 14 Jul 2010 15:40:04 GMT Message-Id: <201007141540.o6EFe4gV042956@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: "Andrey V. Elsukov" Cc: Subject: Re: bin/148296: [zfs] [loader] [patch] Very slow probe in /usr/src/sys/boot/zfs/zfs.c X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Andrey V. Elsukov" List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jul 2010 15:40:04 -0000 The following reply was made to PR bin/148296; it has been noted by GNATS. From: "Andrey V. Elsukov" To: bug-followup@FreeBSD.org, olgeni@freebsd.org Cc: Subject: Re: bin/148296: [zfs] [loader] [patch] Very slow probe in /usr/src/sys/boot/zfs/zfs.c Date: Wed, 14 Jul 2010 19:35:32 +0400 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig1C378CA0ECE91BE4A07DCA95 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable Hi, just one note - user can create partition that doesn't start from 1. For example: # mdconfig -s 100m # gpart create -s gpt md0 # gpart add -i 5 -t freebsd-zfs md0 --=20 WBR, Andrey V. Elsukov --------------enig1C378CA0ECE91BE4A07DCA95 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iQEcBAEBAgAGBQJMPdlOAAoJEAHF6gQQyKF6+7YH/RGODEt2ighgrGuDMsVO13MZ rBrHB94RQb41yPijQeIC5tp41q/KyqesPBHZLkIMjTk9HmzdhobH6RPHpdn9iV9I SEmsJKWTDM3NMGCnE4HwsrrUIoeNI98AqkoqVVWslB48vYH4GPe7tkR0t5WqHKkk rGULOhYvM/ctT8Bqrz5GUSjLuPJDJy1NUBDnzszHF223TLjQUNGFnHL9mxfuQji3 yaTs8pLp/lgaOYZe/7jxzuxe2/w2tntPCGksqI+h+/8LVRTf6/YVdh99Q/Pen19t WrNBRPZBT3KO2YQzGFoQtxSTe76bzmuBxNB20MsLYtu5jqvmpwxQBuDJ2tuGAB8= =Ida+ -----END PGP SIGNATURE----- --------------enig1C378CA0ECE91BE4A07DCA95-- From owner-freebsd-fs@FreeBSD.ORG Wed Jul 14 16:10:04 2010 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B5C7C106566C for ; Wed, 14 Jul 2010 16:10:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id A51B78FC1D for ; Wed, 14 Jul 2010 16:10:04 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o6EGA4js067823 for ; Wed, 14 Jul 2010 16:10:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o6EGA44P067822; Wed, 14 Jul 2010 16:10:04 GMT (envelope-from gnats) Date: Wed, 14 Jul 2010 16:10:04 GMT Message-Id: <201007141610.o6EGA44P067822@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Alvin Poon Cc: Subject: Re: kern/148490: [zfs]: zpool attach - resilver bidirectionally, and reports incorrect time X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Alvin Poon List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jul 2010 16:10:04 -0000 The following reply was made to PR kern/148490; it has been noted by GNATS. From: Alvin Poon To: Martin Matuska Cc: bug-followup@FreeBSD.org Subject: Re: kern/148490: [zfs]: zpool attach - resilver bidirectionally, and reports incorrect time Date: Wed, 14 Jul 2010 23:41:24 +0800 Thanks Martin for the info. I'm just wondering... does this problem affect the integrity of the data = on the mirror at all? I mean... did it actually perform a = bi-directional resilvering? Could it have corrupted my data? Alvin On 12 Jul 2010, at 5:11 AM, Martin Matuska wrote: > The fix for this problem is part of the upcoming upgrade of ZFS to = v15. > A patch for 8-STABLE and 8.1-RELEASE users will be provided. Alvin Poon aspoon@gmail.com From owner-freebsd-fs@FreeBSD.ORG Wed Jul 14 21:40:03 2010 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ECA1C106566C for ; Wed, 14 Jul 2010 21:40:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id DC1CF8FC0C for ; Wed, 14 Jul 2010 21:40:03 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o6ELe3Nm050416 for ; Wed, 14 Jul 2010 21:40:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o6ELe3Gv050415; Wed, 14 Jul 2010 21:40:03 GMT (envelope-from gnats) Date: Wed, 14 Jul 2010 21:40:03 GMT Message-Id: <201007142140.o6ELe3Gv050415@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Martin Matuska Cc: Subject: Re: kern/148490: [zfs]: zpool attach - resilver bidirectionally, and reports incorrect time X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Martin Matuska List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jul 2010 21:40:04 -0000 The following reply was made to PR kern/148490; it has been noted by GNATS. From: Martin Matuska To: Alvin Poon Cc: bug-followup@FreeBSD.org Subject: Re: kern/148490: [zfs]: zpool attach - resilver bidirectionally, and reports incorrect time Date: Wed, 14 Jul 2010 23:33:28 +0200 No, there is no data corruption. Just some data is read from the source drive and then written to both drives instead only to the resilvering drive (this is actually a waste of resources). Dňa 14. 7. 2010 17:41, Alvin Poon wrote / napísal(a): > Thanks Martin for the info. > > I'm just wondering... does this problem affect the integrity of the data on the mirror at all? I mean... did it actually perform a bi-directional resilvering? Could it have corrupted my data? > > Alvin > > On 12 Jul 2010, at 5:11 AM, Martin Matuska wrote: > > >> The fix for this problem is part of the upcoming upgrade of ZFS to v15. >> A patch for 8-STABLE and 8.1-RELEASE users will be provided. >> > Alvin Poon > aspoon@gmail.com > > > > From owner-freebsd-fs@FreeBSD.ORG Thu Jul 15 06:49:09 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 659F11065678 for ; Thu, 15 Jul 2010 06:49:09 +0000 (UTC) (envelope-from word-bounces@dcomp.com) Received: from rs1.vitalnews.com (rs1.vitalnews.com [66.216.91.152]) by mx1.freebsd.org (Postfix) with ESMTP id 159C78FC1D for ; Thu, 15 Jul 2010 06:49:08 +0000 (UTC) Received: (qmail 23160 invoked from network); 15 Jul 2010 01:22:27 -0500 Received: from localhost (HELO 130954-app1.vitalnews.com) (127.0.0.1) by localhost with SMTP; 15 Jul 2010 01:22:27 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit From: word-bounces@dcomp.com To: freebsd-fs@freebsd.org Message-ID: Date: Thu, 15 Jul 2010 01:22:22 -0500 Precedence: bulk X-BeenThere: word@dcomp.com X-Mailman-Version: 2.1.5 X-List-Administrivia: yes Sender: word-bounces@dcomp.com Errors-To: word-bounces@dcomp.com Subject: Your message to Word awaits moderator approval X-BeenThere: freebsd-fs@freebsd.org List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Jul 2010 06:49:09 -0000 Your mail to 'Word' with the subject Mail System Error - Returned Mail Is being held until the list moderator can review it for approval. The reason it is being held: Post by non-member to a members-only list Either the message will get posted to the list, or you will receive notification of the moderator's decision. If you would like to cancel this posting, please visit the following URL: http://lists.dcomp.com/mailman/confirm/word/7240f7e7f2319d6cb97fecae616e73d91ec1ddea From owner-freebsd-fs@FreeBSD.ORG Thu Jul 15 08:50:03 2010 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EDAFD1065673 for ; Thu, 15 Jul 2010 08:50:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id C35DA8FC1C for ; Thu, 15 Jul 2010 08:50:03 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o6F8o3SB061693 for ; Thu, 15 Jul 2010 08:50:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o6F8o3Aj061692; Thu, 15 Jul 2010 08:50:03 GMT (envelope-from gnats) Date: Thu, 15 Jul 2010 08:50:03 GMT Message-Id: <201007150850.o6F8o3Aj061692@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: Andriy Gapon Cc: Subject: Re: bin/148296: [zfs] [loader] [patch] Very slow probe in /usr/src/sys/boot/zfs/zfs.c X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Andriy Gapon List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Jul 2010 08:50:04 -0000 The following reply was made to PR bin/148296; it has been noted by GNATS. From: Andriy Gapon To: bug-followup@FreeBSD.org, olgeni@FreeBSD.org Cc: Subject: Re: bin/148296: [zfs] [loader] [patch] Very slow probe in /usr/src/sys/boot/zfs/zfs.c Date: Thu, 15 Jul 2010 11:46:31 +0300 The last point is a good one. Perhaps the probe code should delve into the lower-level code and directly examine GPT in memory... -- Andriy Gapon From owner-freebsd-fs@FreeBSD.ORG Thu Jul 15 13:20:42 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1C96F1065673 for ; Thu, 15 Jul 2010 13:20:42 +0000 (UTC) (envelope-from rincebrain@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id DC3198FC0C for ; Thu, 15 Jul 2010 13:20:41 +0000 (UTC) Received: by iwn35 with SMTP id 35so1200041iwn.13 for ; Thu, 15 Jul 2010 06:20:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=ocoQ95ktlbx//VzjD8c3d9WMxdeP+eshSV7Eu5sV+8s=; b=IFVoxa53O6FbVbF4eTtYLC9PIThyZ6hliudsA1QtEvd/qY6z48E3yIotOYg/MMWzxs A1E1+YNQ/T0y0SwhMZwgO1EaHc1JKjU53Tbi+XdHqDODItUQ35M3ngtzjTT/kkFgdXaC gcgoPNWEslOk8OstkqciqJw3pTwmmv5Qshx/8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=pJC3yF6lqzfv9WQDb70StBVDjo4K6O2m8NuEOn464yg0rFdoEMXC6bjlK7DwqXiyIC nzveGLEr7InTc3ny3Y5JSkCyAulaE9A5M2EIJ4c0jcRHOzq1Sd3yiNXjN7CqHPVlvCDn s1mO8Kje5uN/QaDQLLR7KehNZqMZA6QGjN62A= MIME-Version: 1.0 Received: by 10.231.160.17 with SMTP id l17mr14557738ibx.102.1279200041017; Thu, 15 Jul 2010 06:20:41 -0700 (PDT) Received: by 10.231.192.134 with HTTP; Thu, 15 Jul 2010 06:20:40 -0700 (PDT) Date: Thu, 15 Jul 2010 09:20:40 -0400 Message-ID: From: Rich To: freebsd-fs Content-Type: text/plain; charset=ISO-8859-1 Subject: zpool scrub stops making progress after a period of time? 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: Thu, 15 Jul 2010 13:20:42 -0000 Hey world, I've got an AMD64 system on SVN r209893 of 8.1, with a standard GENERIC config [except that DDB and DTRACE are turned on]. I've got a 10-disk RAID-Z2, made on 8.0-RELEASE, that had two disks in it fault, one after another. I did a zpool replace on each of them, and it was happily resilvering for about 12 hours, and got to 25% done at 12 hours. I'll let the following output of zpool status speak for itself: # zpool status -v pool: bukkit state: DEGRADED status: One or more devices has experienced an error resulting in data corruption. Applications may be affected. action: Restore the file in question if possible. Otherwise restore the entire pool from backup. see: http://www.sun.com/msg/ZFS-8000-8A scrub: resilver in progress for 23h15m, 25.16% done, 69h11m to go config: NAME STATE READ WRITE CKSUM bukkit DEGRADED 0 0 28 raidz2 DEGRADED 0 0 56 replacing DEGRADED 0 0 0 da1 FAULTED 0 244K 0 corrupted data da11 ONLINE 0 0 0 274G resilvered da9 ONLINE 0 0 0 333M resilvered da1 ONLINE 0 0 0 348M resilvered da8 ONLINE 0 0 0 333M resilvered da0 ONLINE 0 0 0 348M resilvered replacing DEGRADED 0 0 0 12471449581279369829 FAULTED 0 234K 0 was /dev/da7 da2 ONLINE 0 0 0 274G resilvered da6 ONLINE 0 0 0 348M resilvered da10 ONLINE 0 0 0 333M resilvered da5 ONLINE 0 0 0 349M resilvered da7 ONLINE 0 0 0 333M resilvered So, 12 hours have progressed, and the resilver hasn't. zpool iostat 1 reports activity whenever I do any IO on any of the filesystems contained in the pool, but otherwise is just a straight line of 0 activity. dmesg has nothing interesting - the last messages in it are from when I inserted the replacement disks and it noted the secondary GPT tables were wrong. I could restart it, but it's not clear to me that this would help anything. Thanks, - Rich From owner-freebsd-fs@FreeBSD.ORG Fri Jul 16 11:00:10 2010 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C60701065679; Fri, 16 Jul 2010 11:00:10 +0000 (UTC) (envelope-from jh@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 821AC8FC23; Fri, 16 Jul 2010 11:00:10 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o6GB044B028784; Fri, 16 Jul 2010 11:00:04 GMT (envelope-from jh@freefall.freebsd.org) Received: (from jh@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o6GB04ux028780; Fri, 16 Jul 2010 11:00:04 GMT (envelope-from jh) Date: Fri, 16 Jul 2010 11:00:04 GMT Message-Id: <201007161100.o6GB04ux028780@freefall.freebsd.org> To: plosher@isc.org, jh@FreeBSD.org, freebsd-fs@FreeBSD.org, jh@FreeBSD.org From: jh@FreeBSD.org Cc: Subject: Re: kern/53137: [ffs] [panic] background fscking causing ffs_valloc panic. 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: Fri, 16 Jul 2010 11:00:10 -0000 Synopsis: [ffs] [panic] background fscking causing ffs_valloc panic. State-Changed-From-To: open->feedback State-Changed-By: jh State-Changed-When: Fri Jul 16 10:59:27 UTC 2010 State-Changed-Why: Is this still a problem for you? Responsible-Changed-From-To: freebsd-fs->jh Responsible-Changed-By: jh Responsible-Changed-When: Fri Jul 16 10:59:27 UTC 2010 Responsible-Changed-Why: Track. http://www.freebsd.org/cgi/query-pr.cgi?pr=53137 From owner-freebsd-fs@FreeBSD.ORG Fri Jul 16 11:18:05 2010 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 94250106564A; Fri, 16 Jul 2010 11:18:05 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 6C9888FC23; Fri, 16 Jul 2010 11:18:05 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o6GBI5HP046324; Fri, 16 Jul 2010 11:18:05 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o6GBI5We046320; Fri, 16 Jul 2010 11:18:05 GMT (envelope-from linimon) Date: Fri, 16 Jul 2010 11:18:05 GMT Message-Id: <201007161118.o6GBI5We046320@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/148655: [zfs] Booting from a degraded raidz no longer works in 8-STABLE [regression] 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: Fri, 16 Jul 2010 11:18:05 -0000 Synopsis: [zfs] Booting from a degraded raidz no longer works in 8-STABLE [regression] Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Fri Jul 16 11:17:49 UTC 2010 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=148655 From owner-freebsd-fs@FreeBSD.ORG Fri Jul 16 17:55:57 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D280B106564A for ; Fri, 16 Jul 2010 17:55:57 +0000 (UTC) (envelope-from joey@mingrone.org) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 6EBA38FC12 for ; Fri, 16 Jul 2010 17:55:57 +0000 (UTC) Received: by bwz12 with SMTP id 12so1489223bwz.13 for ; Fri, 16 Jul 2010 10:55:56 -0700 (PDT) MIME-Version: 1.0 Received: by 10.204.29.17 with SMTP id o17mr1152459bkc.208.1279301603631; Fri, 16 Jul 2010 10:33:23 -0700 (PDT) Received: by 10.204.118.197 with HTTP; Fri, 16 Jul 2010 10:33:23 -0700 (PDT) Date: Fri, 16 Jul 2010 14:33:23 -0300 Message-ID: From: Joey Mingrone To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=UTF-8 Subject: journal and software raid using gmirror and gjournal 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: Fri, 16 Jul 2010 17:55:57 -0000 Hi, I'm attempting to setup a storage server with mirroring and journalled filesystems using 1TB drives. Initially I did the following: sysctl kern.geom.debugflags=17 dd if=/dev/zero of=/dev/ad8 bs=1k count=1 dd if=/dev/zero of=/dev/ad10 bs=1k count=1 gmirror label -vb round-robin gm0 /dev/ad8 gmirror load gjournal label /dev/mirror/gm0 gjournal load newfs -O 2 -J /dev/mirror/gm0.journal mount /dev/mirror/gm0.journal /mnt/mirror2 gmirror insert gm0 /dev/ad10 ,but read in the archives there are potential issues with the labeling. Does anyone have any suggestions (or references to documentation) describing how this could be done? Are the GEOM parts for doing this sufficiently mature to consider this safe? This did seem to be working, but when I did a dump I got kernel panics like others who have posted recently. Thanks, J. Mingrone From owner-freebsd-fs@FreeBSD.ORG Sat Jul 17 19:54:10 2010 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 72A081065672; Sat, 17 Jul 2010 19:54:10 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 497498FC08; Sat, 17 Jul 2010 19:54:10 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o6HJsAI3097504; Sat, 17 Jul 2010 19:54:10 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o6HJsAhE097500; Sat, 17 Jul 2010 19:54:10 GMT (envelope-from linimon) Date: Sat, 17 Jul 2010 19:54:10 GMT Message-Id: <201007171954.o6HJsAhE097500@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/148709: [zfs] [panic] running du with zfs filesystem with sharesmb=on cause panic zfs_fuid_map_id 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: Sat, 17 Jul 2010 19:54:10 -0000 Old Synopsis: running du with zfs filesystem with sharesmb=on cause panic zfs_fuid_map_id New Synopsis: [zfs] [panic] running du with zfs filesystem with sharesmb=on cause panic zfs_fuid_map_id Responsible-Changed-From-To: freebsd-bugs->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Sat Jul 17 19:53:53 UTC 2010 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=148709