From owner-freebsd-fs@FreeBSD.ORG Mon Mar 3 11:07:07 2008 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 135E2106571D for ; Mon, 3 Mar 2008 11:07:07 +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 08E2A8FC25 for ; Mon, 3 Mar 2008 11:07:07 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m23B76ZX022029 for ; Mon, 3 Mar 2008 11:07:06 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m23B76au022025 for freebsd-fs@FreeBSD.org; Mon, 3 Mar 2008 11:07:06 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 3 Mar 2008 11:07:06 GMT Message-Id: <200803031107.m23B76au022025@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, 03 Mar 2008 11:07:07 -0000 Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/112658 fs [smbfs] [patch] smbfs and caching problems (resolves b o kern/114676 fs [ufs] snapshot creation panics: snapacct_ufs2: bad blo o kern/116170 fs [panic] Kernel panic when mounting /tmp o bin/121072 fs [smbfs] mount_smbfs(8) cannot normally convert the cha 4 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/114847 fs [ntfs] [patch] [request] dirmask support for NTFS ala o bin/118249 fs mv(1): moving a directory changes its mtime 2 problems total. From owner-freebsd-fs@FreeBSD.ORG Mon Mar 3 17:37:38 2008 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 5DC2E106567D; Mon, 3 Mar 2008 17:37:38 +0000 (UTC) (envelope-from peter.schuller@infidyne.com) Received: from smtp.infidyne.com (ds9.infidyne.com [88.80.6.206]) by mx1.freebsd.org (Postfix) with ESMTP id 25F1D8FC1C; Mon, 3 Mar 2008 17:37:37 +0000 (UTC) (envelope-from peter.schuller@infidyne.com) Received: from c-a916e555.03-51-73746f3.cust.bredbandsbolaget.se (c-a916e555.03-51-73746f3.cust.bredbandsbolaget.se [85.229.22.169]) by smtp.infidyne.com (Postfix) with ESMTP id 18ABC75992; Mon, 3 Mar 2008 18:37:36 +0100 (CET) From: Peter Schuller To: freebsd-current@freebsd.org Date: Mon, 3 Mar 2008 18:39:03 +0100 User-Agent: KMail/1.9.7 References: <200802251859.05045.peter.schuller@infidyne.com> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart4929578.WbFGbps5N0"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200803031839.11656.peter.schuller@infidyne.com> Cc: freebsd-fs@freebsd.org, Ivan Voras Subject: Re: ZFS lockup in "zfs" state 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, 03 Mar 2008 17:37:38 -0000 --nextPart4929578.WbFGbps5N0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline > >> I also saw this a couple of days ago (first time for me) on 1 7.0-RCX > >> (not sure if it was RC1 or RC2, and I can't log in to the machine right > >> now). This was recently after upgrading it from an older CURRENT from > >> september. > >> > >> The machine is amd64, 4 GB of RAM, with a single three-way mirror pool. > > > > With prefetch disabled, arc size upped to 800 megs, and kmem size upped > > to 1.2 gb (IIRC). > > +1, happened again, this time mysql was the trigger. I'll try with the > ZIL disabled. I also saw it again about a day ago. This makes it twice within a few weeks= =20 after upgrading to 7.0-RCX, after running for months without this problem=20 before that. *If* this is indicative that the problem was introcuded, it would then put = it=20 somewhere in the 2007-09 - 2008-02 neighborhood. Not sure if other people s= aw=20 this prior to 2007-09? =2D-=20 / Peter Schuller PGP userID: 0xE9758B7D or 'Peter Schuller ' Key retrieval: Send an E-Mail to getpgpkey@scode.org E-Mail: peter.schuller@infidyne.com Web: http://www.scode.org --nextPart4929578.WbFGbps5N0 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQBHzDe/DNor2+l1i30RApvyAJ94vZNbZ/NQQpwm1yI0NWunX/ahDACgwbdX VTH0OlvBQRkQaZ/SNprzRQs= =2KnH -----END PGP SIGNATURE----- --nextPart4929578.WbFGbps5N0-- From owner-freebsd-fs@FreeBSD.ORG Mon Mar 3 20:12:41 2008 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 AE202106566B; Mon, 3 Mar 2008 20:12:41 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from hosted.kievnet.com (hosted.kievnet.com [193.138.144.10]) by mx1.freebsd.org (Postfix) with ESMTP id 7155E8FC19; Mon, 3 Mar 2008 20:12:41 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from [91.193.172.111] by hosted.kievnet.com with esmtpa (Exim 4.62) (envelope-from ) id 1JWGcm-000Kc2-5c; Mon, 03 Mar 2008 21:47:00 +0200 Message-ID: <47CC55B0.4020607@icyb.net.ua> Date: Mon, 03 Mar 2008 21:46:56 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.9 (X11/20071208) MIME-Version: 1.0 To: Poul-Henning Kamp References: <889.1203600472@critter.freebsd.dk> In-Reply-To: <889.1203600472@critter.freebsd.dk> Content-Type: text/plain; charset=KOI8-U Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: newfs_msdos and dvd-ram (fwsectors, fwheads) 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, 03 Mar 2008 20:12:41 -0000 on 21/02/2008 15:27 Poul-Henning Kamp said the following: > In message <47BD6F39.7080105@icyb.net.ua>, Andriy Gapon writes: >> 2) fake those properties in newfs_msdof; >> benefit: this would help with other physical devices that can host >> FAT; > > This is the way to do it, but it might make sense to make a library > routine do it, to get consistent behaviour. I opened a PR for this approach in a simple form. http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/121182 What could be a good place to put thing for re-use/sharing? libutil? -- Andriy Gapon From owner-freebsd-fs@FreeBSD.ORG Tue Mar 4 13:25:42 2008 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 9690B1065672 for ; Tue, 4 Mar 2008 13:25:42 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from ns.trinitel.com (186.161.36.72.static.reverse.ltdomains.com [72.36.161.186]) by mx1.freebsd.org (Postfix) with ESMTP id 631C88FC1B for ; Tue, 4 Mar 2008 13:25:42 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from proton.storspeed.com (209-163-168-124.static.tenantsolutions.net [209.163.168.124] (may be forged)) (authenticated bits=0) by ns.trinitel.com (8.14.1/8.14.1) with ESMTP id m24DPats041502; Tue, 4 Mar 2008 07:25:40 -0600 (CST) (envelope-from anderson@freebsd.org) Message-ID: <47CD4DCF.5070505@freebsd.org> Date: Tue, 04 Mar 2008 07:25:35 -0600 From: Eric Anderson User-Agent: Thunderbird 2.0.0.12 (Macintosh/20080213) MIME-Version: 1.0 To: Joe Peterson References: <47ACD7D4.5050905@skyrush.com> <47ACDE82.1050100@skyrush.com> <20080208173517.rdtobnxqg4g004c4@www.wolves.k12.mo.us> <47ACF0AE.3040802@skyrush.com> <1202747953.27277.7.camel@buffy.york.ac.uk> <47B0A45C.4090909@skyrush.com> In-Reply-To: <47B0A45C.4090909@skyrush.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.2 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on ns.trinitel.com Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Analysis of disk file block with ZFS checksum error 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, 04 Mar 2008 13:25:42 -0000 Joe Peterson wrote: > Gavin Atkinson wrote: >> Are the datestamps (Thu Jan 24 23:20:58 2008) found within the corrupt >> block before or after the datestamp of the file it was found within? >> i.e. was the corrupt block on the disk before or after the mp3 was >> written there? > > Hi Gavin, those dated are later than the original copy (I do not have > the file timestamps to prove this, but according to my email record, I > am pretty sure of this). So the corrupt block is later than the > original write. > > If this is the case, I assume that the block got written, by mistake, > into the middle of the mp3 file. Someone else suggested that it could > be caused by a bad transfer block number or bad drive command (corrupted > on the way to the drive, since these are not checksummed in the > hardware). If the block went to the wrong place, AND if it was a HW > glitch, I suppose the best ZFS could then do is retry the write (if its > failure was even detected - still not sure if ZFS does a re-check of the > disk data checksum after the disk write), not knowing until the later > scrub that the block had corrupted a file. > > I think that anything is possible, but I know I was getting periodic DMA > timeouts, etc. around that time. I hesitate, although it is tempting, > to use this evidence to focus blame purely on bad HW, given that others > seem to be seeing DMA problems too, and there is reasonable doubt > whether their problems are HW related or not. In my case, I have been > free of DMA errors (cross your fingers) after re-installed FreeBSD > completely (giving it a larger boot partition and redoing the ZFS slice > too), and before this, I changed the IDE cable just to eliminate one > more variable. Therefore, there are too many variables to reach a firm > conclusion, since even if the cable was "bad", I never saw one DMA error > or other indication of anything wrong with HW from the Linux side (and > I've been using that HW with both Linux and FreeBSD 6.2 for months now - > no apparent flakiness of any kind on either system). So either it *was* > bad and FreeBSD 7.0 was being more "honest", FreeBSD's drivers and/or > ZFS was stressing the HW and revealing weaknesses in the cable, or it > was a SW issue that got cleared somehow when I re-installed. > > Is it possible that the problem lies in the ATA drivers in FreeBSD or > even in ZFS and just looks like HW issues? I do not have enough > info/expertise to know. If not, then it may very well be true that HW > problems are pretty widespread (and that disk HW cannot, in fact, be > trusted), and there really *is* a strong need for ZFS *now* to protect > our data. If there is a possibility that SW could be involved, any > hints on how to further debug this would be of great help to those still > experiencing recent DMA errors. I just want to be more sure one way or > the other, but I know this issue is not an easy one (however, it's the > kind of problem that should receive the highest priority, IMHO). I'm not sure what happened to this thread, but I also had a lot of similar issues. I was using SATA, and using a mirrored pair of SATA drives, brand new. It was suggested that my controller was junk. I'm starting to think there is a timing issue or some such problem with ZFS, since I can use the same drives in a gmirror with UFS, and never have any data problems (md5 checksums confirm it over-and-over). I highly doubt that everyone is seeing similar issues and it just is because ZFS is so intense. I've had plenty of systems under severe disk load that have never exhibited corrupt files because of something like this. I wish we could get our hands on this issue.. Seems like some common threads are ATA/SATA disks. Is your setup running 32bit or 64bit FreeBSD? (if you already mentioned it, I'm sorry, I missed it) Eric From owner-freebsd-fs@FreeBSD.ORG Tue Mar 4 13:47:57 2008 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 F1EFC1065671; Tue, 4 Mar 2008 13:47:56 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id DB3468FC1F; Tue, 4 Mar 2008 13:47:56 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id C424E1CC033; Tue, 4 Mar 2008 05:47:56 -0800 (PST) Date: Tue, 4 Mar 2008 05:47:56 -0800 From: Jeremy Chadwick To: Eric Anderson Message-ID: <20080304134756.GA90698@eos.sc1.parodius.com> References: <47ACD7D4.5050905@skyrush.com> <47ACDE82.1050100@skyrush.com> <20080208173517.rdtobnxqg4g004c4@www.wolves.k12.mo.us> <47ACF0AE.3040802@skyrush.com> <1202747953.27277.7.camel@buffy.york.ac.uk> <47B0A45C.4090909@skyrush.com> <47CD4DCF.5070505@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <47CD4DCF.5070505@freebsd.org> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-fs@freebsd.org, Joe Peterson , freebsd-stable@freebsd.org Subject: Re: Analysis of disk file block with ZFS checksum error 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, 04 Mar 2008 13:47:57 -0000 On Tue, Mar 04, 2008 at 07:25:35AM -0600, Eric Anderson wrote: > I'm starting to think there is a timing issue or some such problem with > ZFS, since I can use the same drives in a gmirror with UFS, and never have > any data problems (md5 checksums confirm it over-and-over). I highly doubt > that everyone is seeing similar issues and it just is because ZFS is so > intense. I've had plenty of systems under severe disk load that have never > exhibited corrupt files because of something like this. One thing that hasn't been mentioned (or maybe it has been but I missed it): FreeBSD's ZFS port is version 6, while Solaris is up to version 10. Is it possible that the problem folks are experiencing, including the infamous deadlock or crash on heavy I/O between UFS/UFS2 and ZFS filesystems, could've been fixed between versions 6 and 10? I myself use gstripe(8) and UFS2 (no softupdates) on two identical SATA disks. I do nightly backups so if I lose a disk, I'm OK. My transfer rates are quite good (~143MB/sec read, ~130MB/sec write -- really!) on the stripe, and in the past 2 weeks I have spent a LOT of time copying over 150GB of data back and forth between the stripe and the backup disk without any issues. All disks are on an ICH7 controller. > I wish we could get our hands on this issue.. Seems like some common > threads are ATA/SATA disks. Is your setup running 32bit or 64bit FreeBSD? > (if you already mentioned it, I'm sorry, I missed it) So far the reports have shown that it's not specific to either i386 or amd64, and that it's not specific to any type of hardware (motherboard, controller, etc.). Joe's setup is very different from mine, for example. If the same disks are fine when used with UFS/UFS2, then I'd say it's less of a ATA subsystem bug, and more of an oddity with ZFS on FreeBSD. If it's reproducable, that would be helpful to developers. Regarding ATA/SATA though, there are reports of DMA timeouts and other oddities happening on ATA/SATA disks on FreeBSD. When I was using ZFS not too long ago, I experienced that problem when doing heavy I/O (copying data from a standard UFS2 disk to a ZFS RAIDZ pool). It's been the only time I've seen this problem. http://lists.freebsd.org/pipermail/freebsd-stable/2008-January/040013.html The drive showed no signs of errors (SMART stats look fine, no mechanical noises or other oddities). I've since replaced it out of pure paranoia with a disk identical to the ones on the gstripe(8). Regarding those issues (DMA errors, etc.), Scott Long has offered to help, but needs systems which can reproduce the problem reliably and have remote access (serial highly recommended). -- | Jeremy Chadwick jdc at 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 Tue Mar 4 16:38:02 2008 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 D646B1065674 for ; Tue, 4 Mar 2008 16:38:02 +0000 (UTC) (envelope-from ecrist@secure-computing.net) Received: from snipe.secure-computing.net (snipe.secure-computing.net [209.240.66.149]) by mx1.freebsd.org (Postfix) with ESMTP id A660D8FC12 for ; Tue, 4 Mar 2008 16:38:02 +0000 (UTC) (envelope-from ecrist@secure-computing.net) Received: from swordfish.local.claimlynx.com (unknown [74.95.66.25]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: ecrist@secure-computing.net) by snipe.secure-computing.net (Postfix) with ESMTP id 640AA1706B for ; Tue, 4 Mar 2008 10:22:47 -0600 (CST) Message-Id: <6A002150-F8D8-4958-ACA8-7178403C6A4F@secure-computing.net> From: Eric F Crist To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v919.2) Date: Tue, 4 Mar 2008 10:22:35 -0600 X-Mailer: Apple Mail (2.919.2) Subject: ZFS kernel panic in single user 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, 04 Mar 2008 16:38:02 -0000 Hey folks, Please 'reply-all' as I'm not on the mailing list. For background, we've got the following setup: Dell PowerEdge 1650 w/2xP3 1.113GHz 1GB ECC RAM Dell SCSI ACI Backplane 1x3 2x 73GB Seagate 10K SCSI Drives 1x IDE->CF Converter 1x 1GB CF Card We loosely followed the instructions over at http://www.ish.com.au/solutions/articles/freebsdzfs . There is one key difference to our setup from the ish.com.au instructions. We are using the CF card for our /bootdir partition to get the FreeBSD kernel loaded enough to load the ZFS modules. We don't have a boot record or anything on the two SCSI drives. Our idea being that, if a drive fails, the CF card and all the boot goodness stays where it is. To my point. I ran across the ZFSKnownProblems wiki page which strongly encourages the reporting of any problems we have. From a booted system, I issued the 'shutdown now' command to bring the system down to single-user mode. Issuing a reboot command from this point, I get the following errors: Spin lock 0xc0bdca00 (sched lock) held by 0xc3f10c60 (tid 100001) too long panic: spin lock held too long cpuid = 0 Also, the wiki page claims that ZFS file systems aren't started when entering single-user mode. We are *not* experiencing this problem. With the above setup, I am able to successfully enter single-user mode (4 at boot prompt) and my ZFS file systems are loading without error. Could this problem be out of date, as the 'workaround' mentioned was from April of last year? Hope this helps. ----- Eric F Crist Secure Computing Networks From owner-freebsd-fs@FreeBSD.ORG Wed Mar 5 00:15:28 2008 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 33FEB1065673; Wed, 5 Mar 2008 00:15:28 +0000 (UTC) (envelope-from joe@skyrush.com) Received: from shadow.wildlava.net (shadow.wildlava.net [67.40.138.81]) by mx1.freebsd.org (Postfix) with ESMTP id EB3F18FC1A; Wed, 5 Mar 2008 00:15:27 +0000 (UTC) (envelope-from joe@skyrush.com) Received: from [10.0.3.98] (mail.boulder.swri.edu [65.241.78.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by shadow.wildlava.net (Postfix) with ESMTP id 3A18B8F432; Tue, 4 Mar 2008 17:15:25 -0700 (MST) Message-ID: <47CDE61A.8040102@skyrush.com> Date: Tue, 04 Mar 2008 17:15:22 -0700 From: Joe Peterson User-Agent: Thunderbird 2.0.0.9 (X11/20071119) MIME-Version: 1.0 To: Eric Anderson References: <47ACD7D4.5050905@skyrush.com> <47ACDE82.1050100@skyrush.com> <20080208173517.rdtobnxqg4g004c4@www.wolves.k12.mo.us> <47ACF0AE.3040802@skyrush.com> <1202747953.27277.7.camel@buffy.york.ac.uk> <47B0A45C.4090909@skyrush.com> <47CD4DCF.5070505@freebsd.org> In-Reply-To: <47CD4DCF.5070505@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Analysis of disk file block with ZFS checksum error 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, 05 Mar 2008 00:15:28 -0000 Eric Anderson wrote: > I'm starting to think there is a timing issue or some such problem with > ZFS, since I can use the same drives in a gmirror with UFS, and never > have any data problems (md5 checksums confirm it over-and-over). I > highly doubt that everyone is seeing similar issues and it just is > because ZFS is so intense. I've had plenty of systems under severe disk > load that have never exhibited corrupt files because of something like > this. I also wondered this - i.e. if ZFS was triggering a certain timing behavior that revealed the problem. Still, if this is the case, it seems to me that the problem lies in the ATA subsystem, since it should prevent a higher-level things like ZFS to be able to create bad timings (or am I not thinking of this correctly?). Also, I think there were some reports of problems with DMA/ATA when *not* using ZFS. > I wish we could get our hands on this issue.. Seems like some common > threads are ATA/SATA disks. Is your setup running 32bit or 64bit > FreeBSD? (if you already mentioned it, I'm sorry, I missed it) This was on 32bit FreeBSD with PATA. I am the one who had no SMART issues and no DMA errors reported under Linux. Changing the cable may have "fixed" it, since I did not see errors in some further testing, but even if so, my theory is that there is some edge case (timing?) that the FreeBSD ATA drivers were sensitive to, and perhaps my change of cables pushed the problem to the other side of the threshold. Since I never saw errors under Linux (and I've been using that cable for a couple of years), I do not necessarily think the cable was actually "defective". -Joe From owner-freebsd-fs@FreeBSD.ORG Fri Mar 7 18:08:52 2008 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 551C51065696 for ; Fri, 7 Mar 2008 18:08:52 +0000 (UTC) (envelope-from julianor@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.240]) by mx1.freebsd.org (Postfix) with ESMTP id 0B49C8FC24 for ; Fri, 7 Mar 2008 18:08:51 +0000 (UTC) (envelope-from julianor@gmail.com) Received: by an-out-0708.google.com with SMTP id c14so209091anc.13 for ; Fri, 07 Mar 2008 10:08:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:from:to:content-type:mime-version:subject:date:x-mailer; bh=I7ym0xDcbjEuamZfEVbmEKbLtos/qJNMHEIn4gRGRFs=; b=jherRrPGTxi/pWu58JxFoFisDtb5MMgwIoG5IFuwce0u0cOF0L9wP4K1/7t+joleIBYjOlzGKwPVseNWvlCzT2skPnK5ozTox8U7GE8Nzv2n8OphspF3cpqDfXWv3AAeejQitW2jf5JVfUqA8dxBVVMyU08KRMdZJeQgaUHkkdw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:content-type:mime-version:subject:date:x-mailer; b=ZSR+OhMehJznymknFsjbzZjRgIwdyaIDCTDaCB6CFUcFjknYEmOwaiCOaVFBmVznHo+EXYFYTDriu2XjJZymUZSMM/QYcf/jmOrQifJ6Ugd1Eh+iE8X9WgmVBYGAppurJla8SfTBg+/NUnjV+otD6MrRVI+heJQNvWYPu+0WvGg= Received: by 10.100.105.15 with SMTP id d15mr3821798anc.61.1204911663260; Fri, 07 Mar 2008 09:41:03 -0800 (PST) Received: from lan-96.labsec.ufsc.br ( [150.162.66.96]) by mx.google.com with ESMTPS id c1sm8967575ana.36.2008.03.07.09.41.01 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 07 Mar 2008 09:41:02 -0800 (PST) Message-Id: <58644413-9031-48F4-85E6-A49A48E0CA41@gmail.com> From: Juliano Romani To: freebsd-fs@freebsd.org Mime-Version: 1.0 (Apple Message framework v919.2) Date: Fri, 7 Mar 2008 14:40:58 -0300 X-Mailer: Apple Mail (2.919.2) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: mount in freebsd 7.0 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, 07 Mar 2008 18:08:52 -0000 Hi... I have a embedded system based in pfsense structure. When it boot, / dev/ad0a is mounted in / and a memory disk (/dev/md0a) is mounted in / mnt. Then i chroot /mnt. Now, i need mount /dev/ad0a in /cf, but it only possible in read-only mode. I need it work in read-write mode. In freebsd 6.3 it works, but now, i try in 7.0 and this happening. Any ideias about happen??? A example of real case, FreeBSD 6.3,: # mount /dev/ad0a on / (ufs, local, read-only) devfs on /dev (devfs, local) /dev/md0c on /mnt (ufs, local) devfs on /dev (devfs, local) /dev/ad0a on /cf (ufs, local, read-only) # mount -uw /cf # mount /dev/ad0a on / (ufs, local, read-only) devfs on /dev (devfs, local) /dev/md0c on /mnt (ufs, local) devfs on /dev (devfs, local) /dev/ad0a on /cf (ufs, local) # FreeBSD 7.0: # mount /dev/ad0a on / (ufs, local) devfs on /dev (devfs, local) /dev/md0c on /mnt (ufs, local) devfs on /dev (devfs, local) # mount -o ro /dev/ad0a /cf # mount /dev/ad0a on / (ufs, local, read-only) devfs on /dev (devfs, local) /dev/md0c on /mnt (ufs, local) devfs on /dev (devfs, local) /dev/ad0a on /cf (ufs, local, read-only) # mount -uw /cf mount: : Operation not permitted # remember that /cf is mounted inside of chroot. Thanks From owner-freebsd-fs@FreeBSD.ORG Sat Mar 8 09:20:53 2008 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 C9C18106566C for ; Sat, 8 Mar 2008 09:20:53 +0000 (UTC) (envelope-from cedilla@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.178]) by mx1.freebsd.org (Postfix) with ESMTP id 9F9CD8FC1E for ; Sat, 8 Mar 2008 09:20:53 +0000 (UTC) (envelope-from cedilla@gmail.com) Received: by wa-out-1112.google.com with SMTP id k17so1048757waf.3 for ; Sat, 08 Mar 2008 01:20:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:subject:content-type:content-transfer-encoding; bh=sFe8MgvPr+/3j0EGpjzLBoKLxmam6yDCO9YnHXBOovE=; b=XzW7GTwJiSeRw37Da94bbCmgprHw4upuxIzklqkuuYIxOyAgfZ/vn4HKHfgiHc+g29pU4kQNXdbMcmtTRrs6gw+AnE03lVMoWI/7xlqclbAdA9o+7EWAgZZAmA5f5/Paz2qVP8IK8bzAFbl22509XCGQnI4yK1xcm0z/qGBICTc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:content-type:content-transfer-encoding; b=UUC3TUzUBDR9mnTIUNeR3eIv/vPGwn9khrksyuIMceVaisAt1tJ7U++OBIJ9Tp1cpMIjdD9mK+RIiTK1/mk7R6vW+y622rO2CPTbVDwRaoMHRWmugxrxws8ehejdhpfpS4cHat0ELHcyplq3birwWRBs4AcyibqebRpJdFbDhRo= Received: by 10.115.111.1 with SMTP id o1mr239822wam.87.1204966443236; Sat, 08 Mar 2008 00:54:03 -0800 (PST) Received: from ?192.168.1.100? ( [75.36.57.52]) by mx.google.com with ESMTPS id v35sm2645822wah.19.2008.03.08.00.53.59 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 08 Mar 2008 00:54:00 -0800 (PST) Message-ID: <47D25426.8050505@gmail.com> Date: Sat, 08 Mar 2008 00:53:58 -0800 From: Reed Wilson User-Agent: Thunderbird 2.0.0.12 (Windows/20080213) MIME-Version: 1.0 To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: ZFS zvol write speed incredibly slow 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, 08 Mar 2008 09:20:53 -0000 Hi guys! I just got 7.0-RELEASE installed and running on my home server, and I've noticed incredibly slow write speeds to a ZFS zvol. Reading speeds seem normal. It may be related to the OpenSolaris bug #6428639: http://bugs.opensolaris.org/view_bug.do?bug_id=6428639 >> To another zpool: # dd if=junk of=/tank2/junk bs=65536 1024+0 records in 1024+0 records out 67108864 bytes transferred in 0.331802 secs (202255676 bytes/sec) >> To a zvol in the same pool: dd if=junk of=/dev/zvol/tank/tempvol bs=65536 1024+0 records in 1024+0 records out 67108864 bytes transferred in 11.575167 secs (5797658 bytes/sec) Using smaller block sizes exacerbates the problem (444606 bytes/sec with 4096-byte blocks!) -- Reed