From owner-freebsd-fs@FreeBSD.ORG Sun Jul 27 15:03:20 2014 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 83037667 for ; Sun, 27 Jul 2014 15:03:20 +0000 (UTC) Received: from frv189.fwdcdn.com (frv189.fwdcdn.com [212.42.77.189]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3E32523C4 for ; Sun, 27 Jul 2014 15:03:20 +0000 (UTC) Received: from [10.10.2.23] (helo=frv198.fwdcdn.com) by frv189.fwdcdn.com with esmtp ID 1XBPiD-000GXC-Tc for fs@freebsd.org; Sun, 27 Jul 2014 17:46:09 +0300 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ukr.net; s=ffe; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-Id:Cc:To:Subject:From:Date; bh=mYAGHFPQbN2S1N/XkZQ010SeQRv5XJjyaY4wYOgssc8=; b=ioLqbvEr0I3vmveSaN5FvcmifaQaHtvS8D3xcuH99qDoodOyGI8tqoktMr/rY2BlmqRwrLZXBpk6F5jBP7yPgR45cN9RQBofc9U5xWIEjlUzw/8utR1LEa1MX+kk2CuRJEjgSoKA9aUg2rMGR24MAPzenJZ7+c6zd5Fc0mJfl1s=; Received: from [10.10.10.35] (helo=frv35.fwdcdn.com) by frv198.fwdcdn.com with smtp ID 1XBPi3-000FpP-FT for fs@freebsd.org; Sun, 27 Jul 2014 17:45:59 +0300 Date: Sun, 27 Jul 2014 17:45:59 +0300 From: Vladislav Prodan Subject: Say me, please, how I can transfer between servers ZFS-partitions larger than 20Gb. To: questions@freebsd.org X-Mailer: mail.ukr.net 5.0 Message-Id: <1406471619.238727352.o7o2ccyx@frv35.fwdcdn.com> MIME-Version: 1.0 Received: from universite@ukr.net by frv35.fwdcdn.com; Sun, 27 Jul 2014 17:45:59 +0300 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: binary Content-Disposition: inline Cc: fs@freebsd.org, "net@freebsd.org net@freebsd.org" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jul 2014 15:03:20 -0000 Say me, please, how I can transfer between servers ZFS-partitions larger than 20Gb. I have 4 partitions with backup data. There are a lot of small pictures. NAME USED AVAIL REFER MOUNTPOINT tank2 1,42T 1,32T 118M legacy ... tank2/ay-files 31,9G 1,32T 31,8G /backup/beastie/upload_ftp/ay/files tank2/XXXXXmarket-images 135G 1,32T 135G /backup/beastie/upload_ftp/XXXXXmarket/images tank2/XXXXXmarket-uploads 17,6G 1,32T 17,5G /backup/beastie/upload_ftp/XXXXXmarket/uploads tank2/YYYYmarket 24,4G 1,32T 152K /backup/beastie/upload_ftp/YYYYmarket tank2/YYYYmarket/uploads 24,4G 1,32T 24,2G /backup/beastie/upload_ftp/YYYYmarket/uploads ... Say me, please, how I can transfer it at another server with ZFS. Servers are connected through unmanaged 100M switch. Sending via (zfs send) and (ssh host2 zfs recv) ends with error after 20GB of data. Sending via rsync is very lasting and requires often restart of rsync. What an alternative? -- Vladislav V. Prodan System & Network Administrator support.od.ua From owner-freebsd-fs@FreeBSD.ORG Sun Jul 27 16:09:36 2014 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3E687A4D; Sun, 27 Jul 2014 16:09:36 +0000 (UTC) Received: from denrei.darkbsd.org (denrei.darkbsd.org [IPv6:2001:41d0:1:f442::1]) by mx1.freebsd.org (Postfix) with ESMTP id E16F12918; Sun, 27 Jul 2014 16:09:35 +0000 (UTC) Received: from denrei.darkbsd.org (localhost [127.0.0.1]) by denrei.darkbsd.org (Postfix) with ESMTP id 5351116CB; Sun, 27 Jul 2014 18:09:31 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=darkbsd.org; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type; s=selector1; bh=9ziGo4FI2dwOOfTKymTjxF0m1YA=; b=A w0QwQEQN3103MLQL3ihknaG6teSBe6ANpkbT8EK5jULB5ly1llqyPesPzIsr4ZWV e4ym4MGJp+0/JOGOKslA5N1BltvNg5E4LiShoXHzmMucBk1RE6r4e9BnFTS3S+vF VJ3qGONh2qPQXHDga67iXJfN+n8lzpVnahhRx2mqWQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=darkbsd.org; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type; q=dns; s=selector1; b=giAu4V+82A77xxK9K4RfHNgPb0K eP0rbKkS96bfPxE5JFZ0Y+9JDp1m+jTByffk1296zdg4k+DUxgniyt5RvzPDpDMo M0YFLxQDU37NYqEkjb6KAJFoA63ZJZg0dgq6yTZ129f/62HuMZT24wPE8qEv6bEw 7qmJg3+sloMs/PgM= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=darkbsd.org; h= content-type:content-type:in-reply-to:references:subject:subject :mime-version:user-agent:from:from:date:date:message-id:received :received; s=selector1; t=1406477370; bh=bEB9sTfAWicvBsqpyA0Y7wl bRFvKr+brzF+iesPqNrM=; b=igDWQGHdIrm5ZlHpN8jiNqYKzEi44E3WP7wLAgt igJIHG7k100xz2zaU+rX5YXahZ/FW4gLzmntCwx77RZ4ghgzYDBss/fRQYeKAI2E iwyqBj5XZwz2jXYGiVsPXVFFZX5HT9OrLmsmht8UhQ8aMvC0crKihvf/qEMboJOM TgQQ= X-Virus-Scanned: amavisd-new at darkbsd.org Received: from denrei.darkbsd.org ([127.0.0.1]) by denrei.darkbsd.org (denrei.darkbsd.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id nrSHC5BN46Nf; Sun, 27 Jul 2014 18:09:30 +0200 (CEST) Received: from [IPv6:2001:470:24:42d::42] (archer.yomi.darkbsd.org [IPv6:2001:470:24:42d::42]) (Authenticated sender: darksoul@darkbsd.org) by denrei.darkbsd.org (Postfix) with ESMTPSA id 2BED416CA; Sun, 27 Jul 2014 18:09:26 +0200 (CEST) Message-ID: <53D52434.7030308@darkbsd.org> Date: Mon, 28 Jul 2014 01:09:24 +0900 From: DarkSoul User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Vladislav Prodan , questions@freebsd.org Subject: Re: Say me, please, how I can transfer between servers ZFS-partitions larger than 20Gb. References: <1406471619.238727352.o7o2ccyx@frv35.fwdcdn.com> In-Reply-To: <1406471619.238727352.o7o2ccyx@frv35.fwdcdn.com> X-Enigmail-Version: 1.5.2 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="5jXL8L7B7ukTrP2NGVQMs1IExhQWAeuPa" Cc: fs@freebsd.org, "net@freebsd.org net@freebsd.org" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jul 2014 16:09:36 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --5jXL8L7B7ukTrP2NGVQMs1IExhQWAeuPa Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 07/27/2014 11:45 PM, Vladislav Prodan wrote: > Say me, please, how I can transfer between servers ZFS-partitions large= r than 20Gb. > I have 4 partitions with backup data. There are a lot of small pictures= =2E > > NAME USED AVAIL REFER MOUNTPOINT > tank2 1,42T 1,32T 118M legacy > ... > tank2/ay-files 31,9G 1,32T 31,8G /backup/beas= tie/upload_ftp/ay/files > tank2/XXXXXmarket-images 135G 1,32T 135G /backup/beas= tie/upload_ftp/XXXXXmarket/images > tank2/XXXXXmarket-uploads 17,6G 1,32T 17,5G /backup/beas= tie/upload_ftp/XXXXXmarket/uploads > tank2/YYYYmarket 24,4G 1,32T 152K /backup/beas= tie/upload_ftp/YYYYmarket > tank2/YYYYmarket/uploads 24,4G 1,32T 24,2G /backup/beas= tie/upload_ftp/YYYYmarket/uploads > ... > > Say me, please, how I can transfer it at another server with ZFS. > Servers are connected through unmanaged 100M switch. > Sending via (zfs send) and (ssh host2 zfs recv) ends with error after 2= 0GB of data. > Sending via rsync is very lasting and requires often restart of rsync. > > What an alternative? For the initial 20G upload, you could zfs send to a file, and transfer that file via rsync or other resumable file transfer system that ensures integrity : host1# zfs send tank2/XXXXXmarket-images@snapshot > tank2-XXXXXmarket-images@snapshot.zfs host1# rsync tank2-XXXXXmarket-images@snapshot.zfs host2: host2# cat tank2-XXXXXmarket-images@snapshot.zfs | zfs recv tank3 Then the rest can be done via small snapshots and plain zfs send | ssh host2 zfs recv. You could even add bzip2 compression and decompression at each endpoint. This is what I am doing to replicate data of often updated filesystems (mailbox filesystems, with LOTS of small files) between ZFS servers. Cheers, > --=20 > Stephane LAPIE, EPITA SRS, Promo 2005 > "Even when they have digital readouts, I can't understand them." > --MegaTokyo > > --=20 > Stephane LAPIE, EPITA SRS, Promo 2005 > "Even when they have digital readouts, I can't understand them." > --MegaTokyo --5jXL8L7B7ukTrP2NGVQMs1IExhQWAeuPa Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iF4EAREIAAYFAlPVJDQACgkQDJ4OK7D3FWR20wEAlEwxKf4EqYiLuYSTLua3Pkdo vGLQncD91yq63gc2CSoA/3skYXgw/ADY6Fq77LHEHxBnSeWhJYfID6Kd/pPtWy9B =1/W9 -----END PGP SIGNATURE----- --5jXL8L7B7ukTrP2NGVQMs1IExhQWAeuPa-- From owner-freebsd-fs@FreeBSD.ORG Sun Jul 27 18:08:51 2014 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C8DE9B6E; Sun, 27 Jul 2014 18:08:50 +0000 (UTC) Received: from relay2-bcrtfl2.verio.net (relay2-bcrtfl2.verio.net [131.103.218.177]) by mx1.freebsd.org (Postfix) with ESMTP id A92122388; Sun, 27 Jul 2014 18:08:50 +0000 (UTC) Received: from iad-wprd-xchw02.corp.verio.net (iad-wprd-xchw02.corp.verio.net [198.87.7.165]) by relay2-bcrtfl2.verio.net (Postfix) with ESMTP id 0FAC11FF00E8; Sun, 27 Jul 2014 13:41:46 -0400 (EDT) Received: from IAD-WPRD-XCHB01.corp.verio.net ([198.87.7.137]) by iad-wprd-xchw02.corp.verio.net with Microsoft SMTPSVC(6.0.3790.4675); Sun, 27 Jul 2014 13:41:45 -0400 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.4913 Content-Class: urn:content-classes:message Importance: normal Priority: normal MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: RE: Say me, please, how I can transfer between servers ZFS-partitions larger than 20Gb. Date: Sun, 27 Jul 2014 13:41:42 -0400 Message-ID: In-Reply-To: <1406471619.238727352.o7o2ccyx@frv35.fwdcdn.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Say me, please, how I can transfer between servers ZFS-partitions larger than 20Gb. thread-index: Ac+pq/ouBkZN3D0USAGHxOeJGDC1jQAFeDjQ References: <1406471619.238727352.o7o2ccyx@frv35.fwdcdn.com> From: "David DeSimone" To: "Vladislav Prodan" , X-OriginalArrivalTime: 27 Jul 2014 17:41:45.0551 (UTC) FILETIME=[08ECA5F0:01CFA9C2] Cc: fs@freebsd.org, net@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jul 2014 18:08:52 -0000 Mark Martinec just reported this problem a few days ago, and he found a = work-around. See the following: http://lists.freebsd.org/pipermail/freebsd-net/2014-July/039347.html -----Original Message----- From: owner-freebsd-net@freebsd.org = [mailto:owner-freebsd-net@freebsd.org] On Behalf Of Vladislav Prodan Sent: Sunday, July 27, 2014 9:46 AM To: questions@freebsd.org Cc: fs@freebsd.org; net@freebsd.org net@freebsd.org Subject: Say me, please, how I can transfer between servers = ZFS-partitions larger than 20Gb. Say me, please, how I can transfer between servers ZFS-partitions larger = than 20Gb. I have 4 partitions with backup data. There are a lot of small pictures. NAME USED AVAIL REFER MOUNTPOINT tank2 1,42T 1,32T 118M legacy ... tank2/ay-files 31,9G 1,32T 31,8G = /backup/beastie/upload_ftp/ay/files tank2/XXXXXmarket-images 135G 1,32T 135G = /backup/beastie/upload_ftp/XXXXXmarket/images tank2/XXXXXmarket-uploads 17,6G 1,32T 17,5G = /backup/beastie/upload_ftp/XXXXXmarket/uploads tank2/YYYYmarket 24,4G 1,32T 152K = /backup/beastie/upload_ftp/YYYYmarket tank2/YYYYmarket/uploads 24,4G 1,32T 24,2G = /backup/beastie/upload_ftp/YYYYmarket/uploads ... Say me, please, how I can transfer it at another server with ZFS. Servers are connected through unmanaged 100M switch. Sending via (zfs send) and (ssh host2 zfs recv) ends with error after = 20GB of data. Sending via rsync is very lasting and requires often restart of rsync. What an alternative? -- Vladislav V. Prodan System & Network Administrator support.od.ua _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" This email message is intended for the use of the person to whom it has = been sent, and may contain information that is confidential or legally = protected. If you are not the intended recipient or have received this = message in error, you are not authorized to copy, distribute, or = otherwise use this message or its attachments. Please notify the sender = immediately by return e-mail and permanently delete this message and any = attachments. Verio Inc. makes no warranty that this email is error or = virus free. Thank you. From owner-freebsd-fs@FreeBSD.ORG Sun Jul 27 19:39:13 2014 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0DFEA79D for ; Sun, 27 Jul 2014 19:39:13 +0000 (UTC) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 68D432D37 for ; Sun, 27 Jul 2014 19:39:11 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.14.5/8.14.5) with ESMTP id s6RJd9eM076433 for ; Sun, 27 Jul 2014 23:39:09 +0400 (MSK) (envelope-from marck@rinet.ru) Date: Sun, 27 Jul 2014 23:39:09 +0400 (MSK) From: Dmitry Morozovsky To: freebsd-fs@FreeBSD.org Subject: Re: restore: bad block size 5632 between different major versions (fwd) Message-ID: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) X-NCC-RegID: ru.rinet X-OpenPGP-Key-ID: 6B691B03 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (woozle.rinet.ru [0.0.0.0]); Sun, 27 Jul 2014 23:39:10 +0400 (MSK) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jul 2014 19:39:13 -0000 Colleagues, I suppose at least some of you do not track -stable@ due to its volume. Your thoughts? Thank you! -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: marck@FreeBSD.org ] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------ ---------- Forwarded message ---------- Date: Sun, 27 Jul 2014 23:19:48 From: Dmitry Morozovsky To: freebsd-stable@freebsd.org Subject: Re: restore: bad block size 5632 between different major versions Colleagues, following up to myself: On Thu, 24 Jul 2014, Dmitry Morozovsky wrote: > I'm a bit stumbled. > > prerequisites: > > - backup server, stable/9 (a bit obsoleted, but this is unrelated to the > problem) I forgot to mention that it is ZFS-based. > ** on backup server: > backup@whale:/B/dump/lion> uname -r > 9.1-STABLE > backup@whale:/B/dump/lion> cat 5-var.dgz.?? | zcat | ./restore -t -v -f - > Verify tape and initialize maps > Dump date: Thu Jul 24 06:57:04 2014 > Dumped from: Wed Jul 23 06:57:04 2014 > Level 5 dump of /var on lion.rinet.ru:/dev/da0e > Label: none > bad block size 5632 ktrace'ing restore I've found that stat(".") on ZFS in my case returning blksize=5632, which makes restore unhappy somewhere at 261- if (stbuf.st_blksize >= TP_BSIZE && stbuf.st_blksize <= MAXBSIZE) 262- fssize = stbuf.st_blksize; 263- if (((fssize - 1) & fssize) != 0) { 264: fprintf(stderr, "bad block size %ld\n", fssize); 265- done(1); 266- } commenting lines 263-266 gives me working restore. Any hints from now? It's not clear to me why we check this at all? Thanks! -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: marck@FreeBSD.org ] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------ _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-fs@FreeBSD.ORG Sun Jul 27 22:00:30 2014 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7573DF4B for ; Sun, 27 Jul 2014 22:00:30 +0000 (UTC) Received: from smtp.new-ukraine.org (smtp.new-ukraine.org [148.251.53.51]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.new-ukraine.org", Issuer "smtp.new-ukraine.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id EF2042D56 for ; Sun, 27 Jul 2014 22:00:29 +0000 (UTC) Received: from new-ukraine.org (smtp.new-ukraine.org [148.251.53.51]) by smtp.new-ukraine.org with ESMTP id s6RM0JiX024228 for ; Mon, 28 Jul 2014 01:00:20 +0300 (EEST) Message-ID: <20140728010019.24227@smtp.new-ukraine.org> Date: Mon, 28 Jul 2014 01:00:19 -2100 From: "Zeus Panchenko" To: cc: Subject: empty ls(1) output for mounted=yes zfs Organization: I.B.S. LLC Reply-To: "Zeus Panchenko" X-Attribution: zeus Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAFVBMVEWxsbGdnZ3U1NQTExN cXFzx8fG/v7+f8hyWAAACXUlEQVQ4jUWSwXYiIRBFi4yyhtjtWpmRdTL0ZC3TJOukDa6Rc+T/P2F eFepwtFvr8upVFVDua8mLWw6La4VIKTuMdAPOebdU55sQs3n/D1xFFPFGVGh4AHKttr5K0bS6g7N ZCge7qpVLB+f1Z2WAj2OKXwIWt/bXpdXSiu8KXbviWkHxF5td9+lg2e3xlI2SCvatK8YLfHyh9lw 15yrad8Va5eXg4Llr7QmAaC+dL9sDt9iad/DX3OKvLMBf+dm0A0QuMrTvYIevSik1IaSVvgjIHt5 lSCG2ynNRpEcBZ8cgDWk+Ns99qzsYYV3MZoppWzGtYlTO9+meG6m/g92iNO9LfQB2JZsMpoJs7QG ku2KtabRK0bZRwDLyBDvwlxTm6ZlP7qyOqLcfqtLexpDSB4M0H3I/PQy1emvjjzgK+A0LmMKl6Lq zlqzh0VGAw440F6MJd8cY0nI7wiF/fVIBGY7UNCAXy6DmfYGCLLI0wtDbVcDUMqtJLmAhLqODQAe riERAxXJ1/QYGpa0ymqyytpKC19MNXHjvFmEsfcHIrncFR4xdbYWgmfEGLCcZokpGbGj1egMR+6M 1BkNX1pDdhPcOXpAnAeLQUwQLYepgQoZVNGS61yaE8CYA7gYAcWKzwGstACY2HTFvvOwk4FXAG/a mKHni/EcA/GkOk7I0IK7UMIf3+SahU8/FJdiE7KcuWdM3MFocUDEEIX9LfJoo4xV5tnNKc3jJuSs SZWgnnhepgU1zN4Hii18yW4RwDX52CXUtk0Hqz6cHOIUkWaX8fDcB+J7y1y2xDHwjv/8Buu8Ekz6 7tXQAAAAASUVORK5CYII= X-Mailer: MH-E 8.3.1; GNU Mailutils 2.99.98; GNU Emacs 24.3.1 MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jul 2014 22:00:30 -0000 =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, please, help me to understand whether I miss something ... zpool version: 5000 OS: FreeBSD 10.0-STABLE #0 r261303 I have created fs with: zfs create -o mountpoint=3D/home/zeus/storage zroot/storage after reboot it reports it is mounted: > zfs get mounted zroot_z-hp/storage=20 NAME PROPERTY VALUE SOURCE zroot/storage mounted yes - zroot/storage mountpoint /home/zeus/storage local but it is empty ... ls -al /home/zeus/storage . .. and `zfs unmount zroot/storage && zfs mount zroot/storage' helps ... after unmount/mount all zroot/storage content is visible in the expected pa= th what I miss, please? =2D --=20 Zeus V. Panchenko jid:zeus@im.ibs.dn.ua IT Dpt., I.B.S. LLC GMT+2 (EET) =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlPVdnMACgkQr3jpPg/3oyqQUQCg+EUngzH+Kz47s2sJ1KCCXED6 EFcAoKzJUiMIdlfk6wwjRT33sOf+P39W =3DKIej =2D----END PGP SIGNATURE----- From owner-freebsd-fs@FreeBSD.ORG Mon Jul 28 08:00:10 2014 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CDAF3788 for ; Mon, 28 Jul 2014 08:00:10 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B0F272D2E for ; Mon, 28 Jul 2014 08:00:10 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s6S80ArD062238 for ; Mon, 28 Jul 2014 08:00:10 GMT (envelope-from bugzilla-noreply@freebsd.org) Message-Id: <201407280800.s6S80ArD062238@kenobi.freebsd.org> From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bugzilla] Commit Needs MFC MIME-Version: 1.0 X-Bugzilla-Type: whine X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated Date: Mon, 28 Jul 2014 08:00:10 +0000 Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.18 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jul 2014 08:00:11 -0000 Hi, You have a bug in the "Needs MFC" state which has not been touched in 7 or more days. This email serves as a reminder that you may want to MFC this bug or marked it as completed. In the event you have a longer MFC timeout you may update this bug with a comment and I won't remind you again for 7 days. This reminder is only sent on Mondays. Please file a bug about concerns you may have. This search was scheduled by eadler@FreeBSD.org. (5 bugs) Bug 133174: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=133174 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-fs@FreeBSD.org Status: Needs MFC Resolution: Summary: [msdosfs] [patch] msdosfs must support multibyte international characters in file names Bug 136470: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=136470 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-fs@FreeBSD.org Status: Needs MFC Resolution: Summary: [nfs] Cannot mount / in read-only, over NFS Bug 139651: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=139651 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-fs@FreeBSD.org Status: Needs MFC Resolution: Summary: [nfs] mount(8): read-only remount of NFS volume does not work Bug 144447: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=144447 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-fs@FreeBSD.org Status: Needs MFC Resolution: Summary: [zfs] sharenfs fsunshare() & fsshare_main() non functional Bug 155411: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=155411 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-fs@FreeBSD.org Status: Needs MFC Resolution: Summary: [regression] [8.2-release] [tmpfs]: mount: tmpfs : No space left on device From owner-freebsd-fs@FreeBSD.ORG Mon Jul 28 13:24:36 2014 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D4729DC9 for ; Mon, 28 Jul 2014 13:24:36 +0000 (UTC) Received: from mx2.paymentallianceintl.com (mx2.paymentallianceintl.com [216.26.158.171]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mx2.paymentallianceintl.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5FBAC28CE for ; Mon, 28 Jul 2014 13:24:35 +0000 (UTC) Received: from PAIMAIL.pai.local (paimail.pai.local [10.10.0.153]) by mx2.paymentallianceintl.com (8.14.5/8.13.8) with ESMTP id s6SDNvbj075166 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Mon, 28 Jul 2014 09:23:57 -0400 (EDT) (envelope-from mikej@paymentallianceintl.com) Received: from PAIMAILDR.pai.local (10.10.0.152) by PAIMAIL.pai.local (10.10.0.153) with Microsoft SMTP Server (TLS) id 8.3.348.2; Mon, 28 Jul 2014 09:23:56 -0400 Received: from PAIMAIL.pai.local ([::1]) by PAIMAILDR.pai.local ([::1]) with mapi; Mon, 28 Jul 2014 09:23:56 -0400 From: Michael Jung To: "freebsd-fs@freebsd.org" Date: Mon, 28 Jul 2014 09:23:56 -0400 Subject: r269147 fails to boot after ZFS pool upgrade and new boot code installation Thread-Topic: r269147 fails to boot after ZFS pool upgrade and new boot code installation Thread-Index: Ac+qZY7LvK5LeopFRcu2l4ps0lliww== Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jul 2014 13:24:36 -0000 Everyone, 10-stable r269147: Upgraded the zfs pool and installed new bootcode. The system was working fine prior to upgrading the pool. NOTE: Due to the BIOS not supporting drives > 2TB in ACHI mode this MB is running in legacy IDE mode. I understand the speed implications of this - it is just a test box. ZFS MIRROR BOOT ada0/ada1 gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ad0 gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ad1 Loading Operating System ... ZFS: i/o error - all block copies unavailable ZFS: can't read object set for dataset u ZFS: can't open root filesystem gptzsboot: failed to mount default pool zroot FreBSD/x86 boot Default zroot: boot: I tried to recover using FreeBSD-Stable USB Live CD r268571 but could not import the pool. # zpool import -f -N zroot ZFS filesystem version:5 ZFS storage pool version: feature support (5000) This pool uses the following feature(s) not support by this system: com.delphix:embedded_data cannot impot 'zroot': unsupported version or feature # FreeBSD-11-Current r268622 LIVE CD (USB) imports the pool fine. Only two mirrored drives attached to onboard SATA. Both drives show up in = BIOS as first two boot devices. I attempted to install the r269147 bootcode again like: # zpool import -f -N zroot # mkdir /tmp/zroot # mount -r -t zfs zroot/ROOT/default /tmp/zroot # gpart bootcode -b /tmp/zroot/boot/pmbr -p /tmp/zroot/boot/gptzfsboot -i 1= ada0 # gpart bootcode -b /tmp/zroot/boot/pmbr -p /tmp/zroot/boot/gptzfsboot -i 1= ada1 but resulted in same problem. I also tried installing 11-current bootcode = r268622 which also fails to boot. (I did not export the pool. I even tried power reset after writing bootcod= e) gpart list/show: =3D> 34 5860533101 ada0 GPT (2.7T) 34 6 - free - (3.0K) 40 1024 1 freebsd-boot (512K) 1064 25165824 2 freebsd-swap (12G) 25166888 5835366240 3 freebsd-zfs (2.7T) 5860533128 7 - free - (3.5K) =3D> 34 5860533101 ada1 GPT (2.7T) 34 6 - free - (3.0K) 40 1024 1 freebsd-boot (512K) 1064 25165824 2 freebsd-swap (12G) 25166888 5835366240 3 freebsd-zfs (2.7T) 5860533128 7 - free - (3.5K) Geom name: ada0 modified: false state: OK fwheads: 16 fwsectors: 63 last: 5860533134 first: 34 entries: 128 scheme: GPT Providers: 1. Name: ada0p1 Mediasize: 524288 (512K) Sectorsize: 512 Stripesize: 4096 Stripeoffset: 0 Mode: r0w0e0 rawuuid: 4130f007-f278-11e3-990a-001b211e2e44 rawtype: 83bd6b9d-7f41-11dc-be0b-001560b84f0f label: gptboot0 length: 524288 offset: 20480 type: freebsd-boot index: 1 end: 1063 start: 40 2. Name: ada0p2 Mediasize: 12884901888 (12G) Sectorsize: 512 Stripesize: 4096 Stripeoffset: 0 Mode: r0w0e0 rawuuid: 41809b76-f278-11e3-990a-001b211e2e44 rawtype: 516e7cb5-6ecf-11d6-8ff8-00022d09712b label: swap0 length: 12884901888 offset: 544768 type: freebsd-swap index: 2 end: 25166887 start: 1064 3. Name: ada0p3 Mediasize: 2987707514880 (2.7T) Sectorsize: 512 Stripesize: 4096 Stripeoffset: 0 Mode: r1w1e2 rawuuid: 41ad88b5-f278-11e3-990a-001b211e2e44 rawtype: 516e7cba-6ecf-11d6-8ff8-00022d09712b label: zfs0 length: 2987707514880 offset: 12885446656 type: freebsd-zfs index: 3 end: 5860533127 start: 25166888 Consumers: 1. Name: ada0 Mediasize: 3000592982016 (2.7T) Sectorsize: 512 Stripesize: 4096 Stripeoffset: 0 Mode: r1w1e3 Geom name: ada1 modified: false state: OK fwheads: 16 fwsectors: 63 last: 5860533134 first: 34 entries: 128 scheme: GPT Providers: 1. Name: ada1p1 Mediasize: 524288 (512K) Sectorsize: 512 Stripesize: 4096 Stripeoffset: 0 Mode: r0w0e0 rawuuid: 4260eded-f278-11e3-990a-001b211e2e44 rawtype: 83bd6b9d-7f41-11dc-be0b-001560b84f0f label: gptboot1 length: 524288 offset: 20480 type: freebsd-boot index: 1 end: 1063 start: 40 2. Name: ada1p2 Mediasize: 12884901888 (12G) Sectorsize: 512 Stripesize: 4096 Stripeoffset: 0 Mode: r0w0e0 rawuuid: 42984815-f278-11e3-990a-001b211e2e44 rawtype: 516e7cb5-6ecf-11d6-8ff8-00022d09712b label: swap1 length: 12884901888 offset: 544768 type: freebsd-swap index: 2 end: 25166887 start: 1064 3. Name: ada1p3 Mediasize: 2987707514880 (2.7T) Sectorsize: 512 Stripesize: 4096 Stripeoffset: 0 Mode: r1w1e2 rawuuid: 42c54127-f278-11e3-990a-001b211e2e44 rawtype: 516e7cba-6ecf-11d6-8ff8-00022d09712b label: zfs1 length: 2987707514880 offset: 12885446656 type: freebsd-zfs index: 3 end: 5860533127 start: 25166888 Consumers: 1. Name: ada1 Mediasize: 3000592982016 (2.7T) Sectorsize: 512 Stripesize: 4096 Stripeoffset: 0 Mode: r1w1e3 Geom name: da0 modified: false state: OK fwheads: 255 fwsectors: 63 last: 15633405 first: 3 entries: 4 scheme: GPT Providers: 1. Name: da0p1 Mediasize: 819200 (800K) Sectorsize: 512 Stripesize: 0 Stripeoffset: 1536 Mode: r0w0e0 rawuuid: 71f92853-0b8c-11e4-8fcb-002564f96db2 rawtype: c12a7328-f81f-11d2-ba4b-00a0c93ec93b label: (null) length: 819200 offset: 1536 type: efi index: 1 end: 1602 start: 3 2. Name: da0p2 Mediasize: 16384 (16K) Sectorsize: 512 Stripesize: 0 Stripeoffset: 820736 Mode: r0w0e0 rawuuid: 71f9287f-0b8c-11e4-8fcb-002564f96db2 rawtype: 83bd6b9d-7f41-11dc-be0b-001560b84f0f label: (null) length: 16384 offset: 820736 type: freebsd-boot index: 2 end: 1634 start: 1603 3. Name: da0p3 Mediasize: 697991168 (666M) Sectorsize: 512 Stripesize: 0 Stripeoffset: 837120 Mode: r1w0e1 rawuuid: 71f9288e-0b8c-11e4-8fcb-002564f96db2 rawtype: 516e7cb6-6ecf-11d6-8ff8-00022d09712b label: (null) length: 697991168 offset: 837120 type: freebsd-ufs index: 3 end: 1364898 start: 1635 4. Name: da0p4 Mediasize: 1048576 (1.0M) Sectorsize: 512 Stripesize: 0 Stripeoffset: 698828288 Mode: r0w0e0 rawuuid: 71f9289d-0b8c-11e4-8fcb-002564f96db2 rawtype: 516e7cb5-6ecf-11d6-8ff8-00022d09712b label: (null) length: 1048576 offset: 698828288 type: freebsd-swap index: 4 end: 1366946 start: 1364899 Consumers: 1. Name: da0 Mediasize: 8004304896 (7.5G) Sectorsize: 512 Mode: r1w0e1 Geom name: diskid/DISK-20043512300A4E318DDE modified: false state: OK fwheads: 255 fwsectors: 63 last: 15633405 first: 3 entries: 4 scheme: GPT Providers: 1. Name: diskid/DISK-20043512300A4E318DDEp1 Mediasize: 819200 (800K) Sectorsize: 512 Stripesize: 0 Stripeoffset: 1536 Mode: r0w0e0 rawuuid: 71f92853-0b8c-11e4-8fcb-002564f96db2 rawtype: c12a7328-f81f-11d2-ba4b-00a0c93ec93b label: (null) length: 819200 offset: 1536 type: efi index: 1 end: 1602 start: 3 2. Name: diskid/DISK-20043512300A4E318DDEp2 Mediasize: 16384 (16K) Sectorsize: 512 Stripesize: 0 Stripeoffset: 820736 Mode: r0w0e0 rawuuid: 71f9287f-0b8c-11e4-8fcb-002564f96db2 rawtype: 83bd6b9d-7f41-11dc-be0b-001560b84f0f label: (null) length: 16384 offset: 820736 type: freebsd-boot index: 2 end: 1634 start: 1603 3. Name: diskid/DISK-20043512300A4E318DDEp3 Mediasize: 697991168 (666M) Sectorsize: 512 Stripesize: 0 Stripeoffset: 837120 Mode: r0w0e0 rawuuid: 71f9288e-0b8c-11e4-8fcb-002564f96db2 rawtype: 516e7cb6-6ecf-11d6-8ff8-00022d09712b label: (null) length: 697991168 offset: 837120 type: freebsd-ufs index: 3 end: 1364898 start: 1635 4. Name: diskid/DISK-20043512300A4E318DDEp4 Mediasize: 1048576 (1.0M) Sectorsize: 512 Stripesize: 0 Stripeoffset: 698828288 Mode: r0w0e0 rawuuid: 71f9289d-0b8c-11e4-8fcb-002564f96db2 rawtype: 516e7cb5-6ecf-11d6-8ff8-00022d09712b label: (null) length: 1048576 offset: 698828288 type: freebsd-swap index: 4 end: 1366946 start: 1364899 Consumers: 1. Name: diskid/DISK-20043512300A4E318DDE Mediasize: 8004304896 (7.5G) Sectorsize: 512 Mode: r0w0e0 =1B$B!!=1B(B Any ideas on how to debug this further? Regards, Michael Jung GoPai.com | Facebook.com/PaymentAlliance [cid:iso] CONFIDENTIALITY NOTE: This message is intended only for the use of the individual or entity to whom it is addressed and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, please notify us by telephone at (502) 212-4001 or notify us at PAI , Dept. 99, 6060 Dutchmans Lane, Suite 320, Louisville, KY 40205 From owner-freebsd-fs@FreeBSD.ORG Mon Jul 28 16:07:54 2014 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 25BEDD8B; Mon, 28 Jul 2014 16:07:54 +0000 (UTC) Received: from mail-pa0-x22c.google.com (mail-pa0-x22c.google.com [IPv6:2607:f8b0:400e:c03::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E15602D2A; Mon, 28 Jul 2014 16:07:53 +0000 (UTC) Received: by mail-pa0-f44.google.com with SMTP id eu11so10823196pac.3 for ; Mon, 28 Jul 2014 09:07:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=yp5TauZv/+AhYnH+GsFaMbC9qs/9wQRw8Ft61+mJ6P8=; b=Jb7e0vB/GKvrwCNcf5/UMGOYBgmUDRRx4C92P46hVH6s4FsxcZK9VdcmcquMYG9n+L xXByVP3HVvukKwurdbjo+zoKR3F1jUW8vA4CZjx5TycTBczjFJ0jkNEc2wdFv2nfIzTP tahWLTY/D91bsFnurUkXaFQRvHe5NA5JX7C0zD6qba0Hx5PPt30qnA2rHn+V/krdzCYe +XYdjInpZrTo/m3UocxgNEEgun2nOC0CZfNkBRHtVxmmm57J2na/zWdUqWHDoBDhzj6n M1i6G6OW4v80RvmmboF7dlF26r5lEXRz/yrukjky6hFSdIhWeZ2cQpCjya9zUETMJ2Do RYUg== X-Received: by 10.69.2.35 with SMTP id bl3mr39230690pbd.83.1406563673502; Mon, 28 Jul 2014 09:07:53 -0700 (PDT) Received: from ?IPv6:2601:8:ab80:7d6:9cc1:8b97:b7d9:aa45? ([2601:8:ab80:7d6:9cc1:8b97:b7d9:aa45]) by mx.google.com with ESMTPSA id gb1sm18071177pbd.76.2014.07.28.09.07.52 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 28 Jul 2014 09:07:52 -0700 (PDT) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: [REGRESSION] Root zpool mounting broken between 06/30/2013 and 07/21/2013 when PS/2 support compiled into the kernel From: Garrett Cooper In-Reply-To: Date: Mon, 28 Jul 2014 09:07:52 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <3BFFF901-F5C0-4079-834E-F3199A188EF8@gmail.com> References: <78424E5D-4EB2-4462-A190-D0AC97136790@gmail.com> <201307221208.22060.jhb@freebsd.org> To: John Baldwin X-Mailer: Apple Mail (2.1878.6) Cc: "freebsd-fs@freebsd.org" , "freebsd-stable@freebsd.org" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jul 2014 16:07:54 -0000 On Jul 22, 2013, at 10:58 AM, Garrett Cooper = wrote: > On Jul 22, 2013, at 9:08 AM, John Baldwin wrote: >=20 >> On Monday, July 22, 2013 10:30:32 am Garrett Cooper wrote: >>> I have a KERNCONF that previously had PS/2 support compiled into the = kernel. If I comment out the following lines like so: >>>=20 >>> # atkbdc0 controls both the keyboard and the PS/2 mouse >>> #device atkbdc # AT keyboard controller >>> #device atkbd # AT keyboard >>>=20 >>> then I'm able to mount root again (it was failing with ENOXDEV). >>>=20 >>> The working kernel was as follows: >>>=20 >>> $ strings /boot/kernel.WORKING/kernel | grep -B 2 -A 2 BAYONETTA >>> @(#)FreeBSD 9.1-STABLE #7 r+0304216: Sun Jun 30 15:22:55 PDT 2013 >>> FreeBSD 9.1-STABLE #7 r+0304216: Sun Jun 30 15:22:55 PDT 2013 >>> = gcooper@bayonetta.local:/usr/obj/scratch/git/github/yaneurabeya-freebsd-st= able-9/sys/BAYONETTA >>> gcc version 4.2.1 20070831 patched [FreeBSD] >>> FreeBSD >>> 9.1-STABLE >>> BAYONETTA >>> $ cd /usr/src; git log 0304216 >>> commit 03042167f73c213732b44218a24d8e1bbea00f8c >>> Merge: 2edcad2 974abfb >>> Author: Garrett Cooper >>> Date: Mon Jun 24 19:00:45 2013 -0700 >>>=20 >>> Merge remote-tracking branch 'upstream/stable/9' into stable/9 >>>=20 >>> The working kernel [with atkbdc] was as follows: >>>=20 >>> FreeBSD bayonetta.local 9.2-BETA1 FreeBSD 9.2-BETA1 #12 r+c178034: = Sun Jul 21 20:19:38 PDT 2013 =20 >> = root@bayonetta.local:/usr/obj/scratch/git/github/yaneurabeya-freebsd-stabl= e-9/sys/BAYONETTA amd64 >>> $ git log c178034 >>> commit c17803445f4ffb97e1a46a1be5f7ea04692793f0 >>> Author: avg >>> Date: Tue Jul 9 08:30:31 2013 +0000 >>>=20 >>> zfsboottest.sh: remove checks for things that are not strictly = required >>>=20 >>> MFC after: 10 days >>>=20 >>> (Yes, I had to backport some things because they are busted on = stable/9 due to other incomplete/missing MFCs). >>>=20 >>> I can test out patches, but I don't have time to bisect the actual = commit that caused the failure. That being said my intuition says it's = this >> commit should be looked at first: >>>=20 >>> commit 28f961058b0667841d7e9d8639bfd02ed8689faa >>> Author: jhb >>> Date: Wed Jul 17 14:04:18 2013 +0000 >>>=20 >>> MFC 252576: >>> Don't perform the acpi_DeviceIsPresent() check for PCI-PCI = bridges. If >>> we are probing a PCI-PCI bridge it is because we found one by = enumerating >>> the devices on a PCI bus, so the bridge is definitely present. A = few >>> BIOSes report incorrect status (_STA) for some bridges that = claimed they >>> were not present when in fact they were. >>>=20 >>> While here, move this check earlier for Host-PCI bridges so attach = fails >>> before doing any work that needs to be torn down. >>>=20 >>> PR: kern/91594 >>> Approved by: re (marius) >>=20 >> I strongly doubt that this is related. It would be most helpful if = you could >> obtain a dmesg from the new kernel however (perhaps via a serial = console) to >> rule it out. All you would need to see is if the new kernel sees = more "pcib" >> devices than the old one to see if this change even has an effect on = your >> system. >=20 > Unfortunately the USB keyboard is broken as well at the mount root = prompt and the workstation doesn't have a uart on it that I can play = with (it's my home box), so I'm dead in the water when it panics at the = mount root prompt right now. >=20 > I guess I can revert this and a handful of other amd64/ata_cam/zfs = commits to see if this goes away, but I won't be getting to that before = next Sunday probably as this is my file server and DNS server now. I ran into the issue going from vanilla 9.2-RELEASE-p10 to = 9.3-RELEASE as well :(. I=92ve filed this bug to track the issue: = https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D192183 . I=92ll see = if GENERIC can boot my system sometime this week (the KERNCONF has been = working for several releases, but it could be an issue with that that=92s = being overlooked by accident). Thanks! -Garrett From owner-freebsd-fs@FreeBSD.ORG Mon Jul 28 16:37:06 2014 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AF6187C8; Mon, 28 Jul 2014 16:37:06 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5841D218E; Mon, 28 Jul 2014 16:37:06 +0000 (UTC) Received: from [192.168.1.75] (75-48-77-17.lightspeed.cncrca.sbcglobal.net [75.48.77.17]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id C79B7B949; Mon, 28 Jul 2014 12:37:03 -0400 (EDT) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: [REGRESSION] Root zpool mounting broken between 06/30/2013 and 07/21/2013 when PS/2 support compiled into the kernel From: John Baldwin In-Reply-To: <3BFFF901-F5C0-4079-834E-F3199A188EF8@gmail.com> Date: Mon, 28 Jul 2014 09:37:01 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <95A4D9A9-9D69-4258-A1EC-CBC6DC2F49FF@FreeBSD.org> References: <78424E5D-4EB2-4462-A190-D0AC97136790@gmail.com> <201307221208.22060.jhb@freebsd.org> <3BFFF901-F5C0-4079-834E-F3199A188EF8@gmail.com> To: Garrett Cooper X-Mailer: Apple Mail (2.1878.6) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Mon, 28 Jul 2014 12:37:04 -0400 (EDT) Cc: "freebsd-fs@freebsd.org" , "freebsd-stable@freebsd.org" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jul 2014 16:37:06 -0000 On Jul 28, 2014, at 9:07 AM, Garrett Cooper = wrote: > On Jul 22, 2013, at 10:58 AM, Garrett Cooper = wrote: >=20 >> On Jul 22, 2013, at 9:08 AM, John Baldwin wrote: >>=20 >>> On Monday, July 22, 2013 10:30:32 am Garrett Cooper wrote: >>>> I have a KERNCONF that previously had PS/2 support compiled into = the kernel. If I comment out the following lines like so: >>>>=20 >>>> # atkbdc0 controls both the keyboard and the PS/2 mouse >>>> #device atkbdc # AT keyboard controller >>>> #device atkbd # AT keyboard >>>>=20 >>>> then I'm able to mount root again (it was failing with ENOXDEV). >>>>=20 >>>> The working kernel was as follows: >>>>=20 >>>> $ strings /boot/kernel.WORKING/kernel | grep -B 2 -A 2 BAYONETTA >>>> @(#)FreeBSD 9.1-STABLE #7 r+0304216: Sun Jun 30 15:22:55 PDT 2013 >>>> FreeBSD 9.1-STABLE #7 r+0304216: Sun Jun 30 15:22:55 PDT 2013 >>>> = gcooper@bayonetta.local:/usr/obj/scratch/git/github/yaneurabeya-freebsd-st= able-9/sys/BAYONETTA >>>> gcc version 4.2.1 20070831 patched [FreeBSD] >>>> FreeBSD >>>> 9.1-STABLE >>>> BAYONETTA >>>> $ cd /usr/src; git log 0304216 >>>> commit 03042167f73c213732b44218a24d8e1bbea00f8c >>>> Merge: 2edcad2 974abfb >>>> Author: Garrett Cooper >>>> Date: Mon Jun 24 19:00:45 2013 -0700 >>>>=20 >>>> Merge remote-tracking branch 'upstream/stable/9' into stable/9 >>>>=20 >>>> The working kernel [with atkbdc] was as follows: >>>>=20 >>>> FreeBSD bayonetta.local 9.2-BETA1 FreeBSD 9.2-BETA1 #12 r+c178034: = Sun Jul 21 20:19:38 PDT 2013 =20 >>> = root@bayonetta.local:/usr/obj/scratch/git/github/yaneurabeya-freebsd-stabl= e-9/sys/BAYONETTA amd64 >>>> $ git log c178034 >>>> commit c17803445f4ffb97e1a46a1be5f7ea04692793f0 >>>> Author: avg >>>> Date: Tue Jul 9 08:30:31 2013 +0000 >>>>=20 >>>> zfsboottest.sh: remove checks for things that are not strictly = required >>>>=20 >>>> MFC after: 10 days >>>>=20 >>>> (Yes, I had to backport some things because they are busted on = stable/9 due to other incomplete/missing MFCs). >>>>=20 >>>> I can test out patches, but I don't have time to bisect the actual = commit that caused the failure. That being said my intuition says it's = this >>> commit should be looked at first: >>>>=20 >>>> commit 28f961058b0667841d7e9d8639bfd02ed8689faa >>>> Author: jhb >>>> Date: Wed Jul 17 14:04:18 2013 +0000 >>>>=20 >>>> MFC 252576: >>>> Don't perform the acpi_DeviceIsPresent() check for PCI-PCI = bridges. If >>>> we are probing a PCI-PCI bridge it is because we found one by = enumerating >>>> the devices on a PCI bus, so the bridge is definitely present. A = few >>>> BIOSes report incorrect status (_STA) for some bridges that = claimed they >>>> were not present when in fact they were. >>>>=20 >>>> While here, move this check earlier for Host-PCI bridges so attach = fails >>>> before doing any work that needs to be torn down. >>>>=20 >>>> PR: kern/91594 >>>> Approved by: re (marius) >>>=20 >>> I strongly doubt that this is related. It would be most helpful if = you could >>> obtain a dmesg from the new kernel however (perhaps via a serial = console) to >>> rule it out. All you would need to see is if the new kernel sees = more "pcib" >>> devices than the old one to see if this change even has an effect on = your >>> system. >>=20 >> Unfortunately the USB keyboard is broken as well at the mount root = prompt and the workstation doesn't have a uart on it that I can play = with (it's my home box), so I'm dead in the water when it panics at the = mount root prompt right now. >>=20 >> I guess I can revert this and a handful of other amd64/ata_cam/zfs = commits to see if this goes away, but I won't be getting to that before = next Sunday probably as this is my file server and DNS server now. >=20 > I ran into the issue going from vanilla 9.2-RELEASE-p10 to = 9.3-RELEASE as well :(. I=92ve filed this bug to track the issue: = https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D192183 . I=92ll see = if GENERIC can boot my system sometime this week (the KERNCONF has been = working for several releases, but it could be an issue with that that=92s = being overlooked by accident). > Thanks! There is basically zero chance that the commit in question can cause = this. Also, you would need to get verbose dmesg's of old and new = kernels as a first step in narrowing it down. --=20 John Baldwin From owner-freebsd-fs@FreeBSD.ORG Mon Jul 28 16:57:09 2014 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C159F1A6; Mon, 28 Jul 2014 16:57:09 +0000 (UTC) Received: from mail-ig0-x235.google.com (mail-ig0-x235.google.com [IPv6:2607:f8b0:4001:c05::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7A9D02462; Mon, 28 Jul 2014 16:57:09 +0000 (UTC) Received: by mail-ig0-f181.google.com with SMTP id h3so3924416igd.8 for ; Mon, 28 Jul 2014 09:57:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=9xyT82B/BhtPHkcW9Qy/IfunNscqwEV7qbVPPIUz4fc=; b=Vehph17EyiMNF4uqrn1muHazUd1Nl/gDU+gLKTxYKzJZSoZuC7ZfjskUv93iYpQHox RSBtEXQ0JwLVIUVd3WkTqNelw5r5n0ZbbmqQljTmatproL867wNaLP1C7zOGTVfQLpCL xnvtwkastu3cbaPQkhz8h4N5PJ/4nulekXcSUnUYtIQGqNujDzkZzkWSJUX63KqNOnxs H48WFXBtidAHaKr/gZcUoaQEfGAZzpXEcJoWq3Rvw7Fc/7uvnGmXwVdckV964e/0Fdxb mTAFvx8SEvsShCf0YOjB3uu114P83V+e/5qYBg9dw8lc7wqs9rZf0TWZbiw9MH50Y1lX RxQQ== MIME-Version: 1.0 X-Received: by 10.42.198.75 with SMTP id en11mr44210448icb.7.1406566628805; Mon, 28 Jul 2014 09:57:08 -0700 (PDT) Received: by 10.50.213.102 with HTTP; Mon, 28 Jul 2014 09:57:08 -0700 (PDT) In-Reply-To: <95A4D9A9-9D69-4258-A1EC-CBC6DC2F49FF@FreeBSD.org> References: <78424E5D-4EB2-4462-A190-D0AC97136790@gmail.com> <201307221208.22060.jhb@freebsd.org> <3BFFF901-F5C0-4079-834E-F3199A188EF8@gmail.com> <95A4D9A9-9D69-4258-A1EC-CBC6DC2F49FF@FreeBSD.org> Date: Mon, 28 Jul 2014 09:57:08 -0700 Message-ID: Subject: Re: [REGRESSION] Root zpool mounting broken between 06/30/2013 and 07/21/2013 when PS/2 support compiled into the kernel From: Garrett Cooper To: John Baldwin Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-fs@freebsd.org" , "freebsd-stable@freebsd.org" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jul 2014 16:57:09 -0000 On Mon, Jul 28, 2014 at 9:37 AM, John Baldwin wrote: > > On Jul 28, 2014, at 9:07 AM, Garrett Cooper wrote= : > >> On Jul 22, 2013, at 10:58 AM, Garrett Cooper wro= te: >> >>> On Jul 22, 2013, at 9:08 AM, John Baldwin wrote: >>> >>>> On Monday, July 22, 2013 10:30:32 am Garrett Cooper wrote: >>>>> I have a KERNCONF that previously had PS/2 support compiled into the = kernel. If I comment out the following lines like so: >>>>> >>>>> # atkbdc0 controls both the keyboard and the PS/2 mouse >>>>> #device atkbdc # AT keyboard controller >>>>> #device atkbd # AT keyboard >>>>> >>>>> then I'm able to mount root again (it was failing with ENOXDEV). >>>>> >>>>> The working kernel was as follows: >>>>> >>>>> $ strings /boot/kernel.WORKING/kernel | grep -B 2 -A 2 BAYONETTA >>>>> @(#)FreeBSD 9.1-STABLE #7 r+0304216: Sun Jun 30 15:22:55 PDT 2013 >>>>> FreeBSD 9.1-STABLE #7 r+0304216: Sun Jun 30 15:22:55 PDT 2013 >>>>> gcooper@bayonetta.local:/usr/obj/scratch/git/github/yaneurabeya-free= bsd-stable-9/sys/BAYONETTA >>>>> gcc version 4.2.1 20070831 patched [FreeBSD] >>>>> FreeBSD >>>>> 9.1-STABLE >>>>> BAYONETTA >>>>> $ cd /usr/src; git log 0304216 >>>>> commit 03042167f73c213732b44218a24d8e1bbea00f8c >>>>> Merge: 2edcad2 974abfb >>>>> Author: Garrett Cooper >>>>> Date: Mon Jun 24 19:00:45 2013 -0700 >>>>> >>>>> Merge remote-tracking branch 'upstream/stable/9' into stable/9 >>>>> >>>>> The working kernel [with atkbdc] was as follows: >>>>> >>>>> FreeBSD bayonetta.local 9.2-BETA1 FreeBSD 9.2-BETA1 #12 r+c178034: Su= n Jul 21 20:19:38 PDT 2013 >>>> root@bayonetta.local:/usr/obj/scratch/git/github/yaneurabeya-freebsd-s= table-9/sys/BAYONETTA amd64 >>>>> $ git log c178034 >>>>> commit c17803445f4ffb97e1a46a1be5f7ea04692793f0 >>>>> Author: avg >>>>> Date: Tue Jul 9 08:30:31 2013 +0000 >>>>> >>>>> zfsboottest.sh: remove checks for things that are not strictly requi= red >>>>> >>>>> MFC after: 10 days >>>>> >>>>> (Yes, I had to backport some things because they are busted on stable= /9 due to other incomplete/missing MFCs). >>>>> >>>>> I can test out patches, but I don't have time to bisect the actual co= mmit that caused the failure. That being said my intuition says it's this >>>> commit should be looked at first: >>>>> >>>>> commit 28f961058b0667841d7e9d8639bfd02ed8689faa >>>>> Author: jhb >>>>> Date: Wed Jul 17 14:04:18 2013 +0000 >>>>> >>>>> MFC 252576: >>>>> Don't perform the acpi_DeviceIsPresent() check for PCI-PCI bridges. = If >>>>> we are probing a PCI-PCI bridge it is because we found one by enumer= ating >>>>> the devices on a PCI bus, so the bridge is definitely present. A fe= w >>>>> BIOSes report incorrect status (_STA) for some bridges that claimed = they >>>>> were not present when in fact they were. >>>>> >>>>> While here, move this check earlier for Host-PCI bridges so attach f= ails >>>>> before doing any work that needs to be torn down. >>>>> >>>>> PR: kern/91594 >>>>> Approved by: re (marius) >>>> >>>> I strongly doubt that this is related. It would be most helpful if yo= u could >>>> obtain a dmesg from the new kernel however (perhaps via a serial conso= le) to >>>> rule it out. All you would need to see is if the new kernel sees more= "pcib" >>>> devices than the old one to see if this change even has an effect on y= our >>>> system. >>> >>> Unfortunately the USB keyboard is broken as well at the mount root prom= pt and the workstation doesn't have a uart on it that I can play with (it's= my home box), so I'm dead in the water when it panics at the mount root pr= ompt right now. >>> >>> I guess I can revert this and a handful of other amd64/ata_cam/zfs comm= its to see if this goes away, but I won't be getting to that before next Su= nday probably as this is my file server and DNS server now. >> >> I ran into the issue going from vanilla 9.2-RELEASE-p10 to 9.3-REL= EASE as well :(. I=E2=80=99ve filed this bug to track the issue: https://bu= gs.freebsd.org/bugzilla/show_bug.cgi?id=3D192183 . I=E2=80=99ll see if GENE= RIC can boot my system sometime this week (the KERNCONF has been working fo= r several releases, but it could be an issue with that that=E2=80=99s being= overlooked by accident). >> Thanks! ... > Also, you would need to get verbose dmesg's of old and new kernels as a f= irst step in narrowing it down. I can't do trivial debugging because my USB keyboard doesn't work at the mountroot prompt ( https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D133989 ), I don't have a PS/2 keyboard, and the system only has VGA access :(. I'll try working on disabling the PS/2 controller in the BIOS and a few other things to force the system to stop ignoring the USB keyboard to get scrollback, because that appeared to work for some folks with this issue according to the ukbd bug I referenced. -Garrett From owner-freebsd-fs@FreeBSD.ORG Tue Jul 29 01:33:18 2014 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E6A3D195; Tue, 29 Jul 2014 01:33:18 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AAE86203A; Tue, 29 Jul 2014 01:33:18 +0000 (UTC) Received: from pippin.baldwin.cx (75-48-77-17.lightspeed.cncrca.sbcglobal.net [75.48.77.17]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id A35D5B94B; Mon, 28 Jul 2014 21:33:16 -0400 (EDT) From: John Baldwin To: Garrett Cooper Subject: Re: [REGRESSION] Root zpool mounting broken between 06/30/2013 and 07/21/2013 when PS/2 support compiled into the kernel Date: Mon, 28 Jul 2014 21:32:24 -0400 Message-ID: <10421077.Qp3biFQLVt@pippin.baldwin.cx> User-Agent: KMail/4.12.5 (FreeBSD/11.0-CURRENT; KDE/4.12.5; amd64; ; ) In-Reply-To: References: <78424E5D-4EB2-4462-A190-D0AC97136790@gmail.com> <95A4D9A9-9D69-4258-A1EC-CBC6DC2F49FF@FreeBSD.org> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Mon, 28 Jul 2014 21:33:16 -0400 (EDT) Cc: "freebsd-fs@freebsd.org" , "freebsd-stable@freebsd.org" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jul 2014 01:33:19 -0000 On Monday 28 July 2014 09:57:08 Garrett Cooper wrote: > On Mon, Jul 28, 2014 at 9:37 AM, John Baldwin wrote= : > > On Jul 28, 2014, at 9:07 AM, Garrett Cooper = wrote: > >> On Jul 22, 2013, at 10:58 AM, Garrett Cooper =20 wrote: > >>> On Jul 22, 2013, at 9:08 AM, John Baldwin wrote= : > >>>> On Monday, July 22, 2013 10:30:32 am Garrett Cooper wrote: > >>>>> I have a KERNCONF that previously had PS/2 support compiled int= o the > >>>>> kernel. If I comment out the following lines like so: > >>>>>=20 > >>>>> # atkbdc0 controls both the keyboard and the PS/2 mouse > >>>>> #device atkbdc # AT keyboard controller > >>>>> #device atkbd # AT keyboard > >>>>>=20 > >>>>> then I'm able to mount root again (it was failing with ENOXDEV)= . > >>>>>=20 > >>>>> The working kernel was as follows: > >>>>>=20 > >>>>> $ strings /boot/kernel.WORKING/kernel | grep -B 2 -A 2 BAYONETT= A > >>>>> @(#)FreeBSD 9.1-STABLE #7 r+0304216: Sun Jun 30 15:22:55 PDT 20= 13 > >>>>> FreeBSD 9.1-STABLE #7 r+0304216: Sun Jun 30 15:22:55 PDT 2013 > >>>>>=20 > >>>>> gcooper@bayonetta.local:/usr/obj/scratch/git/github/yaneurabey= a-freeb > >>>>> sd-stable-9/sys/BAYONETTA>>>>>=20 > >>>>> gcc version 4.2.1 20070831 patched [FreeBSD] > >>>>> FreeBSD > >>>>> 9.1-STABLE > >>>>> BAYONETTA > >>>>> $ cd /usr/src; git log 0304216 > >>>>> commit 03042167f73c213732b44218a24d8e1bbea00f8c > >>>>> Merge: 2edcad2 974abfb > >>>>> Author: Garrett Cooper > >>>>> Date: Mon Jun 24 19:00:45 2013 -0700 > >>>>>=20 > >>>>> Merge remote-tracking branch 'upstream/stable/9' into stable/9= > >>>>>=20 > >>>>> The working kernel [with atkbdc] was as follows: > >>>>>=20 > >>>>> FreeBSD bayonetta.local 9.2-BETA1 FreeBSD 9.2-BETA1 #12 r+c1780= 34: Sun > >>>>> Jul 21 20:19:38 PDT 2013>>>>=20 > >>>> root@bayonetta.local:/usr/obj/scratch/git/github/yaneurabeya-fre= ebsd-st > >>>> able-9/sys/BAYONETTA amd64>>>>=20 > >>>>> $ git log c178034 > >>>>> commit c17803445f4ffb97e1a46a1be5f7ea04692793f0 > >>>>> Author: avg > >>>>> Date: Tue Jul 9 08:30:31 2013 +0000 > >>>>>=20 > >>>>> zfsboottest.sh: remove checks for things that are not strictly= > >>>>> required > >>>>> =20 > >>>>> MFC after: 10 days > >>>>>=20 > >>>>> (Yes, I had to backport some things because they are busted on > >>>>> stable/9 due to other incomplete/missing MFCs). > >>>>>=20 > >>>>> I can test out patches, but I don't have time to bisect the act= ual > >>>>> commit that caused the failure. That being said my intuition sa= ys > >>>>> it's this>>>>=20 > >>>> commit should be looked at first: > >>>>> commit 28f961058b0667841d7e9d8639bfd02ed8689faa > >>>>> Author: jhb > >>>>> Date: Wed Jul 17 14:04:18 2013 +0000 > >>>>>=20 > >>>>> MFC 252576: > >>>>> Don't perform the acpi_DeviceIsPresent() check for PCI-PCI bri= dges.=20 > >>>>> If > >>>>> we are probing a PCI-PCI bridge it is because we found one by > >>>>> enumerating > >>>>> the devices on a PCI bus, so the bridge is definitely present.= A few > >>>>> BIOSes report incorrect status (_STA) for some bridges that cl= aimed > >>>>> they > >>>>> were not present when in fact they were. > >>>>> =20 > >>>>> While here, move this check earlier for Host-PCI bridges so at= tach > >>>>> fails > >>>>> before doing any work that needs to be torn down. > >>>>> =20 > >>>>> PR: kern/91594 > >>>>> Approved by: re (marius) > >>>>=20 > >>>> I strongly doubt that this is related. It would be most helpful= if you > >>>> could obtain a dmesg from the new kernel however (perhaps via a = serial > >>>> console) to rule it out. All you would need to see is if the ne= w > >>>> kernel sees more "pcib" devices than the old one to see if this = change > >>>> even has an effect on your system. > >>>=20 > >>> Unfortunately the USB keyboard is broken as well at the mount roo= t > >>> prompt and the workstation doesn't have a uart on it that I can p= lay > >>> with (it's my home box), so I'm dead in the water when it panics = at the > >>> mount root prompt right now. > >>>=20 > >>> I guess I can revert this and a handful of other amd64/ata_cam/zf= s > >>> commits to see if this goes away, but I won't be getting to that = before > >>> next Sunday probably as this is my file server and DNS server now= .>>>=20 > >> I ran into the issue going from vanilla 9.2-RELEASE-p10 to > >> 9.3-RELEASE as well :(. I=E2=80=99ve filed this bug to track= the issue: > >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D192183 .= I=E2=80=99ll > >> see if GENERIC can boot my system sometime this week (the KE= RNCONF > >> has been working for several releases, but it could be an is= sue > >> with that that=E2=80=99s being overlooked by accident).>>=20= > >> Thanks! >=20 > ... >=20 > > Also, you would need to get verbose dmesg's of old and new kernels = as a > > first step in narrowing it down. > I can't do trivial debugging because my USB keyboard doesn't work at > the mountroot prompt ( > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D133989 ), I don't= > have a PS/2 keyboard, and the system only has VGA access :(. I'll try= > working on disabling the PS/2 controller in the BIOS and a few other > things to force the system to stop ignoring the USB keyboard to get > scrollback, because that appeared to work for some folks with this > issue according to the ukbd bug I referenced. Do you have a serial port so you could use a serial console (or is this= a=20 laptop)? --=20 John Baldwin From owner-freebsd-fs@FreeBSD.ORG Wed Jul 30 10:51:27 2014 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 350928F2; Wed, 30 Jul 2014 10:51:27 +0000 (UTC) Received: from mail-pa0-x234.google.com (mail-pa0-x234.google.com [IPv6:2607:f8b0:400e:c03::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F00E62ACE; Wed, 30 Jul 2014 10:51:26 +0000 (UTC) Received: by mail-pa0-f52.google.com with SMTP id bj1so1311442pad.39 for ; Wed, 30 Jul 2014 03:51:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=1k69CfV87RE1BNtfzMghnIWBoXgJmb1tQuRSkAs0d0Y=; b=wTTtuEVQesWQRhs+kOv/h5RS1YMCmyz6yCoMtY7g0rW4QHltulJ8e6s74PN8IBx2zi ze95W5ngtz/3RuOuIB4kLJb6jQOSIQq5EzKsmjhYm9IAIw/GEM6pyq9IvPVDykXwxFnE J70iYFZj+nOeSlFY5e4+2cnRym/pcsoqsQh6bF5JcXZ0NlDCwzUhR2u5eBGY2OhVGfNM ompIOoWpeAGwbqU5KCiMTvompnP4Bam1aQCvtf7+UJEWCCfAsqAIO1jJ4si9YPOxTMco LQEE3oVt7YYhtL6kvi1a7nHxI0ptipIInr5Mal04APyvc17rQipY+W2Lu4OlsL9qesnB NqWw== X-Received: by 10.70.37.129 with SMTP id y1mr3714934pdj.12.1406717486174; Wed, 30 Jul 2014 03:51:26 -0700 (PDT) Received: from ?IPv6:2601:8:ab80:7d6:4de3:c604:bd4e:bab2? ([2601:8:ab80:7d6:4de3:c604:bd4e:bab2]) by mx.google.com with ESMTPSA id da14sm6775014pac.24.2014.07.30.03.51.25 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 30 Jul 2014 03:51:25 -0700 (PDT) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: [REGRESSION] Root zpool mounting broken between 06/30/2013 and 07/21/2013 when PS/2 support compiled into the kernel From: Garrett Cooper In-Reply-To: <10421077.Qp3biFQLVt@pippin.baldwin.cx> Date: Wed, 30 Jul 2014 03:51:24 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <78424E5D-4EB2-4462-A190-D0AC97136790@gmail.com> <95A4D9A9-9D69-4258-A1EC-CBC6DC2F49FF@FreeBSD.org> <10421077.Qp3biFQLVt@pippin.baldwin.cx> To: John Baldwin X-Mailer: Apple Mail (2.1878.6) Cc: "freebsd-fs@freebsd.org" , "freebsd-stable@freebsd.org" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jul 2014 10:51:27 -0000 On Jul 28, 2014, at 6:32 PM, John Baldwin wrote: > On Monday 28 July 2014 09:57:08 Garrett Cooper wrote: >> On Mon, Jul 28, 2014 at 9:37 AM, John Baldwin = wrote: >>> On Jul 28, 2014, at 9:07 AM, Garrett Cooper = wrote: >>>> On Jul 22, 2013, at 10:58 AM, Garrett Cooper = =20 > wrote: >>>>> On Jul 22, 2013, at 9:08 AM, John Baldwin wrote: >>>>>> On Monday, July 22, 2013 10:30:32 am Garrett Cooper wrote: >>>>>>> I have a KERNCONF that previously had PS/2 support compiled into = the >>>>>>> kernel. If I comment out the following lines like so: >>>>>>>=20 >>>>>>> # atkbdc0 controls both the keyboard and the PS/2 mouse >>>>>>> #device atkbdc # AT keyboard controller >>>>>>> #device atkbd # AT keyboard >>>>>>>=20 >>>>>>> then I'm able to mount root again (it was failing with ENOXDEV). >>>>>>>=20 >>>>>>> The working kernel was as follows: >>>>>>>=20 >>>>>>> $ strings /boot/kernel.WORKING/kernel | grep -B 2 -A 2 BAYONETTA >>>>>>> @(#)FreeBSD 9.1-STABLE #7 r+0304216: Sun Jun 30 15:22:55 PDT = 2013 >>>>>>> FreeBSD 9.1-STABLE #7 r+0304216: Sun Jun 30 15:22:55 PDT 2013 >>>>>>>=20 >>>>>>> = gcooper@bayonetta.local:/usr/obj/scratch/git/github/yaneurabeya-freeb >>>>>>> sd-stable-9/sys/BAYONETTA>>>>>=20 >>>>>>> gcc version 4.2.1 20070831 patched [FreeBSD] >>>>>>> FreeBSD >>>>>>> 9.1-STABLE >>>>>>> BAYONETTA >>>>>>> $ cd /usr/src; git log 0304216 >>>>>>> commit 03042167f73c213732b44218a24d8e1bbea00f8c >>>>>>> Merge: 2edcad2 974abfb >>>>>>> Author: Garrett Cooper >>>>>>> Date: Mon Jun 24 19:00:45 2013 -0700 >>>>>>>=20 >>>>>>> Merge remote-tracking branch 'upstream/stable/9' into stable/9 >>>>>>>=20 >>>>>>> The working kernel [with atkbdc] was as follows: >>>>>>>=20 >>>>>>> FreeBSD bayonetta.local 9.2-BETA1 FreeBSD 9.2-BETA1 #12 = r+c178034: Sun >>>>>>> Jul 21 20:19:38 PDT 2013>>>>=20 >>>>>> = root@bayonetta.local:/usr/obj/scratch/git/github/yaneurabeya-freebsd-st >>>>>> able-9/sys/BAYONETTA amd64>>>>=20 >>>>>>> $ git log c178034 >>>>>>> commit c17803445f4ffb97e1a46a1be5f7ea04692793f0 >>>>>>> Author: avg >>>>>>> Date: Tue Jul 9 08:30:31 2013 +0000 >>>>>>>=20 >>>>>>> zfsboottest.sh: remove checks for things that are not strictly >>>>>>> required >>>>>>>=20 >>>>>>> MFC after: 10 days >>>>>>>=20 >>>>>>> (Yes, I had to backport some things because they are busted on >>>>>>> stable/9 due to other incomplete/missing MFCs). >>>>>>>=20 >>>>>>> I can test out patches, but I don't have time to bisect the = actual >>>>>>> commit that caused the failure. That being said my intuition = says >>>>>>> it's this>>>>=20 >>>>>> commit should be looked at first: >>>>>>> commit 28f961058b0667841d7e9d8639bfd02ed8689faa >>>>>>> Author: jhb >>>>>>> Date: Wed Jul 17 14:04:18 2013 +0000 >>>>>>>=20 >>>>>>> MFC 252576: >>>>>>> Don't perform the acpi_DeviceIsPresent() check for PCI-PCI = bridges.=20 >>>>>>> If >>>>>>> we are probing a PCI-PCI bridge it is because we found one by >>>>>>> enumerating >>>>>>> the devices on a PCI bus, so the bridge is definitely present. = A few >>>>>>> BIOSes report incorrect status (_STA) for some bridges that = claimed >>>>>>> they >>>>>>> were not present when in fact they were. >>>>>>>=20 >>>>>>> While here, move this check earlier for Host-PCI bridges so = attach >>>>>>> fails >>>>>>> before doing any work that needs to be torn down. >>>>>>>=20 >>>>>>> PR: kern/91594 >>>>>>> Approved by: re (marius) >>>>>>=20 >>>>>> I strongly doubt that this is related. It would be most helpful = if you >>>>>> could obtain a dmesg from the new kernel however (perhaps via a = serial >>>>>> console) to rule it out. All you would need to see is if the new >>>>>> kernel sees more "pcib" devices than the old one to see if this = change >>>>>> even has an effect on your system. >>>>>=20 >>>>> Unfortunately the USB keyboard is broken as well at the mount root >>>>> prompt and the workstation doesn't have a uart on it that I can = play >>>>> with (it's my home box), so I'm dead in the water when it panics = at the >>>>> mount root prompt right now. >>>>>=20 >>>>> I guess I can revert this and a handful of other amd64/ata_cam/zfs >>>>> commits to see if this goes away, but I won't be getting to that = before >>>>> next Sunday probably as this is my file server and DNS server = now.>>>=20 >>>> I ran into the issue going from vanilla 9.2-RELEASE-p10 to >>>> 9.3-RELEASE as well :(. I=92ve filed this bug to track the = issue: >>>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D192183 . = I=92ll >>>> see if GENERIC can boot my system sometime this week (the = KERNCONF >>>> has been working for several releases, but it could be an = issue >>>> with that that=92s being overlooked by accident).>>=20 >>>> Thanks! >>=20 >> ... >>=20 >>> Also, you would need to get verbose dmesg's of old and new kernels = as a >>> first step in narrowing it down. >> I can't do trivial debugging because my USB keyboard doesn't work at >> the mountroot prompt ( >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D133989 ), I don't >> have a PS/2 keyboard, and the system only has VGA access :(. I'll try >> working on disabling the PS/2 controller in the BIOS and a few other >> things to force the system to stop ignoring the USB keyboard to get >> scrollback, because that appeared to work for some folks with this >> issue according to the ukbd bug I referenced. >=20 > Do you have a serial port so you could use a serial console (or is = this a=20 > laptop)? I wish my motherboard had an RS232 port, but unfortunately it doesn=92t; = I don=92t have 2 USB RS-232 converters either (and I=92m not sure a USB = serial adapter would work for boot2sio, would it?) :/. If the legacy USB keyboard route doesn=92t work out, I have a USB to = PS/2 converter coming in the mail. It would be nice if bug 133989 was fixed. I=92ll talk to hps@ about it=85 Thanks! -Garrett= From owner-freebsd-fs@FreeBSD.ORG Thu Jul 31 04:15:50 2014 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 13F298DD; Thu, 31 Jul 2014 04:15:50 +0000 (UTC) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id E43B920DD; Thu, 31 Jul 2014 04:15:49 +0000 (UTC) Received: from [192.168.1.2] (senat1-01.HML3.ScaleEngine.net [209.51.186.5]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 7188431946; Thu, 31 Jul 2014 04:15:47 +0000 (UTC) Message-ID: <53D9C306.6060105@freebsd.org> Date: Thu, 31 Jul 2014 00:16:06 -0400 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: delphij@freebsd.org Subject: panic: avl_find() succeeded inside avl_add() X-Enigmail-Version: 1.6 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="qR1OjgssFm2uN0pMnAKugE67TmBlctcaV" Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jul 2014 04:15:50 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --qR1OjgssFm2uN0pMnAKugE67TmBlctcaV Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I updated one of our storage servers to the latest -CURRENT yesterday and now it is panic'ing every few minutes I suspect this is related to r269229 (MFV r269223) Jul 31 03:25:23 Tango syslogd: kernel boot file is /boot/kernel/kernel Jul 31 03:25:23 Tango kernel: panic: avl_find() succeeded inside avl_add(= ) Jul 31 03:25:23 Tango kernel: cpuid =3D 0 Jul 31 03:25:23 Tango kernel: KDB: stack backtrace: Jul 31 03:25:23 Tango kernel: #0 0xffffffff809ab070 at kdb_backtrace+0x60= Jul 31 03:25:23 Tango kernel: #1 0xffffffff8096c3a5 at panic+0x155 Jul 31 03:25:23 Tango kernel: #2 0xffffffff819dbc04 at avl_add+0x84 Jul 31 03:25:23 Tango kernel: #3 0xffffffff81a04560 at dbuf_create+0x390 Jul 31 03:25:23 Tango kernel: #4 0xffffffff81a03f5a at dbuf_hold_impl+0x1= 1a Jul 31 03:25:23 Tango kernel: #5 0xffffffff81a0467b at dbuf_hold+0x1b Jul 31 03:25:23 Tango kernel: #6 0xffffffff81a09593 at dmu_buf_hold_array_by_dnode+0x153 Jul 31 03:25:23 Tango kernel: #7 0xffffffff81a0a526 at dmu_read_uio+0x66 Jul 31 03:25:23 Tango kernel: #8 0xffffffff81a9bb0a at zfs_freebsd_read+0x58a Jul 31 03:25:23 Tango kernel: #9 0xffffffff80eddf11 at VOP_READ_APV+0xa1 Jul 31 03:25:23 Tango kernel: #10 0xffffffff80a32427 at vn_read+0x167 Jul 31 03:25:23 Tango kernel: #11 0xffffffff80a2e5db at vn_io_fault+0x10b= Jul 31 03:25:23 Tango kernel: #12 0xffffffff809c4a95 at dofileread+0x95 Jul 31 03:25:23 Tango kernel: #13 0xffffffff809c47b8 at kern_readv+0x68 Jul 31 03:25:23 Tango kernel: #14 0xffffffff809c4743 at sys_read+0x63 Jul 31 03:25:23 Tango kernel: #15 0xffffffff80db84fb at amd64_syscall+0x3= fb Jul 31 03:25:23 Tango kernel: #16 0xffffffff80d9a47b at Xfast_syscall+0xf= b Jul 31 03:25:23 Tango kernel: Uptime: 12m11s https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D192284 --=20 Allan Jude --qR1OjgssFm2uN0pMnAKugE67TmBlctcaV 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.22 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJT2cMJAAoJEJrBFpNRJZKfi30P/RV9ZMJc9ldXRr//EvrfPx5J Ym47pVZKDI9TbVHABr+A4Nd+MCyDnajLpM+DHrjQkEAYzNHfifzrwiarSjAmCvpL FWvLu45pUC6K5+zmV7YjivluMVw8g/7IyXl+8Y0hY/eCodp+q1uIwqjHqkr4XFYv BvBYucgsVxsxx9UEeGa+1iRP5FKZKbHP8m0yDVO9fCmNRWtVJ+5LiH/phkSJX9ZM 6VD3jHvjhqjkfAXviVDdct9/hUUKepqXQIPxWMdi4lJLPSNdg24MfgHgtTznmROY NjY3aPdHzNwvFchHO//RpfFFItrC3v0Mq6vCWjwtyfeTSuq+snfTQCzl48wMxyNJ EDLwAxCTcADial0oRfVrOaViB5uiJTMpYMD+UdDfiAMfHZxzqE8I80xJxIcHsMMd BOA7jXHyqKBlT88h8czeNsIDRkDmh5MkCJ91z/lY3ij2Zdm7HASfMmKtlijrQgjq hjpTOrNkoO6aCW3Vlj8ykIzzmsDNTLhLeNRjAJ1O34mqwCvApwmmgkL5gd0uP2yy X4ztWej5fxFDdZ4tEQ3+Ap8w2xo/uwOJ4aUeT1xEvOjmTZnjwHTB2V0JCjeE6K1i f/tWVBFbdkMfTZc+EHkQ33+JR6d+XSxmxiQQZ6JqT9/bwrnfI+QzpgHW112VX+ie dakCga0daeNIFceAHdhV =Lxb0 -----END PGP SIGNATURE----- --qR1OjgssFm2uN0pMnAKugE67TmBlctcaV-- From owner-freebsd-fs@FreeBSD.ORG Thu Jul 31 05:46:48 2014 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 26C07660; Thu, 31 Jul 2014 05:46:48 +0000 (UTC) Received: from anubis.delphij.net (anubis.delphij.net [64.62.153.212]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "anubis.delphij.net", Issuer "StartCom Class 1 Primary Intermediate Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 05BEB28D3; Thu, 31 Jul 2014 05:46:47 +0000 (UTC) Received: from delphij-macbook.local (c-24-5-244-32.hsd1.ca.comcast.net [24.5.244.32]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by anubis.delphij.net (Postfix) with ESMTPSA id CA97AA22C; Wed, 30 Jul 2014 22:46:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=delphij.net; s=anubis; t=1406785606; x=1406800006; bh=LPBrsJpjgtF+5G4xFcqjROYXHy4PKW1B32BCG8fbSlY=; h=Date:From:Reply-To:To:CC:Subject:References:In-Reply-To; b=2AKIQhmtlyST05OfefNn0ll/VdSVZzjyaMM4fZwQiYZrLSdBnLYMUMTkbr+is5/r1 ITOWtvBnYCyZEwuQ1YMJN6T5Y9HHHfSJCFtwZHnkZXIbezcqy7T6KLkhJusiiXExP8 pCm9m1wzEZPRbeTA6MqoEmczvla0jAvPfodOmuQ8= Message-ID: <53D9D845.3070905@delphij.net> Date: Wed, 30 Jul 2014 22:46:45 -0700 From: Xin Li Reply-To: d@delphij.net Organization: The FreeBSD Project MIME-Version: 1.0 To: Allan Jude , delphij@freebsd.org Subject: Re: panic: avl_find() succeeded inside avl_add() References: <53D9C306.6060105@freebsd.org> In-Reply-To: <53D9C306.6060105@freebsd.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, Andriy Gapon X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jul 2014 05:46:48 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 7/30/14 9:16 PM, Allan Jude wrote: > I updated one of our storage servers to the latest -CURRENT > yesterday and now it is panic'ing every few minutes > > I suspect this is related to r269229 (MFV r269223) > > Jul 31 03:25:23 Tango syslogd: kernel boot file is > /boot/kernel/kernel Jul 31 03:25:23 Tango kernel: panic: avl_find() > succeeded inside avl_add() Jul 31 03:25:23 Tango kernel: cpuid = 0 > Jul 31 03:25:23 Tango kernel: KDB: stack backtrace: Jul 31 03:25:23 > Tango kernel: #0 0xffffffff809ab070 at kdb_backtrace+0x60 Jul 31 > 03:25:23 Tango kernel: #1 0xffffffff8096c3a5 at panic+0x155 Jul 31 > 03:25:23 Tango kernel: #2 0xffffffff819dbc04 at avl_add+0x84 Jul 31 > 03:25:23 Tango kernel: #3 0xffffffff81a04560 at dbuf_create+0x390 > Jul 31 03:25:23 Tango kernel: #4 0xffffffff81a03f5a at > dbuf_hold_impl+0x11a Jul 31 03:25:23 Tango kernel: #5 > 0xffffffff81a0467b at dbuf_hold+0x1b Jul 31 03:25:23 Tango kernel: > #6 0xffffffff81a09593 at dmu_buf_hold_array_by_dnode+0x153 Jul 31 > 03:25:23 Tango kernel: #7 0xffffffff81a0a526 at dmu_read_uio+0x66 > Jul 31 03:25:23 Tango kernel: #8 0xffffffff81a9bb0a at > zfs_freebsd_read+0x58a Jul 31 03:25:23 Tango kernel: #9 > 0xffffffff80eddf11 at VOP_READ_APV+0xa1 Jul 31 03:25:23 Tango > kernel: #10 0xffffffff80a32427 at vn_read+0x167 Jul 31 03:25:23 > Tango kernel: #11 0xffffffff80a2e5db at vn_io_fault+0x10b Jul 31 > 03:25:23 Tango kernel: #12 0xffffffff809c4a95 at dofileread+0x95 > Jul 31 03:25:23 Tango kernel: #13 0xffffffff809c47b8 at > kern_readv+0x68 Jul 31 03:25:23 Tango kernel: #14 > 0xffffffff809c4743 at sys_read+0x63 Jul 31 03:25:23 Tango kernel: > #15 0xffffffff80db84fb at amd64_syscall+0x3fb Jul 31 03:25:23 Tango > kernel: #16 0xffffffff80d9a47b at Xfast_syscall+0xfb Jul 31 > 03:25:23 Tango kernel: Uptime: 12m11s > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192284 Can you try reverting r221991? (Andriy: in r221991 -- why reverting that portion?) Cheers, -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJT2dhFAAoJEJW2GBstM+nsLQcP/3/lgH5C7n4v8zlLFrZFuPES Ml7XwK+NGk98/oVNGL984H88ec5p2L5vNBj54dSg1ntCDF9cororBrSaThBZNbvM xjQeQOAX300jL72vkIcZuEgNTRiPfufF+SsKSLVHduySIAJDJg+bakq8JP/VMH6X s4djO6u7RZYWmmIo7knKAWzml/mQ/A4SEh03o17nmcxp9ERkxDxWXyb/dWzVbYG7 J2oJa3Ar1SptGlA3SieLos4t08Ki/UeERZAcQD77LhhgO0jfSueBediDadNVyY9n tY1d/iGRMtck27B8zft0is50DJhRmgCTO50p++HHWQrUxH0I4kbEDEXmq3NBo+Sh YPBFSOPIuas/1pCLZB3eKvXi4ocY8XT+VUeqD01rDnbbu8lQCg1XCd3sOgMNn7Is 6GbEEwXUx9erNeTRU0thMzONbA20Qxn70CkmS+45llDjjfWlqqDxAYJHSldt3QMU MKqUp1K7R97pH3WOowZ+kNrfIlqXR7FAJVYqzQlYs0vgTfrhkmhVpM0nnICtTbCg GPqazvanI9gr+Mtncz366YlJ/zXhj0JGoK345uLPQzECf718QcaOBdfOGODXDrYb zXgcFihO09UFXLloStwmF5fRmOAvfE0UOnKAaMrzQe4mUPAm9dI7VGsOFcxMSV7T HasfIf0w5TZupbP1G9+6 =8O9r -----END PGP SIGNATURE----- From owner-freebsd-fs@FreeBSD.ORG Thu Jul 31 21:20:46 2014 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4CFBC484 for ; Thu, 31 Jul 2014 21:20:46 +0000 (UTC) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [IPv6:2607:f3e0:0:1::12]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "smarthost.sentex.ca", Issuer "smarthost.sentex.ca" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0EF4D290A for ; Thu, 31 Jul 2014 21:20:45 +0000 (UTC) Received: from [IPv6:2607:f3e0:0:4:f025:8813:7603:7e4a] (saphire3.sentex.ca [IPv6:2607:f3e0:0:4:f025:8813:7603:7e4a]) by smarthost1.sentex.ca (8.14.9/8.14.9) with ESMTP id s6VLKfjO069204 for ; Thu, 31 Jul 2014 17:20:41 -0400 (EDT) (envelope-from mike@sentex.net) Message-ID: <53DAB322.1050703@sentex.net> Date: Thu, 31 Jul 2014 17:20:34 -0400 From: Mike Tancsa Organization: Sentex Communications User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: freebsd-fs@freebsd.org Subject: HAST slowness ? Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.74 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jul 2014 21:20:46 -0000 I am trying to setup my first HAST setup and for some reason, traffic sync seems to be really slow. If I do something simple like #dd if=/dev/zero of=/hastvirt/test count=2000 bs=1024k on the primary box, traffic on the secondary never gets much beyond a Mb/s ?!?! iperf and netrate show I can pretty well saturate across the link. There are no errors and the underlying NICs are both at gigabit with no other traffic. Everything seems happy, just very slow to sync. Any idea where to start debugging ? # ifstat -b -i vlan5 vlan5 Kbps in Kbps out 840.40 621.14 825.26 622.40 768.74 577.49 12772.84 1099.10 976.68 729.80 856.61 645.19 751.33 561.07 854.44 637.67 1087.46 811.47 798.61 600.51 837.40 624.65 957.50 719.61 945.90 697.86 756.10 573.92 869.78 649.61 935.69 706.42 784.65 588.13 835.90 627.21 1050.15 772.38 772.70 580.70 795.23 589.38 869.19 660.23 899.00 679.72 837.06 619.58 809.34 607.60 981.75 735.31 875.33 657.42 842.79 627.45 931.13 694.73 # ifconfig vlan5 vlan5: flags=8843 metric 0 mtu 1500 options=303 ether 00:1e:67:84:c8:ca inet 1.1.1.2 netmask 0xfffffff8 broadcast 1.1.1.7 inet6 fe80::21e:67ff:fe84:c8ca%vlan5 prefixlen 64 scopeid 0x4 nd6 options=29 media: Ethernet autoselect (1000baseT ) status: active vlan: 5 parent interface: igb0 # hastctl status Name Status Role Components disk1 complete secondary /dev/ada0p4 1.1.1.1 disk2 complete secondary /dev/ada1p4 1.1.1.1 # hastctl list disk1: role: secondary provname: disk1 localpath: /dev/ada0p4 extentsize: 2097152 (2.0MB) keepdirty: 0 remoteaddr: 1.1.1.1 replication: memsync status: complete workerpid: 888 dirty: 0 (0B) statistics: reads: 0 writes: 40529 deletes: 12 flushes: 22 activemap updates: 0 local errors: read: 0, write: 0, delete: 12, flush: 0 queues: local: 0, send: 0, recv: 0, done: 0, idle: 255 disk2: role: secondary provname: disk2 localpath: /dev/ada1p4 extentsize: 2097152 (2.0MB) keepdirty: 0 remoteaddr: 1.1.1.1 replication: memsync status: complete workerpid: 889 dirty: 0 (0B) statistics: reads: 0 writes: 40529 deletes: 12 flushes: 22 activemap updates: 0 local errors: read: 0, write: 0, delete: 12, flush: 0 queues: local: 0, send: 0, recv: 0, done: 0, idle: 255 ---Mike -- ------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ From owner-freebsd-fs@FreeBSD.ORG Fri Aug 1 18:30:11 2014 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E399366D for ; Fri, 1 Aug 2014 18:30:11 +0000 (UTC) Received: from mail-lb0-x229.google.com (mail-lb0-x229.google.com [IPv6:2a00:1450:4010:c04::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6C66E2491 for ; Fri, 1 Aug 2014 18:30:11 +0000 (UTC) Received: by mail-lb0-f169.google.com with SMTP id s7so3554868lbd.28 for ; Fri, 01 Aug 2014 11:30:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=6Y6AO7OIT34y6867btV6ukw8KlPVeBJ4MyuTwye2ZsU=; b=xlo2gR/VXXTiZHxWE/4zR0W8vnU0AGtNxVqFLORGuiSllJaAyK7mH6GlLHeX+a2mTG vRYn9oWFLhwQ8Hwp+DFFgB1HG1yw6cWEPfAjGDpLl6NiwCXS/PX7D/eyq/PHEuI5DvBI sqkRrgr9PswdlwepEijuQVKbBIlfYJgPuGtY5KSYGTYfJ6LuivDvZDwmFZ3/12Wf1F9W i4qURfSNGPw7ibghTDSBs/+C+54k2XojQPa5LRRKxLLTDO2TtJc5ic8OxusMNwM24RSZ uYJDhSr0FMAXCxaY67CptcYm5OfG1by91jU5YqKZRatyA/sA5ZrwOhXWVt/6VwjwDZQw jL7w== X-Received: by 10.152.23.197 with SMTP id o5mr8107787laf.60.1406917809257; Fri, 01 Aug 2014 11:30:09 -0700 (PDT) Received: from localhost ([91.225.202.19]) by mx.google.com with ESMTPSA id x10sm14266026lba.7.2014.08.01.11.30.07 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 01 Aug 2014 11:30:08 -0700 (PDT) Date: Fri, 1 Aug 2014 21:30:06 +0300 From: Mikolaj Golub To: Mike Tancsa Subject: Re: HAST slowness ? Message-ID: <20140801183005.GA3286@gmail.com> References: <53DAB322.1050703@sentex.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <53DAB322.1050703@sentex.net> User-Agent: Mutt/1.5.22 (2013-10-16) Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Aug 2014 18:30:12 -0000 On Thu, Jul 31, 2014 at 05:20:34PM -0400, Mike Tancsa wrote: > I am trying to setup my first HAST setup and for some reason, traffic > sync seems to be really slow. If I do something simple like > > > #dd if=/dev/zero of=/hastvirt/test count=2000 bs=1024k > > on the primary box, traffic on the secondary never gets much beyond a > Mb/s ?!?! > > iperf and netrate show I can pretty well saturate across the link. There > are no errors and the underlying NICs are both at gigabit with no other > traffic. Everything seems happy, just very slow to sync. Any idea where > to start debugging ? It looks you are writing to a file-system, not directly to HAST device? What is this FS? I see two HAST devices? Are they combined in one FS? How? What if you write directly to a HAST device instead? Also note, "hole" compression is enabled by default, so your test with copying zero blocks is not very good. You might be limited here by RTT, because in memsync mode, on every "compressed" block sent HAST waits for response before proceeding with the next block. -- Mikolaj Golub From owner-freebsd-fs@FreeBSD.ORG Fri Aug 1 19:36:05 2014 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 970A02D9 for ; Fri, 1 Aug 2014 19:36:05 +0000 (UTC) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [IPv6:2607:f3e0:0:1::12]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "smarthost.sentex.ca", Issuer "smarthost.sentex.ca" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 715E72BB6 for ; Fri, 1 Aug 2014 19:36:05 +0000 (UTC) Received: from [IPv6:2607:f3e0:0:4:f025:8813:7603:7e4a] (saphire3.sentex.ca [IPv6:2607:f3e0:0:4:f025:8813:7603:7e4a]) by smarthost1.sentex.ca (8.14.9/8.14.9) with ESMTP id s71JZwQQ015817; Fri, 1 Aug 2014 15:35:58 -0400 (EDT) (envelope-from mike@sentex.net) Message-ID: <53DBEC15.2040406@sentex.net> Date: Fri, 01 Aug 2014 15:35:49 -0400 From: Mike Tancsa Organization: Sentex Communications User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: Mikolaj Golub Subject: Re: HAST slowness ? References: <53DAB322.1050703@sentex.net> <20140801183005.GA3286@gmail.com> In-Reply-To: <20140801183005.GA3286@gmail.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.74 Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Aug 2014 19:36:05 -0000 On 8/1/2014 2:30 PM, Mikolaj Golub wrote: > On Thu, Jul 31, 2014 at 05:20:34PM -0400, Mike Tancsa wrote: >> I am trying to setup my first HAST setup and for some reason, traffic >> sync seems to be really slow. If I do something simple like >> >> >> #dd if=/dev/zero of=/hastvirt/test count=2000 bs=1024k >> >> on the primary box, traffic on the secondary never gets much beyond a >> Mb/s ?!?! >> > > It looks you are writing to a file-system, not directly to HAST > device? What is this FS? I see two HAST devices? Are they combined in > one FS? How? What if you write directly to a HAST device instead? Hi Mikolaj, Thank you for responding. I have 2 servers, both with two disks. Each have 2 zfs partitions The first zfs partition is the operating system ada0p4 and ada1p4 are for hast on each of the boxes # zpool status pool: hastvirt state: ONLINE scan: scrub repaired 0 in 0h5m with 0 errors on Thu Jul 31 17:34:49 2014 config: NAME STATE READ WRITE CKSUM hastvirt ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 hast/disk1 ONLINE 0 0 0 hast/disk2 ONLINE 0 0 0 The idea if one box dies, the other can take over and mount hastvirt > > Also note, "hole" compression is enabled by default, so your test with > copying zero blocks is not very good. You might be limited here by > RTT, because in memsync mode, on every "compressed" block sent HAST > waits for response before proceeding with the next block. Perhaps this indeed was the issue. I tried importing a windows VM and it seemed to go much faster. I am now seeing traffic across the HAST dedicated NIC at close to 200Mb % ifstat -b -i vlan5 vlan5 Kbps in Kbps out 262365.4 6407.79 235609.5 5757.97 217813.4 5380.81 144054.8 3606.39 150899.8 3882.17 240806.7 5908.37 238943.7 5718.61 Looking at gstat on the master, it currently has maxed out the disk writing so I guess the network is keeping up. # hastctl status Name Status Role Components disk1 complete primary /dev/ada0p4 1.1.1.1 disk2 complete primary /dev/ada1p4 1.1.1.1 hastctl list disk1: role: primary provname: disk1 localpath: /dev/ada0p4 extentsize: 2097152 (2.0MB) keepdirty: 64 remoteaddr: 1.1.1.1 replication: memsync status: complete workerpid: 1021 dirty: 4194304 (4.0MB) statistics: reads: 387530 writes: 309272 deletes: 11 flushes: 480 activemap updates: 19121 local errors: read: 0, write: 0, delete: 11, flush: 0 queues: local: 0, send: 0, recv: 0, done: 0, idle: 255 disk2: role: primary provname: disk2 localpath: /dev/ada1p4 extentsize: 2097152 (2.0MB) keepdirty: 64 remoteaddr: 1.1.1.1 replication: memsync status: complete workerpid: 1023 dirty: 4194304 (4.0MB) statistics: reads: 387008 writes: 309251 deletes: 11 flushes: 480 activemap updates: 19118 local errors: read: 0, write: 0, delete: 11, flush: 0 queues: local: 0, send: 0, recv: 0, done: 0, idle: 255 Are there any good hast tuning guides beyond the wiki you recommend ? Should anything be tuned beyond the defaults ? Thanks again ---Mike -- ------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ From owner-freebsd-fs@FreeBSD.ORG Sat Aug 2 08:01:52 2014 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6254F156 for ; Sat, 2 Aug 2014 08:01:52 +0000 (UTC) Received: from mail-la0-x236.google.com (mail-la0-x236.google.com [IPv6:2a00:1450:4010:c03::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E07C42FA8 for ; Sat, 2 Aug 2014 08:01:51 +0000 (UTC) Received: by mail-la0-f54.google.com with SMTP id hz20so3955735lab.27 for ; Sat, 02 Aug 2014 01:01:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=JI3/rYabd0eeitrIYlO7Q7MJ1BR0CN4IQI4PV6Ct5+A=; b=B4exuJlUsBw4jyMDllMEgv4kGI8mibNX8Y9R8fjOivr6n3veiLkFewN7cYjEMwFjfc SWgqAqZVh59IxH6z3eTDWqv8HWZXw42NioyXDFZATZMOpu+8XS3hkcPxGACMGLwzg6kg wyCRiPD3uOaIryC91lb7H8cXQ/JUpJUwDAUgY3VUkmvOp1uTQIpkq8amthMWcP/2As96 1UxAQnHG9ordLjKYKaw0eLVbo9PVhEIZDG/qB2J1KCAk3sLeKIrqY1r81xXHaHOydLPv pFGxGa0YN4ahi/68kzWmdMCT8yY4MIZw/rR2+v+QCHtzgu1ruNA0nikyj8r0p41T1G/x RQww== X-Received: by 10.152.19.1 with SMTP id a1mr1628516lae.64.1406966508944; Sat, 02 Aug 2014 01:01:48 -0700 (PDT) Received: from localhost ([91.225.200.106]) by mx.google.com with ESMTPSA id n1sm17021215lbs.0.2014.08.02.01.01.47 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 02 Aug 2014 01:01:48 -0700 (PDT) Date: Sat, 2 Aug 2014 08:01:46 +0000 From: Mikolaj Golub To: Mike Tancsa Subject: Re: HAST slowness ? Message-ID: <20140802080144.GA2123@gmail.com> References: <53DAB322.1050703@sentex.net> <20140801183005.GA3286@gmail.com> <53DBEC15.2040406@sentex.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <53DBEC15.2040406@sentex.net> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Aug 2014 08:01:52 -0000 On Fri, Aug 01, 2014 at 03:35:49PM -0400, Mike Tancsa wrote: > Are there any good hast tuning guides beyond the wiki you recommend ? I am not aware of any. > Should anything be tuned beyond the defaults ? I suppose the defaults are good for most of the cases, still you might consider experimenting with replication and compression modes. And as usual, before tuning you have to identify the bottleneck. -- Mikolaj Golub