From owner-freebsd-stable@FreeBSD.ORG Sun Nov 30 00:08:04 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1659EE08 for ; Sun, 30 Nov 2014 00:08:04 +0000 (UTC) Received: from mail-pa0-x235.google.com (mail-pa0-x235.google.com [IPv6:2607:f8b0:400e:c03::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 D6BB58AF for ; Sun, 30 Nov 2014 00:08:03 +0000 (UTC) Received: by mail-pa0-f53.google.com with SMTP id kq14so8625640pab.26 for ; Sat, 29 Nov 2014 16:08:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; bh=ivgbufDIoRy7XJL9egGIUJyNt5RRQeDU/1/3i3GykXM=; b=GGNWpQUAoc5S3BjJsnVV07c/4rGlqxldCLsenXcHFjokd7Bt5nWIV/tOVuy1Xr1RCO /sDm/wykZKCBzTb48UwLnVTgsDZArnrkTeM5sQzMLFaSBQIYUp745e+hZTzPvT60KHzJ IlqJaPCkPKSKDHcajy1Dl03lnRklg1nDmrigfBPGAqr1JVHH5flkIz3lRjfAHdLuLpOl 6b5WAGz5tFNB5dw5mm4hpD4LCoZJ2c0b8+8y/2l5VqrQLw7jyPoFVQXRvybVaH3QlNnJ GA37yMPa8W6huSL+cocrbqGx8VGbwUMgkt9KvJZB3QOVCAr0OgssFTfGGf8ZQXY63CnD IWvw== X-Received: by 10.70.100.199 with SMTP id fa7mr86891668pdb.114.1417306083501; Sat, 29 Nov 2014 16:08:03 -0800 (PST) Received: from splash.akips.com (CPE-120-146-191-2.static.qld.bigpond.net.au. [120.146.191.2]) by mx.google.com with ESMTPSA id w4sm2863356pdq.28.2014.11.29.16.08.01 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 29 Nov 2014 16:08:02 -0800 (PST) Date: Sun, 30 Nov 2014 10:07:20 +1000 From: Paul Koch To: freebsd-stable@freebsd.org Subject: Re: 10.1 mmap on zfs not updating mtime Message-ID: <20141130100720.5b0bead7@splash.akips.com> In-Reply-To: <20141125142302.1199041c@akips.com> References: <20141125142302.1199041c@akips.com> X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.22; amd64-portbld-freebsd10.1) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Nov 2014 00:08:04 -0000 Can probably ignore this. We changed our application so it always calls futimes() on the file descriptor after a fsync() or munmap(). Paul. On Tue, 25 Nov 2014 14:23:02 +1000 Paul Koch wrote: > > Hi, > > we have observed some odd behaviour with the mtime of a mmap'ed file > when it has been updated on a zfs pool. The mtime does not appear to > be updated. Seems to work ok on UFS. > > Test program below... > > On 10.0, the following works ok: > > dd bs=1k if=/dev/zero of=mdata count=1 > ls -lT mdata; /tmp/mmap-mtime mdata; ls -lT mdata > > but on 10.1 the mtime stays at its creation time. > > > > #include > #include > #include > > #include > #include > #include > #include > #include > #include > > > int > main (int argc, char **argv) > { > int fd, > i; > char *data, > *filename; > struct stat s; > > if (argc != 2) > exit (1); > > filename =argv[1]; > > if (stat (filename, &s) != 0) { > fprintf (stderr, "stat: %s\n", strerror (errno)); > exit (1); > } > else if ((fd = open (filename, O_RDWR, 0644)) == -1) { > fprintf (stderr, "open: %s\n", strerror (errno)); > exit (1); > } > else if ((data = mmap (NULL, (size_t) s.st_size, > PROT_READ | PROT_WRITE, > MAP_SHARED, > fd, (off_t) 0)) == MAP_FAILED) { > fprintf (stderr, "mmap: %s\n", strerror (errno)); > exit (1); > } > > for (i = 0; i < s.st_size; i++) { > data[i] = 1; > } > > munmap (data, s.st_size); > close (fd); > > exit (0); > } > > Paul. From owner-freebsd-stable@FreeBSD.ORG Sun Nov 30 00:10:17 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D42CB14E for ; Sun, 30 Nov 2014 00:10:17 +0000 (UTC) Received: from avasout06.plus.net (avasout06.plus.net [212.159.14.18]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "Bizanga Labs SMTP Client Certificate", Issuer "Bizanga Labs CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6D2E2945 for ; Sun, 30 Nov 2014 00:10:16 +0000 (UTC) Received: from [192.168.1.17] ([80.229.236.194]) by avasout06 with smtp id Mc721p0034CLJ5401c73Ly; Sun, 30 Nov 2014 00:07:03 +0000 X-CM-Score: 0.00 X-CNFS-Analysis: v=2.1 cv=CN+kXHbD c=1 sm=1 tr=0 a=G4bc5lkgapKKm1P+Twxy3Q==:117 a=G4bc5lkgapKKm1P+Twxy3Q==:17 a=0Bzu9jTXAAAA:8 a=rkJuIV0pGx0A:10 a=IkcTkHD0fZMA:10 a=80hmnl3cAAAA:8 a=58fkQW-ix62NEQ5N9qQA:9 a=QEXdDO2ut3YA:10 Message-ID: <547A5F4C.6090901@bubblegen.co.uk> Date: Sun, 30 Nov 2014 00:05:32 +0000 From: Matt User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: freebsd-stable@FreeBSD.org Subject: ssmtp and message ID Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Nov 2014 00:10:17 -0000 Hi all, I'm using ssmtp instead of sendmail as the mailer on my FreeBSD 10.1-RELEASE box. The SMTP relay I point it to is my Synology NAS running the mail server application. What I've noticed is that all mails sent by ssmtp appear as having no Message ID in the log on the Synology. I use the Synology with several other email clients, eg android phone, ipad, kmail, alpine, thunderbird and all of them show a valid Message ID. Do you have any idea why the Message ID isn't shown for emails sent by ssmtp? Thanks for any suggestions. -- Matt From owner-freebsd-stable@FreeBSD.ORG Sun Nov 30 11:20:42 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 06DC37AD for ; Sun, 30 Nov 2014 11:20:42 +0000 (UTC) Received: from kaija.ugh.net.au (kaija.ugh.net.au [IPv6:2a00:1a48:7803:107:65bc:4bde:ff08:1f7f]) by mx1.freebsd.org (Postfix) with ESMTP id C4FA27FA for ; Sun, 30 Nov 2014 11:20:41 +0000 (UTC) Received: from [IPv6:2a00:c1a0:c100:2700:4d93:6273:b61f:7197] (unknown [IPv6:2a00:c1a0:c100:2700:4d93:6273:b61f:7197]) by kaija.ugh.net.au (Postfix) with ESMTPSA id 26C1787E5 for ; Sun, 30 Nov 2014 11:20:32 +0000 (UTC) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: build world failing From: Andrew Stevenson In-Reply-To: Date: Sun, 30 Nov 2014 12:20:25 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <7E853878-E82A-41D1-9BD6-494122F9FCAD@ugh.net.au> References: <2C0C65F2-558B-4759-BE6C-BB4668C0E681@ugh.net.au> <0120C440-95F1-4183-9AD4-2CA1B35E713A@ugh.net.au> <4D71855F-1F3E-4AED-A214-8D7F431E373E@FreeBSD.org> <5D131B1C-A13A-45F0-97A4-976FDEE8B59A@ugh.net.au> To: freebsd-stable@freebsd.org X-Mailer: Apple Mail (2.1878.6) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Nov 2014 11:20:42 -0000 On 20 Nov 2014, at 11:23, Andrew Stevenson wrote: > build world finished successfully when building with -O0. Of course = now I have an entire unoptimised world=85 >=20 > I will (once the kernel is done) try running this and use it as a base = for an attempt with -O1. And miraculously everything worked. I successfully build world with = CFLAGS=3D-O2 -pipe. I guess there must have been a bug in clang that = only happened with an optimisation enabled at -O2 that was later fixed Thanks for everyone=92s help, Andrew= From owner-freebsd-stable@FreeBSD.ORG Mon Dec 1 00:38:01 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 97E856D8; Mon, 1 Dec 2014 00:38:01 +0000 (UTC) Received: from mail-lb0-x22a.google.com (mail-lb0-x22a.google.com [IPv6:2a00:1450:4010:c04::22a]) (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 35903A10; Mon, 1 Dec 2014 00:38:01 +0000 (UTC) Received: by mail-lb0-f170.google.com with SMTP id w7so7887007lbi.1 for ; Sun, 30 Nov 2014 16:37:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:cc:content-type; bh=cJXw7C4IQskmrfrRcRQ89dDV01ejVjMz4SrpPesE9/Q=; b=FtHDKHeKzUUwbJpuMYs9DDDDs2A/tID0H3ccdXmpw1mBabLKmY/zmlMOYQqaBwx+Ah 893ii7j9kYaOW8EDSRscAPPOe3OnDBABaQMR732U3ehqkKiX6dtuUL2He9GWHIetTc6E 2yiI5UpOaOQnkKKDgVuSoyJdhKjhoCk2mrMs1RL9Xgvlt5lL+zfm6fNmSTWLa/YPCNPO dQ0oRNz3yLetoU0rgdv5QoRVpxPOnB03QqWYmz5fFbnPtRP/tN33bdyl0KJx7dMvHS8d eRUZnwjCN/pdW5JqCGwWlHSfb1DmxgyINBpxqxuS/y0k3E5CH/2dB1Zdgy6RVIZvy/iJ IOPw== MIME-Version: 1.0 X-Received: by 10.112.137.39 with SMTP id qf7mr53893311lbb.47.1417394279298; Sun, 30 Nov 2014 16:37:59 -0800 (PST) Sender: crodr001@gmail.com Received: by 10.112.130.168 with HTTP; Sun, 30 Nov 2014 16:37:59 -0800 (PST) Date: Sun, 30 Nov 2014 16:37:59 -0800 X-Google-Sender-Auth: Oos_yiOWCHwmK1KjyQKeH01vqFM Message-ID: Subject: Call for Help: Setting up Saltstack for devops of jenkins.freebsd.org cluster From: Craig Rodrigues To: freebsd-current Current Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: FreeBSD stable , ports , freebsd-python@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Dec 2014 00:38:01 -0000 FYI, https://lists.freebsd.org/pipermail/freebsd-testing/2014-December/000693.html Please send follow-ups to freebsd-testing@FreeBSD.org . Thanks. -- Craig -- Craig From owner-freebsd-stable@FreeBSD.ORG Mon Dec 1 08:11:17 2014 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D0DA81AC for ; Mon, 1 Dec 2014 08:11:17 +0000 (UTC) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 2D7C91B7 for ; Mon, 1 Dec 2014 08:11:16 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id KAA19338; Mon, 01 Dec 2014 10:13:01 +0200 (EET) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1XvM4Z-000MSn-Ji; Mon, 01 Dec 2014 10:11:07 +0200 Message-ID: <547C2263.3000001@FreeBSD.org> Date: Mon, 01 Dec 2014 10:10:11 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Paul Koch , freebsd-stable@FreeBSD.org Subject: Re: 10.1 mmap on zfs not updating mtime References: <20141125142302.1199041c@akips.com> In-Reply-To: <20141125142302.1199041c@akips.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Dec 2014 08:11:17 -0000 On 25/11/2014 06:23, Paul Koch wrote: > > Hi, > > we have observed some odd behaviour with the mtime of a mmap'ed file > when it has been updated on a zfs pool. The mtime does not appear to > be updated. Seems to work ok on UFS. Could you please test the following simple patch? Index: sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c =================================================================== --- sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c (revision 275036) +++ sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c (working copy) @@ -5969,6 +5969,7 @@ top: &zp->z_pflags, 8); zfs_tstamp_update_setup(zp, CONTENT_MODIFIED, mtime, ctime, B_TRUE); + (void)sa_bulk_update(zp->z_sa_hdl, bulk, count, tx); zfs_log_write(zfsvfs->z_log, tx, TX_WRITE, zp, off, len, 0); zfs_vmobject_wlock(object); > Test program below... > > On 10.0, the following works ok: > > dd bs=1k if=/dev/zero of=mdata count=1 > ls -lT mdata; /tmp/mmap-mtime mdata; ls -lT mdata > > but on 10.1 the mtime stays at its creation time. [snip] -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Tue Dec 2 01:27:58 2014 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CDB08B05; Tue, 2 Dec 2014 01:27:58 +0000 (UTC) Received: from mail.akips.com (mail.akips.com [65.19.130.19]) by mx1.freebsd.org (Postfix) with ESMTP id BA9BD814; Tue, 2 Dec 2014 01:27:58 +0000 (UTC) Received: from akips.com (CPE-120-146-191-2.static.qld.bigpond.net.au [120.146.191.2]) by mail.akips.com (Postfix) with ESMTPSA id E4D0728441; Tue, 2 Dec 2014 11:27:50 +1000 (EST) Date: Tue, 2 Dec 2014 11:27:07 +1000 From: Paul Koch To: Andriy Gapon Subject: Re: 10.1 mmap on zfs not updating mtime Message-ID: <20141202112707.5ee84c5a@akips.com> In-Reply-To: <547C2263.3000001@FreeBSD.org> References: <20141125142302.1199041c@akips.com> <547C2263.3000001@FreeBSD.org> Organization: AKIPS X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.22; amd64-portbld-freebsd10.1) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=5.0 tests=UNPARSEABLE_RELAY, URIBL_BLOCKED autolearn=disabled version=3.4.0 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on host1.akips.com Cc: freebsd-stable@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Dec 2014 01:27:58 -0000 On Mon, 01 Dec 2014 10:10:11 +0200 Andriy Gapon wrote: > On 25/11/2014 06:23, Paul Koch wrote: > > > > Hi, > > > > we have observed some odd behaviour with the mtime of a mmap'ed file > > when it has been updated on a zfs pool. The mtime does not appear to > > be updated. Seems to work ok on UFS. > > Could you please test the following simple patch? > Index: sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c > =================================================================== > --- sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c (revision 275036) > +++ sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c (working copy) > @@ -5969,6 +5969,7 @@ top: > &zp->z_pflags, 8); > zfs_tstamp_update_setup(zp, CONTENT_MODIFIED, mtime, ctime, > B_TRUE); > + (void)sa_bulk_update(zp->z_sa_hdl, bulk, count, tx); > zfs_log_write(zfsvfs->z_log, tx, TX_WRITE, zp, off, len, 0); > > zfs_vmobject_wlock(object); > > > Test program below... > > > > On 10.0, the following works ok: > > > > dd bs=1k if=/dev/zero of=mdata count=1 > > ls -lT mdata; /tmp/mmap-mtime mdata; ls -lT mdata > > > > but on 10.1 the mtime stays at its creation time. > [snip] > Applied the same change to 10.1-RELEASE and it fixed the problem. Don't know how this affects other applications running on 10.1, but we've applied a workaround for ours by calling futimes() after we do a fsync() or between munmap()/close() on a mmap'ed file. Paul. -- Paul Koch | Founder, CEO AKIPS Network Monitor http://www.akips.com Brisbane, Australia From owner-freebsd-stable@FreeBSD.ORG Tue Dec 2 06:18:55 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6836DB3B for ; Tue, 2 Dec 2014 06:18:55 +0000 (UTC) Received: from mamba.tntpowerhost.com (mamba.tntpowerhost.com [208.100.19.247]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3E9B27CF for ; Tue, 2 Dec 2014 06:18:55 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=kane.mn; s=default; h=Message-ID:Subject:To:From:Date:Content-Transfer-Encoding:Content-Type:MIME-Version; bh=ymS+xJk2+tjd4R8meCSGF+Ky4DFzj5vlBQamI1IfH/8=; b=e6Z2P4TrKoPPD5VgNa7lmSAFLeYVKjqbFvM8J70i3/30/YLmhByDSiYklAOrugBytBHR+8MYwhQ/Vp23JmAD8wXoBTmkQBH0Bp7Ki420UDixyWUUxePHQRhXS4y7VeTP0PmV91el/IbJGJoF/g7rC8Lv08Ky/BFAPo+90/EtiPs=; Received: from localhost ([::1]:52740 helo=mamba.tntpowerhost.com) by mamba.tntpowerhost.com with esmtpa (Exim 4.84) (envelope-from ) id 1XvgnW-0005Yb-Fa for freebsd-stable@freebsd.org; Tue, 02 Dec 2014 00:18:54 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 02 Dec 2014 00:18:54 -0600 From: Mark Kane To: freebsd-stable@freebsd.org Subject: ZFS available space difference between 10.0 and 10.1 Message-ID: X-Sender: mark@kane.mn User-Agent: Roundcube Webmail/1.0.1 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - mamba.tntpowerhost.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - kane.mn X-Get-Message-Sender-Via: mamba.tntpowerhost.com: authenticated_id: mark@mkproductions.org X-Source: X-Source-Args: X-Source-Dir: X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Dec 2014 06:18:55 -0000 Hi all, I updated a machine running 10.0-STABLE from April to 10.1-RELEASE and am noticing a discrepancy in available space on a ZFS filesystem between versions. Initially upon booting 10.1-RELEASE this filesystem was reporting 0B avail and was unusable, though it was operating normally in 10.0-STABLE. I was able to clear enough space by booting back into 10.0 and removing files, but attempts to truncate files in 10.1-REL did not actually reclaim space on the filesystem. Example from 10.1: % zpool list NAME SIZE ALLOC FREE FRAG EXPANDSZ CAP DEDUP HEALTH ALTROOT seagate2tb 1.81T 1.76T 55.5G - - 97% 1.00x ONLINE - tank - - - - - - - FAULTED - % zfs list NAME USED AVAIL REFER MOUNTPOINT seagate2tb 1.76T 0 1.76T /seagate2tb % ls -lh /seagate2tb/isos/FreeBSD-8.1-RELEASE-i386-disc1.iso -rw-r--r-- 1 mixx941 wheel 645M Jul 18 2010 /seagate2tb/isos/FreeBSD-8.1-RELEASE-i386-disc1.iso % rm /seagate2tb/isos/FreeBSD-8.1-RELEASE-i386-disc1.iso rm: /seagate2tb/isos/FreeBSD-8.1-RELEASE-i386-disc1.iso: No space left on device % echo "" > /seagate2tb/isos/FreeBSD-8.1-RELEASE-i386-disc1.iso % ls -lh /seagate2tb/isos/FreeBSD-8.1-RELEASE-i386-disc1.iso -rw-r--r-- 1 mixx941 wheel 1B Nov 27 19:38 /seagate2tb/isos/FreeBSD-8.1-RELEASE-i386-disc1.iso Free pool space increased as expected: % zpool list seagate2tb NAME SIZE ALLOC FREE FRAG EXPANDSZ CAP DEDUP HEALTH ALTROOT seagate2tb 1.81T 1.76T 56.1G - - 96% 1.00x ONLINE - ...but not the filesystem: % zfs list NAME USED AVAIL REFER MOUNTPOINT seagate2tb 1.76T 0 1.76T /seagate2tb ---------------------------------------------------------------------------- Once enough space was cleared to restore normal operation, I did a quick test to compare the available space in both versions with no changes to the filesystem between booting the 10.0 and 10.1 kernels. 10.0-STABLE reports over 30GB available while 10.1 reports only 2.25GB avail: % uname -a FreeBSD amd645200.localhost 10.0-STABLE FreeBSD 10.0-STABLE #0: Sun Apr 27 18:55:28 CDT 2014 mixx941@amd645200.localhost:/usr/obj/usr/src/sys/AMD645200 amd64 % zpool list NAME SIZE ALLOC FREE FRAG EXPANDSZ CAP DEDUP HEALTH ALTROOT seagate2tb 1.81T 1.75T 60.3G 0% - 96% 1.00x ONLINE - tank - - - - - - - FAULTED - % zfs list NAME USED AVAIL REFER MOUNTPOINT seagate2tb 1.75T 31.3G 1.75T /seagate2tb ----- % uname -a FreeBSD amd645200.localhost 10.1-RELEASE FreeBSD 10.1-RELEASE #0: Mon Nov 24 11:15:59 CST 2014 mixx941@amd645200.localhost:/usr/obj/usr/src/sys/GENERIC amd64 % zpool list NAME SIZE ALLOC FREE FRAG EXPANDSZ CAP DEDUP HEALTH ALTROOT seagate2tb 1.81T 1.75T 60.3G - - 96% 1.00x ONLINE - tank - - - - - - - FAULTED - % zfs list NAME USED AVAIL REFER MOUNTPOINT seagate2tb 1.75T 2.25G 1.75T /seagate2tb ---------------------------------------------------------------------------- Has anyone seen any similar issues in 10.1, or any ideas what could cause the discrepancy between versions? I'm happy to provide any further info/testing if needed. Thanks in advance, -Mark From owner-freebsd-stable@FreeBSD.ORG Tue Dec 2 07:19:34 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 25CA862B for ; Tue, 2 Dec 2014 07:19:34 +0000 (UTC) Received: from mail-oi0-x233.google.com (mail-oi0-x233.google.com [IPv6:2607:f8b0:4003:c06::233]) (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 E507AD0D for ; Tue, 2 Dec 2014 07:19:33 +0000 (UTC) Received: by mail-oi0-f51.google.com with SMTP id e131so8724326oig.24 for ; Mon, 01 Dec 2014 23:19:33 -0800 (PST) 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; bh=YADbRLCV5i+Y6PZgLSkeeRjHjBhuyzQiq+MENXMa8ME=; b=vUosPa5zi5M0sQQGLe+AdcTFjVmMJRFo6hTOBo0P2s+O/hYsJWbRI7F4gynKVBS1tG IH34yjDPgOyGJ4XUHsA5CVBljqE3lJnzMUgA8iuER5hEt157brg9jSH/vDgI0blAFq37 /zwy4EaBTrTGVoi6I96Ln8UJLF9ViioaHrWta/Nxs9szETHC165aeyRhmD5RTa9WPWfd kIt3/d2S8AeTgm5pvAUoWsNfvVOq0chd0tlmFn+UbcIn6+bQaPcjkMMWnFbTbgr9/CRf ZRiKMrXtJ/0UEFJ6oIOCSaEYcFY1sKR/ZaVS4TUzbdaJOuFZWPtK3x/ad45JkQyg70zI 47Mg== MIME-Version: 1.0 X-Received: by 10.60.139.66 with SMTP id qw2mr10492330oeb.11.1417504773196; Mon, 01 Dec 2014 23:19:33 -0800 (PST) Received: by 10.202.6.21 with HTTP; Mon, 1 Dec 2014 23:19:33 -0800 (PST) Received: by 10.202.6.21 with HTTP; Mon, 1 Dec 2014 23:19:33 -0800 (PST) In-Reply-To: References: Date: Mon, 1 Dec 2014 23:19:33 -0800 Message-ID: Subject: Re: ZFS available space difference between 10.0 and 10.1 From: Freddie Cash To: Mark Kane Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: FreeBSD Stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Dec 2014 07:19:34 -0000 On Dec 1, 2014 10:19 PM, "Mark Kane" wrote: > > Hi all, > > I updated a machine running 10.0-STABLE from April to 10.1-RELEASE and am noticing a discrepancy in available space on a ZFS filesystem between versions. [snip] > Has anyone seen any similar issues in 10.1, or any ideas what could cause the discrepancy between versions? I'm happy to provide any further info/testing if needed. IIUC, ZFS now reserves 3% of pool space for administrative purposes (namely to be able to delete things when "pool is full"). So a pool imported on 10.0 will show more available space than a pool imported on 10.1. Cheers, Freddie From owner-freebsd-stable@FreeBSD.ORG Tue Dec 2 12:16:09 2014 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6C60A285 for ; Tue, 2 Dec 2014 12:16:09 +0000 (UTC) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id BE334F99 for ; Tue, 2 Dec 2014 12:16:08 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id OAA16240; Tue, 02 Dec 2014 14:17:55 +0200 (EET) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1XvmN6-000O33-IZ; Tue, 02 Dec 2014 14:16:00 +0200 Message-ID: <547DAD48.2010407@FreeBSD.org> Date: Tue, 02 Dec 2014 14:15:04 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Paul Koch Subject: Re: 10.1 mmap on zfs not updating mtime References: <20141125142302.1199041c@akips.com> <547C2263.3000001@FreeBSD.org> <20141202112707.5ee84c5a@akips.com> In-Reply-To: <20141202112707.5ee84c5a@akips.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Dec 2014 12:16:09 -0000 On 02/12/2014 03:27, Paul Koch wrote: > On Mon, 01 Dec 2014 10:10:11 +0200 > Andriy Gapon wrote: > >> On 25/11/2014 06:23, Paul Koch wrote: >>> >>> Hi, >>> >>> we have observed some odd behaviour with the mtime of a mmap'ed file >>> when it has been updated on a zfs pool. The mtime does not appear to >>> be updated. Seems to work ok on UFS. >> >> Could you please test the following simple patch? >> Index: sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c >> =================================================================== >> --- sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c (revision 275036) >> +++ sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c (working copy) >> @@ -5969,6 +5969,7 @@ top: >> &zp->z_pflags, 8); >> zfs_tstamp_update_setup(zp, CONTENT_MODIFIED, mtime, ctime, >> B_TRUE); >> + (void)sa_bulk_update(zp->z_sa_hdl, bulk, count, tx); >> zfs_log_write(zfsvfs->z_log, tx, TX_WRITE, zp, off, len, 0); >> >> zfs_vmobject_wlock(object); >> >>> Test program below... >>> >>> On 10.0, the following works ok: >>> >>> dd bs=1k if=/dev/zero of=mdata count=1 >>> ls -lT mdata; /tmp/mmap-mtime mdata; ls -lT mdata >>> >>> but on 10.1 the mtime stays at its creation time. >> [snip] >> > > Applied the same change to 10.1-RELEASE and it fixed the problem. Thank you for reporting the problem and testing the patch! > Don't know how this affects other applications running on 10.1, but we've > applied a workaround for ours by calling futimes() after we do a fsync() > or between munmap()/close() on a mmap'ed file. -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Tue Dec 2 14:09:39 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 618009DE for ; Tue, 2 Dec 2014 14:09:39 +0000 (UTC) Received: from mail.nospam.fr.eu.org (saloon.dalton-brothers.org [IPv6:2001:bc8:3ac3::beef:1]) by mx1.freebsd.org (Postfix) with ESMTP id 2A400D85 for ; Tue, 2 Dec 2014 14:09:39 +0000 (UTC) Received: from mail.dupille.org (localhost [IPv6:::1]) by mail.nospam.fr.eu.org (Postfix) with ESMTP id 917031907 for ; Tue, 2 Dec 2014 15:09:30 +0100 (CET) Authentication-Results: mail.nospam.fr.eu.org; dkim=none reason="no signature"; dkim-adsp=fail (unprotected policy) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 02 Dec 2014 15:09:30 +0100 From: =?UTF-8?Q?St=C3=A9phane_Dupille?= To: freebsd-stable@freebsd.org Subject: Zpool is segfaulting Organization: Maison Message-ID: X-Sender: stephane@dupille.org User-Agent: Roundcube Webmail/1.0.3 X-Spam-Status: No, score=0.9 required=5.0 tests=AWL, BAYES_40, UNPARSEABLE_RELAY shortcircuit=no autolearn=ham autolearn_force=no version=3.4.0 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on spamd X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Dec 2014 14:09:39 -0000 Hello ! I've juste upgraded my server from 10.0-RELEASE to 10.1-RELEASE. Everything went well, exception in my daily periodic report, I've found that the command "zpool list" is behaving strangely : # zpool list bad property list: invalid property 'fragmentation' usage: list [-Hpv] [-o property[,...]] [-T d|u] [pool] ... [interval [count]] the following properties are supported: PROPERTY EDIT VALUES allocated NO capacity NO dedupratio NO <1.00x or higher if deduped> expandsize NO free NO freeing NO guid NO health NO size NO altroot YES autoexpand YES on | off autoreplace YES on | off bootfs YES cachefile YES | none comment YES dedupditto YES delegation YES on | off failmode YES wait | continue | panic listsnapshots YES on | off readonly YES on | off version YES feature@... YES disabled | enabled | active The feature@ properties must be appended with a feature name. See zpool-features(7). On a freshly installed 10.1-RELEASE it behaves correctly. But what is frightening me the most is that : # zpool upgrade This system supports ZFS pool feature flags. All pools are formatted using feature flags. Some supported features are not enabled on the following pools. Once a feature is enabled the pool may become incompatible with software that does not support the feature. See zpool-features(7) for details. POOL FEATURE --------------- zboot com.delphix:async_destroy zsh: segmentation fault (core dumped) zpool upgrade Again, it works perfeclty well on a freshly installed 10.1-RELEASE. So, on my server, I installed a mirror zfs on top of a GELI layer. I don't know if it's of any importance. I don't know where to look to fix this issue (if there's an issue, the system is behaving perfectly well). Best regards, SD From owner-freebsd-stable@FreeBSD.ORG Tue Dec 2 14:27:39 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D42CEF10 for ; Tue, 2 Dec 2014 14:27:39 +0000 (UTC) Received: from smtprelay04.ispgateway.de (smtprelay04.ispgateway.de [80.67.18.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9641AF6D for ; Tue, 2 Dec 2014 14:27:39 +0000 (UTC) Received: from [78.35.176.15] (helo=fabiankeil.de) by smtprelay04.ispgateway.de with esmtpsa (TLSv1.2:AES128-GCM-SHA256:128) (Exim 4.84) (envelope-from ) id 1XvoQL-0006CP-80 for freebsd-stable@freebsd.org; Tue, 02 Dec 2014 15:27:29 +0100 Date: Tue, 2 Dec 2014 15:27:28 +0100 From: Fabian Keil To: Subject: Re: Zpool is segfaulting Message-ID: <6ce2be85.1a4a8742@fabiankeil.de> In-Reply-To: References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; boundary="Sig_/x3dkSl6vgnZ18bYiPRNykMh"; protocol="application/pgp-signature" X-Df-Sender: Nzc1MDY3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Dec 2014 14:27:39 -0000 --Sig_/x3dkSl6vgnZ18bYiPRNykMh Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable St=C3=A9phane Dupille via freebsd-stable wrote: > I've juste upgraded my server from 10.0-RELEASE to 10.1-RELEASE.=20 > Everything went well, exception in my daily periodic report, I've found=20 > that the command "zpool list" is behaving strangely : > # zpool list > bad property list: invalid property 'fragmentation' Are you sure kernel and userland are in sync? > But what is frightening me the most is that : > # zpool upgrade > This system supports ZFS pool feature flags. >=20 > All pools are formatted using feature flags. >=20 >=20 > Some supported features are not enabled on the following pools. Once a > feature is enabled the pool may become incompatible with software > that does not support the feature. See zpool-features(7) for details. >=20 > POOL FEATURE > --------------- > zboot > com.delphix:async_destroy > zsh: segmentation fault (core dumped) zpool upgrade >=20 >=20 > Again, it works perfeclty well on a freshly installed 10.1-RELEASE. >=20 > So, on my server, I installed a mirror zfs on top of a GELI layer. I=20 > don't know if it's of any importance. This could be related to: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D182248 Fabian --Sig_/x3dkSl6vgnZ18bYiPRNykMh Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlR9zFAACgkQBYqIVf93VJ07PgCdGeUVw0GMOmzlzUOH/0f1w7wU QEQAnA1ZObbr/8JgDMDARvjhDkXuCHLC =qXB9 -----END PGP SIGNATURE----- --Sig_/x3dkSl6vgnZ18bYiPRNykMh-- From owner-freebsd-stable@FreeBSD.ORG Tue Dec 2 14:41:34 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C8575243 for ; Tue, 2 Dec 2014 14:41:34 +0000 (UTC) Received: from mail.nospam.fr.eu.org (saloon.dalton-brothers.org [IPv6:2001:bc8:3ac3::beef:1]) by mx1.freebsd.org (Postfix) with ESMTP id 8F8AC186 for ; Tue, 2 Dec 2014 14:41:34 +0000 (UTC) Received: from mail.dupille.org (localhost [IPv6:::1]) by mail.nospam.fr.eu.org (Postfix) with ESMTP id 74E64190A for ; Tue, 2 Dec 2014 15:41:26 +0100 (CET) Authentication-Results: mail.nospam.fr.eu.org; dkim=none reason="no signature"; dkim-adsp=fail (unprotected policy) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Tue, 02 Dec 2014 15:41:26 +0100 From: =?UTF-8?Q?St=C3=A9phane_Dupille?= To: freebsd-stable@freebsd.org Subject: Re: Zpool is segfaulting Organization: Maison In-Reply-To: <6ce2be85.1a4a8742@fabiankeil.de> References: <6ce2be85.1a4a8742@fabiankeil.de> Message-ID: <9e518a24d422a344429af043b6344c3c@dupille.org> X-Sender: stephane@dupille.org User-Agent: Roundcube Webmail/1.0.3 X-Spam-Status: No, score=-110.0 required=5.0 tests=BAYES_00,SHORTCIRCUIT shortcircuit=ham autolearn=disabled version=3.4.0 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on spamd X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Dec 2014 14:41:34 -0000 Le 02/12/2014 15:27, Fabian Keil a écrit : > Are you sure kernel and userland are in sync? It seems, yes : # freebsd-version -k 10.1-RELEASE # freebsd-version -u 10.1-RELEASE # uname -v FreeBSD 10.1-RELEASE #0 r274401: Tue Nov 11 21:02:49 UTC 2014 root@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC Upgraded with freebsd-update. Everything went fine. Just to be sure, I launched : # freebsd-update IDS [...] /lib/libzfs.so.2 has SHA256 hash dd0077e90ac89cdbc7006822d8a78f7e6438d5c2602fa9c67e64f2a79babd3e5, but should have SHA256 hash 4b482b933b663f3d3c010d0e28a9608e9f663141e5ad8c8368ece8347a7f05da. /lib/libzfs_core.so.2 has SHA256 hash 1c5705dbd0332ebba13002873673e9e2397feff2e8a2c7834bfe154d37070843, but should have SHA256 hash f52bb8c66d50166bffb9833f861beb7658c4c06acf109efdbf1dbd254a06af62. /lib/libzpool.so.2 has SHA256 hash 815029709278391fb5b3cba64bdda39119e1310bc31aa9c548cdef4a372ab224, but should have SHA256 has h a9d5f42317947bfc6cb81ddcc8634fe9c93224b03285e82bc83bac69c919d464. [...] OK, I think I've found the problem. I have a lot of things that have not been upgraded in /lib and /etc. It seems related to what I found here : https://forums.freebsd.org/threads/segmentation-fault-while-upgrading-from-10-0-release-to-10-1-release.48977/ Okay, I'll upgrade it again, manually this time. Thanks ! From owner-freebsd-stable@FreeBSD.ORG Tue Dec 2 23:25:04 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 53C1347E for ; Tue, 2 Dec 2014 23:25:04 +0000 (UTC) Received: from mamba.tntpowerhost.com (mamba.tntpowerhost.com [208.100.19.247]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1AC2E3E2 for ; Tue, 2 Dec 2014 23:25:03 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=kane.mn; s=default; h=Message-ID:References:In-Reply-To:Subject:Cc:To:From:Date:Content-Transfer-Encoding:Content-Type:MIME-Version; bh=jC0flShpLD/L0BY2AdH2/B2om+cO2TbwPKPRNd2Slgk=; b=SXUMWiisowLNVOXievZ/aidqGrRKNSGclzZra9/LJlonoKVHXlpVTEIjV+tIbm0DIlO4xJAEUngUP0MzpcsgKLvUNAWrUyYfVF6lefF773ruwYr80eg8DHOyPFoDmFjDw+imdfvyGBBJfQeYbKthnoWd++ckHyBIM+7dtJ/QvQA=; Received: from localhost ([::1]:42431 helo=mamba.tntpowerhost.com) by mamba.tntpowerhost.com with esmtpa (Exim 4.84) (envelope-from ) id 1XvwoY-0006Bl-Gt; Tue, 02 Dec 2014 17:25:02 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 02 Dec 2014 17:25:02 -0600 From: Mark Kane To: Freddie Cash Subject: Re: ZFS available space difference between 10.0 and 10.1 In-Reply-To: References: Message-ID: <794adc6a7bafdef4264f2c30f2e5905f@mkproductions.org> X-Sender: mark@kane.mn User-Agent: Roundcube Webmail/1.0.1 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - mamba.tntpowerhost.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - kane.mn X-Get-Message-Sender-Via: mamba.tntpowerhost.com: authenticated_id: mark@mkproductions.org X-Source: X-Source-Args: X-Source-Dir: Cc: FreeBSD Stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Dec 2014 23:25:04 -0000 On 2014-12-02 01:19, Freddie Cash wrote: > IIUC, ZFS now reserves 3% of pool space for administrative purposes > (namely > to be able to delete things when "pool is full"). > > So a pool imported on 10.0 will show more available space than a pool > imported on 10.1. Thanks Freddie. I had looked through the 10.1 release notes and UPDATING for any changes in how ZFS reserves space, but did not note anything that looked relevant. Appreciate the info. It probably isn't super common to run pools so close to capacity like this one is (being used for temporary storage from a failed raidz), but if this is a known change that affects existing pools it would be great to have it in the release notes as it has the potential to break existing pools/filesystems in some cases :). Thanks again, -Mark From owner-freebsd-stable@FreeBSD.ORG Wed Dec 3 12:12:49 2014 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4CDA9668 for ; Wed, 3 Dec 2014 12:12:49 +0000 (UTC) Received: from smtp.digiware.nl (unknown [IPv6:2001:4cb8:90:ffff::3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0FADEC85 for ; Wed, 3 Dec 2014 12:12:48 +0000 (UTC) Received: from rack1.digiware.nl (unknown [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id 5E89916A404 for ; Wed, 3 Dec 2014 13:12:45 +0100 (CET) X-Virus-Scanned: amavisd-new at digiware.nl Received: from smtp.digiware.nl ([127.0.0.1]) by rack1.digiware.nl (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fnpD1QU8Q-cz; Wed, 3 Dec 2014 13:12:17 +0100 (CET) Received: from [192.168.101.102] (vpn.ecoracks.nl [31.223.170.173]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.digiware.nl (Postfix) with ESMTPSA id C562416A407 for ; Wed, 3 Dec 2014 13:12:17 +0100 (CET) Message-ID: <547EFE22.6050801@digiware.nl> Date: Wed, 03 Dec 2014 13:12:18 +0100 From: Willem Jan Withagen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: "stable@freebsd.org" Subject: Trying to upgrade from 9.3-Stable to 10.1-Stable Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Dec 2014 12:12:49 -0000 Hi, Trying to compile world for upgrading I run into: (single threaded make) ===> lib/clang/libclanganalysis (depend) clang-tblgen -gen-clang-attr-list -I /usr/src10/lib/clang/libclanganalysis/../../../contrib/llvm/tools/clang/include -d AttrList.inc.d -o AttrList.inc.h /usr/src10/lib/clang/libclanganalysis/../../../contrib/llvm/tools/clang/include/clang/Basic/Attr.td clang-tblgen -gen-clang-attr-classes -I /usr/src10/lib/clang/libclanganalysis/../../../contrib/llvm/tools/clang/include -d Attrs.inc.d -o Attrs.inc.h /usr/src10/lib/clang/libclanganalysis/../../../contrib/llvm/tools/clang/include/clang/Basic/Attr.td Stack dump: 0. Program arguments: clang-tblgen -gen-clang-attr-classes -I /usr/src10/lib/clang/libclanganalysis/../../../contrib/llvm/tools/clang/include -d Attrs.inc.d -o Attrs.inc.h /usr/src10/lib/clang/libclanganalysis/../../../contrib/llvm/tools/clang/include/clang/Basic/Attr.td *** Signal 11 Is this because the 9.3 toolchain doesn't like 10.1...?? Upgrade is on a atom running: 9.3-STABLE FreeBSD 9.3-STABLE #56 r269952: Thu Aug 14 07:00:37 CEST 2014 Any suggestions are welcome. --WjW From owner-freebsd-stable@FreeBSD.ORG Wed Dec 3 15:18:54 2014 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B8DC0F2E for ; Wed, 3 Dec 2014 15:18:54 +0000 (UTC) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6A8D4838 for ; Wed, 3 Dec 2014 15:18:54 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.9/8.14.9) with ESMTP id sB3FInSs001583 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 3 Dec 2014 08:18:49 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.9/8.14.9/Submit) with ESMTP id sB3FImxE001580; Wed, 3 Dec 2014 08:18:49 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Wed, 3 Dec 2014 08:18:48 -0700 (MST) From: Warren Block To: Willem Jan Withagen Subject: Re: Trying to upgrade from 9.3-Stable to 10.1-Stable In-Reply-To: <547EFE22.6050801@digiware.nl> Message-ID: References: <547EFE22.6050801@digiware.nl> User-Agent: Alpine 2.11 (BSF 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Wed, 03 Dec 2014 08:18:49 -0700 (MST) Cc: "stable@freebsd.org" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Dec 2014 15:18:54 -0000 On Wed, 3 Dec 2014, Willem Jan Withagen wrote: > Trying to compile world for upgrading I run into: > (single threaded make) > > ===> lib/clang/libclanganalysis (depend) > clang-tblgen -gen-clang-attr-list -I > /usr/src10/lib/clang/libclanganalysis/../../../contrib/llvm/tools/clang/include > -d AttrList.inc.d -o AttrList.inc.h > /usr/src10/lib/clang/libclanganalysis/../../../contrib/llvm/tools/clang/include/clang/Basic/Attr.td > clang-tblgen -gen-clang-attr-classes -I > /usr/src10/lib/clang/libclanganalysis/../../../contrib/llvm/tools/clang/include > -d Attrs.inc.d -o Attrs.inc.h > /usr/src10/lib/clang/libclanganalysis/../../../contrib/llvm/tools/clang/include/clang/Basic/Attr.td > Stack dump: > 0. Program arguments: clang-tblgen -gen-clang-attr-classes -I > /usr/src10/lib/clang/libclanganalysis/../../../contrib/llvm/tools/clang/include > -d Attrs.inc.d -o Attrs.inc.h > /usr/src10/lib/clang/libclanganalysis/../../../contrib/llvm/tools/clang/include/clang/Basic/Attr.td > *** Signal 11 > > Is this because the 9.3 toolchain doesn't like 10.1...?? > > Upgrade is on a atom running: > 9.3-STABLE FreeBSD 9.3-STABLE #56 r269952: Thu Aug 14 07:00:37 CEST 2014 'make toolchain' can help before trying a buildworld for a different major version. From owner-freebsd-stable@FreeBSD.ORG Wed Dec 3 15:21:44 2014 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2A70A22F for ; Wed, 3 Dec 2014 15:21:44 +0000 (UTC) Received: from mho-01-ewr.mailhop.org (mho-03-ewr.mailhop.org [204.13.248.66]) (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 F1A918FC for ; Wed, 3 Dec 2014 15:21:43 +0000 (UTC) Received: from [73.34.117.227] (helo=ilsoft.org) by mho-01-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1XwBkM-0005HG-A3; Wed, 03 Dec 2014 15:21:42 +0000 Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by ilsoft.org (8.14.9/8.14.9) with ESMTP id sB3FLehO009542; Wed, 3 Dec 2014 08:21:40 -0700 (MST) (envelope-from ian@FreeBSD.org) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 73.34.117.227 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1/e5zZTq9X1PXzLVIAm0Qle X-Authentication-Warning: paranoia.hippie.lan: Host revolution.hippie.lan [172.22.42.240] claimed to be [172.22.42.240] Subject: Re: Trying to upgrade from 9.3-Stable to 10.1-Stable From: Ian Lepore To: Warren Block In-Reply-To: References: <547EFE22.6050801@digiware.nl> Content-Type: text/plain; charset="us-ascii" Date: Wed, 03 Dec 2014 08:21:40 -0700 Message-ID: <1417620100.1064.72.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: "stable@freebsd.org" , Willem Jan Withagen X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Dec 2014 15:21:44 -0000 On Wed, 2014-12-03 at 08:18 -0700, Warren Block wrote: > On Wed, 3 Dec 2014, Willem Jan Withagen wrote: > > > Trying to compile world for upgrading I run into: > > (single threaded make) > > > > ===> lib/clang/libclanganalysis (depend) > > clang-tblgen -gen-clang-attr-list -I > > /usr/src10/lib/clang/libclanganalysis/../../../contrib/llvm/tools/clang/include > > -d AttrList.inc.d -o AttrList.inc.h > > /usr/src10/lib/clang/libclanganalysis/../../../contrib/llvm/tools/clang/include/clang/Basic/Attr.td > > clang-tblgen -gen-clang-attr-classes -I > > /usr/src10/lib/clang/libclanganalysis/../../../contrib/llvm/tools/clang/include > > -d Attrs.inc.d -o Attrs.inc.h > > /usr/src10/lib/clang/libclanganalysis/../../../contrib/llvm/tools/clang/include/clang/Basic/Attr.td > > Stack dump: > > 0. Program arguments: clang-tblgen -gen-clang-attr-classes -I > > /usr/src10/lib/clang/libclanganalysis/../../../contrib/llvm/tools/clang/include > > -d Attrs.inc.d -o Attrs.inc.h > > /usr/src10/lib/clang/libclanganalysis/../../../contrib/llvm/tools/clang/include/clang/Basic/Attr.td > > *** Signal 11 > > > > Is this because the 9.3 toolchain doesn't like 10.1...?? > > > > Upgrade is on a atom running: > > 9.3-STABLE FreeBSD 9.3-STABLE #56 r269952: Thu Aug 14 07:00:37 CEST 2014 > > 'make toolchain' can help before trying a buildworld for a different > major version. toolchain is one of the early steps run during buildworld, invoking it separately shouldn't make any difference. This looks like it ran out of memory... check syslog or dmesg, see if you have some "process killed; out of swap space" messages. Building clang needs a ton of memory. -- Ian From owner-freebsd-stable@FreeBSD.ORG Wed Dec 3 20:16:52 2014 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DD827FC0; Wed, 3 Dec 2014 20:16:52 +0000 (UTC) Received: from mail.takwa.de (antares.takwa.de [5.9.72.166]) by mx1.freebsd.org (Postfix) with ESMTP id A076D7D1; Wed, 3 Dec 2014 20:16:51 +0000 (UTC) Received: by mail.takwa.de (Postfix, from userid 65534) id 6D215107; Wed, 3 Dec 2014 21:10:59 +0100 (CET) X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on mail.takwa.de X-Spam-Level: X-Spam-Status: No, score=-1.5 required=5.0 tests=ALL_TRUSTED,BAYES_05 autolearn=disabled version=3.4.0 Received: from [192.168.10.5] (unknown [62.246.110.10]) by mail.takwa.de (Postfix) with ESMTPSA id 9D9B8105; Wed, 3 Dec 2014 21:10:58 +0100 (CET) Message-ID: <547F6E54.5020706@takwa.de> Date: Wed, 03 Dec 2014 21:11:00 +0100 From: Michael Schmiedgen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: "stable@freebsd.org" , freebsd-fs@freebsd.org Subject: ZFS 'mount error 5' hits production server Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Dec 2014 20:16:53 -0000 Hi list, today I upgraded one of our servers from 10.0 to 10.1 with freebsd-update. GENERIC kernel, ZFS 2-way mirror, GPT, nothing special. After booting kernel, when trying to mount the root file system I get: 'cannot mount, error 5' or something. Strangely I got this error a few weeks ago at home, running CURRENT with custom kernel: https://lists.freebsd.org/pipermail/freebsd-current/2014-October/052900.html I created the pools and datasets manually via console. Has anything changed? With legacy mountpoint, or that one needs a boot dataset, or something? Thanks, Michael Configuration is: gpart show: => 34 5860533101 ada0 GPT (2.7T) 34 256 1 freebsd-boot (128K) 290 6 - free - (3.0K) 296 8388608 2 freebsd-swap (4.0G) 8388904 5662310400 3 freebsd-zfs (2.6T) 5670699304 189833831 - free - (91G) => 34 5860533101 ada1 GPT (2.7T) 34 256 1 freebsd-boot (128K) 290 6 - free - (3.0K) 296 8388608 2 freebsd-swap (4.0G) 8388904 5662310400 3 freebsd-zfs (2.6T) 5670699304 189833831 - free - (91G) zpool status: NAME PROPERTY VALUE SOURCE tank size 2.62T - tank capacity 3% - tank altroot - default tank health ONLINE - tank guid XXX default tank version - default tank bootfs tank local tank delegation on default tank autoreplace off default tank cachefile - default tank failmode wait default tank listsnapshots off default tank autoexpand off default tank dedupditto 0 default tank dedupratio 1.00x - tank free 2.53T - tank allocated 99.0G - tank readonly off - tank comment - default tank expandsize 0 - tank freeing 0 default tank fragmentation 0% default tank leaked 0 default tank feature@async_destroy enabled local tank feature@empty_bpobj active local tank feature@lz4_compress enabled local tank feature@multi_vdev_crash_dump enabled local tank feature@spacemap_histogram disabled local tank feature@enabled_txg disabled local tank feature@hole_birth disabled local tank feature@extensible_dataset disabled local tank feature@embedded_data disabled local tank feature@bookmarks disabled local tank feature@filesystem_limits disabled local zfs get all tank: NAME PROPERTY VALUE SOURCE tank type filesystem - tank creation Aug 2012 - tank used 98.9G - tank available 2.49T - tank referenced 8.34G - tank compressratio 1.00x - tank mounted yes - tank quota none default tank reservation none default tank recordsize 128K default tank mountpoint legacy local tank sharenfs off default tank checksum on default tank compression off default tank atime off local tank devices on default tank exec on default tank setuid on default tank readonly off default tank jailed off default tank snapdir hidden default tank aclmode discard default tank aclinherit restricted default tank canmount on default tank xattr off temporary tank copies 1 default tank version 5 - tank utf8only off - tank normalization none - tank casesensitivity sensitive - tank vscan off default tank nbmand off default tank sharesmb off default tank refquota none default tank refreservation none default tank primarycache all default tank secondarycache all default tank usedbysnapshots 4.53G - tank usedbydataset 8.34G - tank usedbychildren 86.1G - tank usedbyrefreservation 0 - tank logbias latency default tank dedup off default tank mlslabel - tank sync standard default tank refcompressratio 1.00x - tank written 3.10G - tank logicalused 91.7G - tank logicalreferenced 6.71G - tank volmode default default tank filesystem_limit none default tank snapshot_limit none default tank filesystem_count none default tank snapshot_count none default tank redundant_metadata all default -- ___________________________ Michael Schmiedgen, BSc Senior Software Engineer Takwa GmbH Friedrich-List-Str. 36 99096 Erfurt GERMANY Tel +49 361 6534096 Fax +49 361 6534097 Mail schmiedgen@takwa.de Web http://www.takwa.de/ ___________________________ Amtsgericht Jena HRB 112964 Geschäftsführung: Ingo Buchholz From owner-freebsd-stable@FreeBSD.ORG Wed Dec 3 21:07:39 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4698892A; Wed, 3 Dec 2014 21:07:39 +0000 (UTC) Received: from mail-wi0-x22e.google.com (mail-wi0-x22e.google.com [IPv6:2a00:1450:400c:c05::22e]) (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 BF372CDF; Wed, 3 Dec 2014 21:07:38 +0000 (UTC) Received: by mail-wi0-f174.google.com with SMTP id h11so32746893wiw.13 for ; Wed, 03 Dec 2014 13:07:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:cc:content-type; bh=wYUXWyTh6BG8Kmrv1TR/wHbrViFagUCX1D3ea0TiwCw=; b=PScbV5oNQKE5Zz+yet7VETbfhrFDYD2waa+WkfbxhotJyNFIJLAuq33VaUlj9777Ma WLjlkAn1Qca7gj0jrNqoOpjoZB5PQYvR47GaifQ3AWXN3E+r/h0Sjq10ERMRQ+kPm3Ix r7UvHf62Xk7VSN4CEkgdxArqfDwdMUbpJpDGpV75Y/r1ofIs7cL+iwe1jAKE7RC80wwj RZ1zJZMVKmULhfw0w7o/vQW5Hlp7CHuRQChHJdN+OnfomYJPRuWttxl4oER54FgPQQso 8cSa8q2APHMCG7tYCcPnfROmqOKZvj3YGA/Fe+9E0H9T9AOOIEpLs0SHtBVC8b/ZB1Fr STDg== MIME-Version: 1.0 X-Received: by 10.180.90.206 with SMTP id by14mr16438250wib.67.1417640857212; Wed, 03 Dec 2014 13:07:37 -0800 (PST) Sender: egypcio@gmail.com Received: by 10.27.7.18 with HTTP; Wed, 3 Dec 2014 13:07:37 -0800 (PST) Date: Wed, 3 Dec 2014 18:07:37 -0300 X-Google-Sender-Auth: gUjBZfjyB26yL1Ii6jYblRIhQ1s Message-ID: Subject: Panic (fatal double fault) in a fresh installed 10.1-RELEASE (i386) r274401 with ZFS and GEOM_ELI From: =?UTF-8?Q?Vin=C3=ADcius_Zavam?= To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: gavin@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Dec 2014 21:07:39 -0000 tl;dr; I can't use 10.1-R after has it installed with ZFS(only)+GEOM_ELI. https://i.imgur.com/LzJkGoL.png pciconf? http://pastebin.com/8Fkm1Rte dmesg? http://pastebin.com/RtSUzsbg The box is an old Asus eeePC 1005pe ( http://www.asus.com/Notebooks_Ultrabooks/Eee_PC_1005PE_Seashell) and I would like to use it as a FreeBSD (i386) only machine. In the past it was running smooth with a linux-based O.S. and FreeBSD 9.0-CURRENT (UFS-only). Last week, when I got time to kill that old setup, I decided to run it as a FreeBSD-only machine by ripping everything out with a brand new fresh installation. Powered by the "new" bsdinstall(8), this step was never so easy and quick to do and I finished everything following just some dummy default options. Installation image? FreeBSD-10.1-RELEASE-i386-memstick.img, downloaded from ftp.br.freebsd.org and good checksum (sha256). 1. partitions? zfs-only (auto) 1.1. discs? only one (stripe) 1.2. encryption? yes (+swap) 2. system components? all (doc, src, ports, ..) 3. daemons? everything (moused, powerd, ntpd, ...) 4. post install steps... reboot! All safe and sweet after first reboot and I was able to put back some backup configurations and installing new packages (pkg, firefox, awesome, screen, irssi, ..., xscreensaver); but it was late and after downloading and installing everything I remembered, I decided to power off the system (usual `halt -p`) and went to bed. Blablabla, breakfast... time to touch the beastie again... NOT! https://i.imgur.com/LzJkGoL.png Tried to boot in single, safe and "WHATTHEF*" mode, but got nothing (also with ACPI off). I was just okay with that and decided to reinstall it and not loosing so much time... same usb stick... same image... same setup.. done! I went to a "Live Session" after installing everything again, but, this time, the battery discharged and the AC power cable... wasn't... errr... you know :D Again, same panic (fatal double fault); APIC ID was sometimes 01 or 00, depending on my way to boot. I reinstalled 10.1-R two more times, with a different image (also sha256 checked), downloaded from ftp.freebsd.org and ftp13.freebsd.org (yes, 13). This time I decided not to run powerd(8) and not changing powerd_flags to "-a hiadaptive -b adaptive"; rebooted; halted; powered on again... nice, but just a coincidence. I was using the machine with firefox, screen and irssi and decided to halt and sleep. Later that day I got the same panic again. I talked to people on IRC (#bsdcode/EFnet) and someone pointed me out that, somehow, ZFS wasn't able to finish "internal tasks" (routines) and this could be the cause to f* everything up. gavin@ also pointed me that powerd(8) couldn't be the "generator" of my problems. nox@ gave me the advice to wait a little more than the usual to put out the bootable memstick I created with dd(1) on a "linux machine" (and not to use bs=3D102= 40 or conv=3Dsync parameters)... nothing! Same issue. The solution (maybe)? FreeBSD 11.0-CURRENT snapshot (20141113-r274463)? NOT; downloaded the memstick, disc1 and bootonly images but they didn't work (didn't even load the bsdinstall(8) or kernel). I also tried a shot with UNetBootin (http://unetbootin.sourceforge.net) with no success and here I am! My last setup with ZFS was to install everything with ZFS+GEOM_ELI again, checkout the sources, compile and install world/kernel and upgrade everything... got nothing. The box complained about "no buffer space" while running the `make installworld` and, with no hope, I powered off the box by holding the power button :D My current setup is up and running with FreeBSD 10.1-R (i386) with UFS and no filesystem/swap encryption; that's how I was able to write the dmesg.boot and pciconf output to pastebin. Finally, I ask you: does anyone has a glue or an idea how to solve it? I really would love to run ZFS here with GELI and some fine tunning to handle this. Ah! I have two other machines (desktops) with 11.0-CURRENT (amd64) running okay with it... one with ZFS (but no encryption) and another one with UFS. Both were installed using an ISO-IMAGE of 10.1-RC1. B.R., --=20 Vin=C3=ADcius Zavam profiles.google.com/egypcio From owner-freebsd-stable@FreeBSD.ORG Wed Dec 3 21:09:45 2014 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E066DA38; Wed, 3 Dec 2014 21:09:45 +0000 (UTC) Received: from smtp.digiware.nl (smtp.digiware.nl [31.223.170.169]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9D5BBD01; Wed, 3 Dec 2014 21:09:45 +0000 (UTC) Received: from rack1.digiware.nl (unknown [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id 09E3B16A404; Wed, 3 Dec 2014 22:09:37 +0100 (CET) X-Virus-Scanned: amavisd-new at digiware.nl Received: from smtp.digiware.nl ([127.0.0.1]) by rack1.digiware.nl (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aIl7h0dIUysh; Wed, 3 Dec 2014 22:09:25 +0100 (CET) Received: from [192.168.10.9] (vaio [192.168.10.9]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.digiware.nl (Postfix) with ESMTPSA id EF00F16A406; Wed, 3 Dec 2014 22:09:24 +0100 (CET) Message-ID: <547F7C05.10404@digiware.nl> Date: Wed, 03 Dec 2014 22:09:25 +0100 From: Willem Jan Withagen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Ian Lepore , Warren Block Subject: Re: Trying to upgrade from 9.3-Stable to 10.1-Stable References: <547EFE22.6050801@digiware.nl> <1417620100.1064.72.camel@revolution.hippie.lan> In-Reply-To: <1417620100.1064.72.camel@revolution.hippie.lan> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "stable@freebsd.org" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Dec 2014 21:09:46 -0000 On 3-12-2014 16:21, Ian Lepore wrote: > On Wed, 2014-12-03 at 08:18 -0700, Warren Block wrote: >> On Wed, 3 Dec 2014, Willem Jan Withagen wrote: >> >>> Trying to compile world for upgrading I run into: >>> (single threaded make) >>> >>> ===> lib/clang/libclanganalysis (depend) >>> clang-tblgen -gen-clang-attr-list -I >>> /usr/src10/lib/clang/libclanganalysis/../../../contrib/llvm/tools/clang/include >>> -d AttrList.inc.d -o AttrList.inc.h >>> /usr/src10/lib/clang/libclanganalysis/../../../contrib/llvm/tools/clang/include/clang/Basic/Attr.td >>> clang-tblgen -gen-clang-attr-classes -I >>> /usr/src10/lib/clang/libclanganalysis/../../../contrib/llvm/tools/clang/include >>> -d Attrs.inc.d -o Attrs.inc.h >>> /usr/src10/lib/clang/libclanganalysis/../../../contrib/llvm/tools/clang/include/clang/Basic/Attr.td >>> Stack dump: >>> 0. Program arguments: clang-tblgen -gen-clang-attr-classes -I >>> /usr/src10/lib/clang/libclanganalysis/../../../contrib/llvm/tools/clang/include >>> -d Attrs.inc.d -o Attrs.inc.h >>> /usr/src10/lib/clang/libclanganalysis/../../../contrib/llvm/tools/clang/include/clang/Basic/Attr.td >>> *** Signal 11 >>> >>> Is this because the 9.3 toolchain doesn't like 10.1...?? >>> >>> Upgrade is on a atom running: >>> 9.3-STABLE FreeBSD 9.3-STABLE #56 r269952: Thu Aug 14 07:00:37 CEST 2014 >> >> 'make toolchain' can help before trying a buildworld for a different >> major version. > > toolchain is one of the early steps run during buildworld, invoking it > separately shouldn't make any difference. > > This looks like it ran out of memory... check syslog or dmesg, see if > you have some "process killed; out of swap space" messages. Building > clang needs a ton of memory. This is what dmesg says: pid 251 (clang-tblgen), uid 0: exited on signal 11 (core dumped) pid 252 (clang-tblgen), uid 0: exited on signal 11 (core dumped) pid 253 (clang-tblgen), uid 0: exited on signal 11 (core dumped) pid 25518 (clang-tblgen), uid 0: exited on signal 11 (core dumped) System has 4Gb of mem. No complaints about out of swap. There is 4Gb of swap reserved. Perhaps I should go the royal way, and go for 10.0 as intermediate step? --WjW From owner-freebsd-stable@FreeBSD.ORG Wed Dec 3 23:16:14 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DB1BE782 for ; Wed, 3 Dec 2014 23:16:14 +0000 (UTC) Received: from mail-wi0-f171.google.com (mail-wi0-f171.google.com [209.85.212.171]) (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 71B17CA5 for ; Wed, 3 Dec 2014 23:16:14 +0000 (UTC) Received: by mail-wi0-f171.google.com with SMTP id bs8so32962862wib.16 for ; Wed, 03 Dec 2014 15:16:07 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=C2lwUcIUVnS64PQ+tMYKoiF9lMtZxjwU5PFL3em/o2k=; b=X86c61RQciYElgrdfgkr19tUVeivfghBO2+PruQ3Za0jlgNJIpEtNwbzFVgh7NFMyU 3bW80xSzGWWz0P34y08BcAcLlEKzVKPohD5OjiChXFSmV3wJslTm++E3L3ThvteAD/Xd A7D6D+vkTBIuBgQBc9cL3/6aVgb/sG9WX6KX9usAi7hY65UF5aVHodGL9/BmjAwJH6Ix EZXXfMfZX2LGQW0U47enBiJcI3y16ktvoLQqkKhC4iEiablyo0j1EhlkdYT2icL7Qmw7 I1q/e1RvTsXQzzZEmWCDvr7MYKUXOmfgk7aI1c11+AgNFRgyCQXDkiIiVdrXusVV49o/ f5Dg== X-Gm-Message-State: ALoCoQm0isc8YV8NeOq+Wu3PgK5lSg+lw0o2ptQE1oU+p8sBe9SL6sZPlcCdNSgRw6APx6P0GCbN X-Received: by 10.194.234.40 with SMTP id ub8mr11457503wjc.100.1417648185478; Wed, 03 Dec 2014 15:09:45 -0800 (PST) Received: from [10.10.1.68] (82-69-141-170.dsl.in-addr.zen.co.uk. [82.69.141.170]) by mx.google.com with ESMTPSA id l10sm52604864wif.20.2014.12.03.15.09.44 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 03 Dec 2014 15:09:44 -0800 (PST) Message-ID: <547F98AF.9070701@multiplay.co.uk> Date: Wed, 03 Dec 2014 23:11:43 +0000 From: Steven Hartland User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: ZFS 'mount error 5' hits production server References: <547F6E54.5020706@takwa.de> In-Reply-To: <547F6E54.5020706@takwa.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Dec 2014 23:16:14 -0000 Have you been able to boot from rescue / mfsroot cd? On 03/12/2014 20:11, Michael Schmiedgen wrote: > Hi list, > > today I upgraded one of our servers from 10.0 to 10.1 with > freebsd-update. GENERIC kernel, ZFS 2-way mirror, GPT, nothing > special. After booting kernel, when trying to mount the > root file system I get: 'cannot mount, error 5' or something. > > Strangely I got this error a few weeks ago at home, running > CURRENT with custom kernel: > https://lists.freebsd.org/pipermail/freebsd-current/2014-October/052900.html > > > I created the pools and datasets manually via console. Has > anything changed? With legacy mountpoint, or that one needs a > boot dataset, or something? > > Thanks, > Michael > > > Configuration is: > > gpart show: > > => 34 5860533101 ada0 GPT (2.7T) > 34 256 1 freebsd-boot (128K) > 290 6 - free - (3.0K) > 296 8388608 2 freebsd-swap (4.0G) > 8388904 5662310400 3 freebsd-zfs (2.6T) > 5670699304 189833831 - free - (91G) > > => 34 5860533101 ada1 GPT (2.7T) > 34 256 1 freebsd-boot (128K) > 290 6 - free - (3.0K) > 296 8388608 2 freebsd-swap (4.0G) > 8388904 5662310400 3 freebsd-zfs (2.6T) > 5670699304 189833831 - free - (91G) > > > zpool status: > > NAME PROPERTY VALUE SOURCE > tank size 2.62T - > tank capacity 3% - > tank altroot - default > tank health ONLINE - > tank guid XXX default > tank version - default > tank bootfs tank local > tank delegation on default > tank autoreplace off default > tank cachefile - default > tank failmode wait default > tank listsnapshots off default > tank autoexpand off default > tank dedupditto 0 default > tank dedupratio 1.00x - > tank free 2.53T - > tank allocated 99.0G - > tank readonly off - > tank comment - default > tank expandsize 0 - > tank freeing 0 default > tank fragmentation 0% default > tank leaked 0 default > tank feature@async_destroy enabled local > tank feature@empty_bpobj active local > tank feature@lz4_compress enabled local > tank feature@multi_vdev_crash_dump enabled local > tank feature@spacemap_histogram disabled local > tank feature@enabled_txg disabled local > tank feature@hole_birth disabled local > tank feature@extensible_dataset disabled local > tank feature@embedded_data disabled local > tank feature@bookmarks disabled local > tank feature@filesystem_limits disabled local > > > zfs get all tank: > > NAME PROPERTY VALUE SOURCE > tank type filesystem - > tank creation Aug 2012 - > tank used 98.9G - > tank available 2.49T - > tank referenced 8.34G - > tank compressratio 1.00x - > tank mounted yes - > tank quota none default > tank reservation none default > tank recordsize 128K default > tank mountpoint legacy local > tank sharenfs off default > tank checksum on default > tank compression off default > tank atime off local > tank devices on default > tank exec on default > tank setuid on default > tank readonly off default > tank jailed off default > tank snapdir hidden default > tank aclmode discard default > tank aclinherit restricted default > tank canmount on default > tank xattr off temporary > tank copies 1 default > tank version 5 - > tank utf8only off - > tank normalization none - > tank casesensitivity sensitive - > tank vscan off default > tank nbmand off default > tank sharesmb off default > tank refquota none default > tank refreservation none default > tank primarycache all default > tank secondarycache all default > tank usedbysnapshots 4.53G - > tank usedbydataset 8.34G - > tank usedbychildren 86.1G - > tank usedbyrefreservation 0 - > tank logbias latency default > tank dedup off default > tank mlslabel - > tank sync standard default > tank refcompressratio 1.00x - > tank written 3.10G - > tank logicalused 91.7G - > tank logicalreferenced 6.71G - > tank volmode default default > tank filesystem_limit none default > tank snapshot_limit none default > tank filesystem_count none default > tank snapshot_count none default > tank redundant_metadata all default > > From owner-freebsd-stable@FreeBSD.ORG Wed Dec 3 23:18:55 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2EBAC8AC for ; Wed, 3 Dec 2014 23:18:55 +0000 (UTC) Received: from mail-wg0-f49.google.com (mail-wg0-f49.google.com [74.125.82.49]) (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 B6D2DCD2 for ; Wed, 3 Dec 2014 23:18:54 +0000 (UTC) Received: by mail-wg0-f49.google.com with SMTP id n12so13012503wgh.36 for ; Wed, 03 Dec 2014 15:18:47 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=BIkMWnK1lFEUueKbY7IaI2yd9spginKg2RfagB3pxpA=; b=GH3nvKogzLBQfVdMt1sXXwlJa+um8/C3P99lcbkYSW9o5o0BsorMZrqhYp89qq3WKX jDvQClwHjwyrQTjJPojWs6icmspCUYTY57UXboDEfPmTxe9tNMEFCaJ/cajxQv63kXLI hxL2SvATNf587iw3RuR65ttSQiPhwTbAGEXaD18VPSBX8y3JH7sdVx5cptwzc9349vVc R4LEXqy4UgLqP1SSqoTNt7x/5t4GP1/uvEYvQDK20IiLT4gQ+xJju2mNOZfjC64wSaTC Tj4AhYRfEIRK8uBDlcBsPwwzuV8SPEZgti7TzC44gxmIWZdBOW3y383KaCTi0cGrMdYs 2UcQ== X-Gm-Message-State: ALoCoQmOLLTL/EEpus7lKmSBS+jcamPa7OC5+lQIe06bF/BdBjazsI23+v7QvQcWqVSFMFQV39e0 X-Received: by 10.194.238.3 with SMTP id vg3mr10615014wjc.69.1417648245816; Wed, 03 Dec 2014 15:10:45 -0800 (PST) Received: from [10.10.1.68] (82-69-141-170.dsl.in-addr.zen.co.uk. [82.69.141.170]) by mx.google.com with ESMTPSA id qg11sm32132354wic.17.2014.12.03.15.10.44 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 03 Dec 2014 15:10:45 -0800 (PST) Message-ID: <547F98E8.9010104@multiplay.co.uk> Date: Wed, 03 Dec 2014 23:12:40 +0000 From: Steven Hartland User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: Panic (fatal double fault) in a fresh installed 10.1-RELEASE (i386) r274401 with ZFS and GEOM_ELI References: In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Dec 2014 23:18:55 -0000 Either switch to amd64 or increase the stack size of your kernel. On 03/12/2014 21:07, Vinícius Zavam wrote: > tl;dr; I can't use 10.1-R after has it installed with ZFS(only)+GEOM_ELI. > https://i.imgur.com/LzJkGoL.png > > pciconf? http://pastebin.com/8Fkm1Rte > dmesg? http://pastebin.com/RtSUzsbg > > The box is an old Asus eeePC 1005pe ( > http://www.asus.com/Notebooks_Ultrabooks/Eee_PC_1005PE_Seashell) and I > would like to use it as a FreeBSD (i386) only machine. In the past it was > running smooth with a linux-based O.S. and FreeBSD 9.0-CURRENT (UFS-only). > > Last week, when I got time to kill that old setup, I decided to run it as a > FreeBSD-only machine by ripping everything out with a brand new fresh > installation. Powered by the "new" bsdinstall(8), this step was never so > easy and quick to do and I finished everything following just some dummy > default options. > > Installation image? FreeBSD-10.1-RELEASE-i386-memstick.img, downloaded from > ftp.br.freebsd.org and good checksum (sha256). > > 1. partitions? zfs-only (auto) > 1.1. discs? only one (stripe) > 1.2. encryption? yes (+swap) > 2. system components? all (doc, src, ports, ..) > 3. daemons? everything (moused, powerd, ntpd, ...) > 4. post install steps... reboot! > > All safe and sweet after first reboot and I was able to put back some > backup configurations and installing new packages (pkg, firefox, awesome, > screen, irssi, ..., xscreensaver); but it was late and after downloading > and installing everything I remembered, I decided to power off the system > (usual `halt -p`) and went to bed. > > Blablabla, breakfast... time to touch the beastie again... NOT! > https://i.imgur.com/LzJkGoL.png > > Tried to boot in single, safe and "WHATTHEF*" mode, but got nothing (also > with ACPI off). I was just okay with that and decided to reinstall it and > not loosing so much time... same usb stick... same image... same setup.. > done! I went to a "Live Session" after installing everything again, but, > this time, the battery discharged and the AC power cable... wasn't... > errr... you know :D > > Again, same panic (fatal double fault); APIC ID was sometimes 01 or 00, > depending on my way to boot. I reinstalled 10.1-R two more times, with a > different image (also sha256 checked), downloaded from ftp.freebsd.org and > ftp13.freebsd.org (yes, 13). This time I decided not to run powerd(8) and > not changing powerd_flags to "-a hiadaptive -b adaptive"; rebooted; halted; > powered on again... nice, but just a coincidence. I was using the machine > with firefox, screen and irssi and decided to halt and sleep. Later that > day I got the same panic again. > > I talked to people on IRC (#bsdcode/EFnet) and someone pointed me out that, > somehow, ZFS wasn't able to finish "internal tasks" (routines) and this > could be the cause to f* everything up. gavin@ also pointed me that > powerd(8) couldn't be the "generator" of my problems. nox@ gave me the > advice to wait a little more than the usual to put out the bootable > memstick I created with dd(1) on a "linux machine" (and not to use bs=10240 > or conv=sync parameters)... nothing! Same issue. > > The solution (maybe)? FreeBSD 11.0-CURRENT snapshot (20141113-r274463)? > NOT; downloaded the memstick, disc1 and bootonly images but they didn't > work (didn't even load the bsdinstall(8) or kernel). I also tried a shot > with UNetBootin (http://unetbootin.sourceforge.net) with no success and > here I am! > > My last setup with ZFS was to install everything with ZFS+GEOM_ELI again, > checkout the sources, compile and install world/kernel and upgrade > everything... got nothing. The box complained about "no buffer space" while > running the `make installworld` and, with no hope, I powered off the box by > holding the power button :D > > My current setup is up and running with FreeBSD 10.1-R (i386) with UFS and > no filesystem/swap encryption; that's how I was able to write the > dmesg.boot and pciconf output to pastebin. > > Finally, I ask you: does anyone has a glue or an idea how to solve it? I > really would love to run ZFS here with GELI and some fine tunning to handle > this. > > Ah! I have two other machines (desktops) with 11.0-CURRENT (amd64) running > okay with it... one with ZFS (but no encryption) and another one with UFS. > Both were installed using an ISO-IMAGE of 10.1-RC1. > > B.R., > > From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 00:12:28 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BCA2F94C for ; Thu, 4 Dec 2014 00:12:28 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6161D37A for ; Thu, 4 Dec 2014 00:12:27 +0000 (UTC) Received: from pluto.sol.local ([188.103.87.225]) by mail.gmx.com (mrgmx001) with ESMTPSA (Nemesis) id 0M09BU-1YAYTe28yq-00uFc4; Thu, 04 Dec 2014 01:07:06 +0100 Message-ID: <547FA5A9.1010600@gmx.net> Date: Thu, 04 Dec 2014 01:07:05 +0100 From: Michael Schmiedgen User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Steven Hartland , freebsd-stable@freebsd.org Subject: Re: ZFS 'mount error 5' hits production server References: <547F6E54.5020706@takwa.de> <547F98AF.9070701@multiplay.co.uk> In-Reply-To: <547F98AF.9070701@multiplay.co.uk> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:v3/g8i1amCwOY94Xce20VjBYF1KPfRkwOKJVTE/ergBJZEVfpob lZPudgdTWJuUWFaWLJ2RqnrTTYdhnQOz32udTH2++vElr9EauyciRZYdolfY3ERirE5QV/r VJZ0lK9JNuteGfp/vhjg7ZRbQ6JbWuqxf3FKmd8wTyOmx97GYEu6F5nCLyHlOKTRKrP0uVm ObIQ7mCxSZaE4O/QPClvw== X-UI-Out-Filterresults: notjunk:1; X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Dec 2014 00:12:28 -0000 On 12/04/2014 00:11, Steven Hartland wrote: > Have you been able to boot from rescue / mfsroot cd? I got remote console via KVM and booted kernel.old from loader prompt. Everythins is fine with old 10.0 kernel. Finished upgrading by installing 10.1 userland did not help either. Thanks, Michael > On 03/12/2014 20:11, Michael Schmiedgen wrote: >> Hi list, >> >> today I upgraded one of our servers from 10.0 to 10.1 with >> freebsd-update. GENERIC kernel, ZFS 2-way mirror, GPT, nothing >> special. After booting kernel, when trying to mount the >> root file system I get: 'cannot mount, error 5' or something. >> >> Strangely I got this error a few weeks ago at home, running >> CURRENT with custom kernel: >> https://lists.freebsd.org/pipermail/freebsd-current/2014-October/052900.html >> >> >> I created the pools and datasets manually via console. Has >> anything changed? With legacy mountpoint, or that one needs a >> boot dataset, or something? >> >> Thanks, >> Michael >> >> >> Configuration is: >> >> gpart show: >> >> => 34 5860533101 ada0 GPT (2.7T) >> 34 256 1 freebsd-boot (128K) >> 290 6 - free - (3.0K) >> 296 8388608 2 freebsd-swap (4.0G) >> 8388904 5662310400 3 freebsd-zfs (2.6T) >> 5670699304 189833831 - free - (91G) >> >> => 34 5860533101 ada1 GPT (2.7T) >> 34 256 1 freebsd-boot (128K) >> 290 6 - free - (3.0K) >> 296 8388608 2 freebsd-swap (4.0G) >> 8388904 5662310400 3 freebsd-zfs (2.6T) >> 5670699304 189833831 - free - (91G) >> >> >> zpool status: >> >> NAME PROPERTY VALUE SOURCE >> tank size 2.62T - >> tank capacity 3% - >> tank altroot - default >> tank health ONLINE - >> tank guid XXX default >> tank version - default >> tank bootfs tank local >> tank delegation on default >> tank autoreplace off default >> tank cachefile - default >> tank failmode wait default >> tank listsnapshots off default >> tank autoexpand off default >> tank dedupditto 0 default >> tank dedupratio 1.00x - >> tank free 2.53T - >> tank allocated 99.0G - >> tank readonly off - >> tank comment - default >> tank expandsize 0 - >> tank freeing 0 default >> tank fragmentation 0% default >> tank leaked 0 default >> tank feature@async_destroy enabled local >> tank feature@empty_bpobj active local >> tank feature@lz4_compress enabled local >> tank feature@multi_vdev_crash_dump enabled local >> tank feature@spacemap_histogram disabled local >> tank feature@enabled_txg disabled local >> tank feature@hole_birth disabled local >> tank feature@extensible_dataset disabled local >> tank feature@embedded_data disabled local >> tank feature@bookmarks disabled local >> tank feature@filesystem_limits disabled local >> >> >> zfs get all tank: >> >> NAME PROPERTY VALUE SOURCE >> tank type filesystem - >> tank creation Aug 2012 - >> tank used 98.9G - >> tank available 2.49T - >> tank referenced 8.34G - >> tank compressratio 1.00x - >> tank mounted yes - >> tank quota none default >> tank reservation none default >> tank recordsize 128K default >> tank mountpoint legacy local >> tank sharenfs off default >> tank checksum on default >> tank compression off default >> tank atime off local >> tank devices on default >> tank exec on default >> tank setuid on default >> tank readonly off default >> tank jailed off default >> tank snapdir hidden default >> tank aclmode discard default >> tank aclinherit restricted default >> tank canmount on default >> tank xattr off temporary >> tank copies 1 default >> tank version 5 - >> tank utf8only off - >> tank normalization none - >> tank casesensitivity sensitive - >> tank vscan off default >> tank nbmand off default >> tank sharesmb off default >> tank refquota none default >> tank refreservation none default >> tank primarycache all default >> tank secondarycache all default >> tank usedbysnapshots 4.53G - >> tank usedbydataset 8.34G - >> tank usedbychildren 86.1G - >> tank usedbyrefreservation 0 - >> tank logbias latency default >> tank dedup off default >> tank mlslabel - >> tank sync standard default >> tank refcompressratio 1.00x - >> tank written 3.10G - >> tank logicalused 91.7G - >> tank logicalreferenced 6.71G - >> tank volmode default default >> tank filesystem_limit none default >> tank snapshot_limit none default >> tank filesystem_count none default >> tank snapshot_count none default >> tank redundant_metadata all default From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 00:46:01 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 741D5231 for ; Thu, 4 Dec 2014 00:46:01 +0000 (UTC) Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com [209.85.212.182]) (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 1A5E78D1 for ; Thu, 4 Dec 2014 00:46:00 +0000 (UTC) Received: by mail-wi0-f182.google.com with SMTP id h11so26271127wiw.15 for ; Wed, 03 Dec 2014 16:45:59 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=OmWAN4AfmVHafPDlLzYCMhBghzGUnSO49zmpoqzB3MY=; b=OtsiDXD9msWujBY4ty3in1T+nkCkf9OK12Y5u0vjiyXDLnhR2on/uY9iL3iQAbiajq nKvOmgrRMCdmg7neEW1bQeyzfeSK4m2kBRt6qz5uYZIqzQnKCZlXTOmlUNMxKld30X0P 70bqGysz1eYuD6OMO2g2gGzIXsSKdme6NXrVl/GNobfw8T4wPR3dCaVEkDCSz/aNiafo wCmu7VJznXw12BihNPKt4qAiXsN1QPBVni4rvwQLCVy0E1kyv2CkPK21Ed78h2L4OqLq VlZzl3TCyGOAm8aNkeeW3eKDS4CJv3WLfAUZK2uB2D87KmeAcuj5Rs+Iiug1QfEqvEeV J+hg== X-Gm-Message-State: ALoCoQnOxpg/Ca2ZA5sGqjXdeQ91An8kiI23ot7ihmSBhodPMZRvxLIoB0AET5Mt40ss1yXE+NR5 X-Received: by 10.194.175.69 with SMTP id by5mr11408880wjc.32.1417653958963; Wed, 03 Dec 2014 16:45:58 -0800 (PST) Received: from [10.10.1.68] (82-69-141-170.dsl.in-addr.zen.co.uk. [82.69.141.170]) by mx.google.com with ESMTPSA id t10sm34953040wix.15.2014.12.03.16.45.57 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 03 Dec 2014 16:45:58 -0800 (PST) Message-ID: <547FAF3C.5080002@multiplay.co.uk> Date: Thu, 04 Dec 2014 00:47:56 +0000 From: Steven Hartland User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Michael Schmiedgen , freebsd-stable@freebsd.org Subject: Re: ZFS 'mount error 5' hits production server References: <547F6E54.5020706@takwa.de> <547F98AF.9070701@multiplay.co.uk> <547FA5A9.1010600@gmx.net> In-Reply-To: <547FA5A9.1010600@gmx.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Dec 2014 00:46:01 -0000 Unfortunately error 5 isn't very helpful as that's just EIO :( When booted from the old kernel try moving out the cache file e.g. mv /boot/zfs/zpool.cache /boot/zfs/zpool.cache.old If for some reason your cache file and your disks are out of sync that might help. Also ensure your loading zfs in /etc/rc.conf zfs_enable="YES" Check you don't have anything zfs custom in /boot/loader.conf You should just have the two zfs related lines such as: zfs_load="YES" vfs.root.mountfrom="zfs:tank/root" Your pool layout does look a little odd from your zpool get all as bootfs seems to be set to just "tank" is that correct as its quite none standard? If not and your root is tank/root then that might also be your issue. Next up there should be no need for mountpoint legacy / should do just fine. If you do have a single partition install you might want to consider switching to something more standard which looks something like: NAME USED AVAIL REFER MOUNTPOINT tank 853G 292G 46.5K none tank/root 21.6G 292G 21.3G / tank/root/tmp 11.2M 292G 11.2M /tmp tank/root/var 270M 292G 270M /var Oh and ensure your boot loader has been updated: gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada0 gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada1 Hope this helps. Regards Steve On 04/12/2014 00:07, Michael Schmiedgen wrote: > On 12/04/2014 00:11, Steven Hartland wrote: >> Have you been able to boot from rescue / mfsroot cd? > > I got remote console via KVM and booted kernel.old > from loader prompt. Everythins is fine with old 10.0 > kernel. Finished upgrading by installing 10.1 userland > did not help either. > > Thanks, > Michael > >> On 03/12/2014 20:11, Michael Schmiedgen wrote: >>> Hi list, >>> >>> today I upgraded one of our servers from 10.0 to 10.1 with >>> freebsd-update. GENERIC kernel, ZFS 2-way mirror, GPT, nothing >>> special. After booting kernel, when trying to mount the >>> root file system I get: 'cannot mount, error 5' or something. >>> >>> Strangely I got this error a few weeks ago at home, running >>> CURRENT with custom kernel: >>> https://lists.freebsd.org/pipermail/freebsd-current/2014-October/052900.html >>> >>> >>> >>> I created the pools and datasets manually via console. Has >>> anything changed? With legacy mountpoint, or that one needs a >>> boot dataset, or something? >>> >>> Thanks, >>> Michael >>> >>> >>> Configuration is: >>> >>> gpart show: >>> >>> => 34 5860533101 ada0 GPT (2.7T) >>> 34 256 1 freebsd-boot (128K) >>> 290 6 - free - (3.0K) >>> 296 8388608 2 freebsd-swap (4.0G) >>> 8388904 5662310400 3 freebsd-zfs (2.6T) >>> 5670699304 189833831 - free - (91G) >>> >>> => 34 5860533101 ada1 GPT (2.7T) >>> 34 256 1 freebsd-boot (128K) >>> 290 6 - free - (3.0K) >>> 296 8388608 2 freebsd-swap (4.0G) >>> 8388904 5662310400 3 freebsd-zfs (2.6T) >>> 5670699304 189833831 - free - (91G) >>> >>> >>> zpool status: >>> >>> NAME PROPERTY VALUE SOURCE >>> tank size 2.62T - >>> tank capacity 3% - >>> tank altroot - default >>> tank health ONLINE - >>> tank guid XXX default >>> tank version - default >>> tank bootfs tank local >>> tank delegation on default >>> tank autoreplace off default >>> tank cachefile - default >>> tank failmode wait default >>> tank listsnapshots off default >>> tank autoexpand off default >>> tank dedupditto 0 default >>> tank dedupratio 1.00x - >>> tank free 2.53T - >>> tank allocated 99.0G - >>> tank readonly off - >>> tank comment - default >>> tank expandsize 0 - >>> tank freeing 0 default >>> tank fragmentation 0% default >>> tank leaked 0 default >>> tank feature@async_destroy enabled local >>> tank feature@empty_bpobj active local >>> tank feature@lz4_compress enabled local >>> tank feature@multi_vdev_crash_dump enabled local >>> tank feature@spacemap_histogram disabled local >>> tank feature@enabled_txg disabled local >>> tank feature@hole_birth disabled local >>> tank feature@extensible_dataset disabled local >>> tank feature@embedded_data disabled local >>> tank feature@bookmarks disabled local >>> tank feature@filesystem_limits disabled local >>> >>> >>> zfs get all tank: >>> >>> NAME PROPERTY VALUE SOURCE >>> tank type filesystem - >>> tank creation Aug 2012 - >>> tank used 98.9G - >>> tank available 2.49T - >>> tank referenced 8.34G - >>> tank compressratio 1.00x - >>> tank mounted yes - >>> tank quota none default >>> tank reservation none default >>> tank recordsize 128K default >>> tank mountpoint legacy local >>> tank sharenfs off default >>> tank checksum on default >>> tank compression off default >>> tank atime off local >>> tank devices on default >>> tank exec on default >>> tank setuid on default >>> tank readonly off default >>> tank jailed off default >>> tank snapdir hidden default >>> tank aclmode discard default >>> tank aclinherit restricted default >>> tank canmount on default >>> tank xattr off temporary >>> tank copies 1 default >>> tank version 5 - >>> tank utf8only off - >>> tank normalization none - >>> tank casesensitivity sensitive - >>> tank vscan off default >>> tank nbmand off default >>> tank sharesmb off default >>> tank refquota none default >>> tank refreservation none default >>> tank primarycache all default >>> tank secondarycache all default >>> tank usedbysnapshots 4.53G - >>> tank usedbydataset 8.34G - >>> tank usedbychildren 86.1G - >>> tank usedbyrefreservation 0 - >>> tank logbias latency default >>> tank dedup off default >>> tank mlslabel - >>> tank sync standard default >>> tank refcompressratio 1.00x - >>> tank written 3.10G - >>> tank logicalused 91.7G - >>> tank logicalreferenced 6.71G - >>> tank volmode default default >>> tank filesystem_limit none default >>> tank snapshot_limit none default >>> tank filesystem_count none default >>> tank snapshot_count none default >>> tank redundant_metadata all default > From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 01:07:01 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 53036733 for ; Thu, 4 Dec 2014 01:07:01 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C0B36ABC for ; Thu, 4 Dec 2014 01:07:00 +0000 (UTC) Received: from pluto.sol.local ([188.103.87.225]) by mail.gmx.com (mrgmx002) with ESMTPSA (Nemesis) id 0Lt1S6-1Y2Hw609iU-012b6r; Thu, 04 Dec 2014 02:06:52 +0100 Message-ID: <547FB3AB.6030003@gmx.net> Date: Thu, 04 Dec 2014 02:06:51 +0100 From: Michael Schmiedgen User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Steven Hartland , freebsd-stable@freebsd.org Subject: Re: ZFS 'mount error 5' hits production server References: <547F6E54.5020706@takwa.de> <547F98AF.9070701@multiplay.co.uk> <547FA5A9.1010600@gmx.net> <547FAF3C.5080002@multiplay.co.uk> In-Reply-To: <547FAF3C.5080002@multiplay.co.uk> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:S8xuczgi/uijVSwa1Ay2k4ES1/2nR3QdqGXmbR2xmnpxfGhjvg2 XaK6mZ0D209iU60fX1fsXUk+TRmBI5B7jjubqGQ/xXkkE07AsRdxhoTQVk9NmWRYOzaJLEn eaNPE3xS6JpP+Hif2sR+H2oXBL9/h+tO0Q+au5ZVopPx5XPIs3WnNamQZmQ+YgOp07L6ODj 4cTW5xBit9JziG1BwnzbQ== X-UI-Out-Filterresults: notjunk:1; X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Dec 2014 01:07:01 -0000 On 12/04/2014 01:47, Steven Hartland wrote: > Unfortunately error 5 isn't very helpful as that's just EIO :( > > When booted from the old kernel try moving out the cache file e.g. > mv /boot/zfs/zpool.cache /boot/zfs/zpool.cache.old > > If for some reason your cache file and your disks are out of sync that > might help. Ok, will try this. > Also ensure your loading zfs in /etc/rc.conf > zfs_enable="YES" It was there. > Check you don't have anything zfs custom in /boot/loader.conf > > You should just have the two zfs related lines such as: > zfs_load="YES" > vfs.root.mountfrom="zfs:tank/root" It was there. I commented all others out. > Your pool layout does look a little odd from your zpool get all as > bootfs seems to be set to just "tank" is that correct as its quite none > standard? If not and your root is tank/root then that might also be your > issue. It is tank. Back in 2012 there was no installer with ZFS features, it was done manually, with gnop trick and aligned partitions. Datasets are used for certain purposes, but kernel and userland resides on the root dataset 'tank'. > Next up there should be no need for mountpoint legacy / should do just > fine. > > If you do have a single partition install you might want to consider > switching to something more standard which looks something like: > NAME USED AVAIL REFER MOUNTPOINT > tank 853G 292G 46.5K none > tank/root 21.6G 292G 21.3G / > tank/root/tmp 11.2M 292G 11.2M /tmp > tank/root/var 270M 292G 270M /var > > Oh and ensure your boot loader has been updated: > gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada0 > gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada1 I have already done this, at least the gpt zfs bootcode. So I will give the cache file a try when I am at work tomorrow and report back. Thank you, much appreciated! Michael From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 11:26:32 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5DCC5562 for ; Thu, 4 Dec 2014 11:26:32 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E6DA1258 for ; Thu, 4 Dec 2014 11:26:31 +0000 (UTC) Received: from [192.168.10.5] ([62.246.110.10]) by mail.gmx.com (mrgmx001) with ESMTPSA (Nemesis) id 0LgYuT-1Xc3Mn3ZHZ-00o1WF; Thu, 04 Dec 2014 12:26:28 +0100 Message-ID: <548044E6.1020703@gmx.net> Date: Thu, 04 Dec 2014 12:26:30 +0100 From: Michael Schmiedgen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Steven Hartland , freebsd-stable@freebsd.org Subject: Re: ZFS 'mount error 5' hits production server References: <547F6E54.5020706@takwa.de> <547F98AF.9070701@multiplay.co.uk> <547FA5A9.1010600@gmx.net> <547FAF3C.5080002@multiplay.co.uk> <547FB3AB.6030003@gmx.net> In-Reply-To: <547FB3AB.6030003@gmx.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:9Lv+lHJGqq4UG8RihTD6L89YJ1ziix04yvho/wsGr1/fRjO1b8E v41fqlvgmBx1lrWzztHAbAG9T7mjRV2u47s24ESXXt8aR4ppPVEzQwqq1lLhkGh4JjOvG9S C8VZn0KJJWH+eaWwZTJcE6TaUHkvCGEs+C2cq0moxixr3cQhfcMKBaDGghI5YiVgJSX8y7/ Q4inUjZ+YCaOC75KrwmIA== X-UI-Out-Filterresults: notjunk:1; X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Dec 2014 11:26:32 -0000 On 04.12.2014 02:06, Michael Schmiedgen wrote: > On 12/04/2014 01:47, Steven Hartland wrote: >> Unfortunately error 5 isn't very helpful as that's just EIO :( >> >> When booted from the old kernel try moving out the cache file e.g. >> mv /boot/zfs/zpool.cache /boot/zfs/zpool.cache.old >> >> If for some reason your cache file and your disks are out of sync that >> might help. I created a new cache file. It is slightly larger in size. But no luck either. I am running out of ideas. :( As I said I had a similar 'mount error 5' problem at home some weeks ago with CURRENT and custom kernel: https://lists.freebsd.org/pipermail/freebsd-current/2014-October/052900.html Solution was there to not remove the virtual machine stuff on bottom of the kernel config. Very strange. Also the commit r271963 (callout convert) that first triggered the problem seems to be unrelated. Strange. And some months ago I had a 'mount error 5' problem if loading nvidia driver in loader.conf, also on my desktop machine at home. I found similar 'error 5' problems on the mailing list, but no solution at all. One thing I can try is to 4K align the start of the boot partition, but at the moment this is a bit risky, I have no physical access to the machine. Please tell if I should provide some more information. Thanks, Michael From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 11:50:23 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C207BB9C for ; Thu, 4 Dec 2014 11:50:23 +0000 (UTC) Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com [209.85.212.182]) (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 60A286C9 for ; Thu, 4 Dec 2014 11:50:23 +0000 (UTC) Received: by mail-wi0-f182.google.com with SMTP id h11so27591310wiw.3 for ; Thu, 04 Dec 2014 03:50:21 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=CQgqUSehAgJjppiPQ10Ffp4ci5CbTT/OwiyUUPz4BCU=; b=AK6Z3FTCbyJMuyPNYBOEwInKpkDvnXit+xqQzCQLcevJj/w0vmgy/HqDRpJMSjTBtZ ZXOV5JL1QwQhiXq9L1mERdbXa3scmKHmEHL3fTaujKYndhoDnx1jYkTFQUD38M8q5IGz MzpYObGz2HKq3HwUT024gee1+vPyZzQQyS38Iv5hJ8L+E0gHGfiT5ZLVW5xKtyfCMS7x 088LzPRz30Ll5ourjD4qzgwYqqZhx62PNRIBQ5PzYSVJEvRnNRiooQeF/Xqv/79gQQro 7eB/J2Kc66NGiJSoh1JDL69Ya7EMRv7byw+ZPAgzG8/P27mAwVk79uZH8+W1mvUtPFBJ qF3A== X-Gm-Message-State: ALoCoQmvVKWVf9XAlMZgcWUMlg823sRh1XCh3dxvI6HAgW8zQKSu1Dx87Qky2sTX9dU33zXs0XE0 X-Received: by 10.194.187.164 with SMTP id ft4mr15200076wjc.76.1417693821138; Thu, 04 Dec 2014 03:50:21 -0800 (PST) Received: from [10.10.1.68] (82-69-141-170.dsl.in-addr.zen.co.uk. [82.69.141.170]) by mx.google.com with ESMTPSA id j2sm40190201wjs.28.2014.12.04.03.50.20 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 04 Dec 2014 03:50:20 -0800 (PST) Message-ID: <54804AF3.9020805@multiplay.co.uk> Date: Thu, 04 Dec 2014 11:52:19 +0000 From: Steven Hartland User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Michael Schmiedgen , freebsd-stable@freebsd.org Subject: Re: ZFS 'mount error 5' hits production server References: <547F6E54.5020706@takwa.de> <547F98AF.9070701@multiplay.co.uk> <547FA5A9.1010600@gmx.net> <547FAF3C.5080002@multiplay.co.uk> <547FB3AB.6030003@gmx.net> <548044E6.1020703@gmx.net> In-Reply-To: <548044E6.1020703@gmx.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Dec 2014 11:50:23 -0000 On 04/12/2014 11:26, Michael Schmiedgen wrote: > On 04.12.2014 02:06, Michael Schmiedgen wrote: >> On 12/04/2014 01:47, Steven Hartland wrote: >>> Unfortunately error 5 isn't very helpful as that's just EIO :( >>> >>> When booted from the old kernel try moving out the cache file e.g. >>> mv /boot/zfs/zpool.cache /boot/zfs/zpool.cache.old >>> >>> If for some reason your cache file and your disks are out of sync that >>> might help. > > I created a new cache file. It is slightly larger in size. But > no luck either. I am running out of ideas. :( > > As I said I had a similar 'mount error 5' problem at home some weeks > ago with CURRENT and custom kernel: > https://lists.freebsd.org/pipermail/freebsd-current/2014-October/052900.html > > > Solution was there to not remove the virtual machine stuff on > bottom of the kernel config. Very strange. Also the commit r271963 > (callout convert) that first triggered the problem seems to be > unrelated. Strange. > > And some months ago I had a 'mount error 5' problem if loading > nvidia driver in loader.conf, also on my desktop machine at home. > > I found similar 'error 5' problems on the mailing list, but no solution > at all. > > One thing I can try is to 4K align the start of the boot partition, but > at the moment this is a bit risky, I have no physical access to the > machine. > > Please tell if I should provide some more information. Did you try converting from tank from legacy to standard mount point? From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 12:28:21 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9198B736 for ; Thu, 4 Dec 2014 12:28:21 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 23916BAA for ; Thu, 4 Dec 2014 12:28:20 +0000 (UTC) Received: from [192.168.10.5] ([62.246.110.10]) by mail.gmx.com (mrgmx102) with ESMTPSA (Nemesis) id 0M6fXs-1XkSq02JIy-00wWIm; Thu, 04 Dec 2014 13:28:12 +0100 Message-ID: <5480535E.3010202@gmx.net> Date: Thu, 04 Dec 2014 13:28:14 +0100 From: Michael Schmiedgen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Steven Hartland , freebsd-stable@freebsd.org Subject: Re: ZFS 'mount error 5' hits production server References: <547F6E54.5020706@takwa.de> <547F98AF.9070701@multiplay.co.uk> <547FA5A9.1010600@gmx.net> <547FAF3C.5080002@multiplay.co.uk> <547FB3AB.6030003@gmx.net> <548044E6.1020703@gmx.net> <54804AF3.9020805@multiplay.co.uk> In-Reply-To: <54804AF3.9020805@multiplay.co.uk> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:L5PXCO2u9KnqA0inwpfwwCIXiobomgHEn1HCM4yrUB6VuHJYwUM B8IO5vasukJvVvXIS25DEdomR2hwsJSbKa0IOCH/J6T5hhq9nw3hm8rchO1UxjtGktyz28P 5Bu6ALwS0L8H656PTkKdaBDaJJUN9/lHZuOXvDg4Jfl99AQEy/W0gAcZZZ7K66NJwjvBH7t R8yammm5fVmKAIlLY0dXA== X-UI-Out-Filterresults: notjunk:1; X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Dec 2014 12:28:21 -0000 On 04.12.2014 12:52, Steven Hartland wrote: > >> Please tell if I should provide some more information. > Did you try converting from tank from legacy to standard mount point? > I already tried, but I cannot, because it is mounted. # zfs set mountpoint=/ tank error: cannot unmount / (...or something) Or is there another way to do this? Thanks, Michael From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 13:07:20 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2AC703EE for ; Thu, 4 Dec 2014 13:07:20 +0000 (UTC) Received: from mail-wg0-f51.google.com (mail-wg0-f51.google.com [74.125.82.51]) (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 AE761FDE for ; Thu, 4 Dec 2014 13:07:18 +0000 (UTC) Received: by mail-wg0-f51.google.com with SMTP id k14so22302176wgh.24 for ; Thu, 04 Dec 2014 05:07:11 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-type:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=k47pWZSr1iKmiu9PUYXgPyMy9jCIGJX4DLQGUy8gnt8=; b=Fz4XAmKUr+Ar/N0+TCFBQBTqdpHUHSuZ4pGYKms7ckWNypIyZPwD7lZvy1JBk+tm1G dN4j3o0222Y9vmomfTGgpBU6655itsmSTmFnYv0vrl4puMjvXuvnxY+BHJXxq5xxbBVj Ys2Zd1em67jCcxNKLNwUEEPQ5Is+AKbiK2j+4Hlgqq4iWbI504R195DyCYn2NBZtv/S+ V3kjI3YauTgUjikE6EkDEKOwe+F0RuobvB5jkKtJHJI6tmU+DBF1z4z3cTIcTi2awDPL dxyVSsi9dtn5+PLJYblRVZNIZ7rZnBDHENr/Uht/GS0aCfDinf5VAEHHKtaWDDEZPmNZ wcNA== X-Gm-Message-State: ALoCoQkYuVyoqWbq34AjSWHQX2GzJPUDX97oG3W3D4BHkDj3HWMGHzQkXT8igTLGFU+dUcyL6wUO X-Received: by 10.180.96.42 with SMTP id dp10mr101081254wib.38.1417698431051; Thu, 04 Dec 2014 05:07:11 -0800 (PST) Received: from sigil.instinctive.eu ([2001:758:f00:340:78:41:233:119]) by mx.google.com with ESMTPSA id a14sm11709685wib.22.2014.12.04.05.07.10 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Thu, 04 Dec 2014 05:07:10 -0800 (PST) Date: Thu, 4 Dec 2014 13:06:58 +0000 From: Natacha =?iso-8859-1?Q?Port=E9?= To: Shane Ambler Subject: Re: Need help with unexpected reboot in 10.1-RELEASE Message-ID: <20141204130658.GA38683@nat.rebma.instinctive.eu> References: <20141126082923.GA87180@nat.rebma.instinctive.eu> <547601F4.2040005@ShaneWare.Biz> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <547601F4.2040005@ShaneWare.Biz> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: FreeBSD stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Dec 2014 13:07:20 -0000 Hello, on Thursday 27 November 2014 at 03:08, Shane Ambler wrote: > On 26/11/2014 18:59, Natacha Porté wrote: > > Hello, > > > > last week, I updated my main personal computer from 9.2-RELEASE to > > 10.1-RELEASE. Since then, I experienced four sudden and unexpected > > reboots (is that what is called "crashes"?). They were immediate, so > > it's not a kernel panic (which keeps the system unusable for 15s before > > rebooting). Nothing appears in the logs, but who knows what could be in > > the uncommitted buffers? > > I haven't had reboots but my machine has hung, forcing me to reset > nearly every day. When it doesn't hang the usb system fails to create > new devices forcing me to restart to access a disk. So for the record, in case anyone stumbles back here, I noticed that nVidia proprietary drivers were upgraded in the ports (relatively) close to the release of 10.1-RELEASE, so I happened to have simultaneously upgraded FreeBSD base from 9.2 to 10.1 and nVidia drivers from 331 to 340. Since I downgraded the drivers to 331 (the exact variant installed in my 9.2-RELEASE setup), I haven't experienced a single crash, despite a heavy use of World of Warcraft. So I guess the culprit is very likely to be nVidia proprietary drivers, which makes the problem out-of-topic for this ML. However I did experience one freeze (which I believe designates the same reality as "my machine has hung), during a poudriere run. Unfortunately I wasn't home when it happened, so I can only describe a sudden loss of network connectivity (other hosts saying "host is down" when trying to ping it), and when I got physical access, I couldn't make the screen leave stand-by mode, and the keyboard LED didn't toggle. I'm afraid that without network, screen or keyboard LED there is nothing left to judge whether there is still any activity going on. When I have time to babysit a poudriere run I will try again, that's a completely different problem but I would love to see it solved too (assuming it is indeed reproducible). Considering all that, I'm not sure the questions below are still relevant, but I will answer them in case it is somehow useful. > > I run with a ZFS root, and the zpool is directly on the unsliced disk. > > I have a nVidia graphics card, with the proprietary driver, on two > > screens with two displays (":0" and ":0.1") and two window managers. > > It's an amd64 platform. > > How much ram? one disk in zpool? 8 GB for RAM, one disk (half a TB) for the system and one SSD (107GB) for game installations, each of them alone in their dedicated zpool. > > I doubt this is a purely hardware issue, since I generally choose my > > hardware for its reliability, and I regularly reached three-digit days > > of uptime with 9.2-RELEASE. > > I used to install updates and restart monthly on 9.2. I tend to keep an unhealthy amount of state in the various programs I have opened, so I find seldom convenient to reboot. I might even be a few CVE's late because of that. > > I did take a snapshot of my 9.2-RELEASE, so I'm one zfs rollback away > > from checking whether it sill happens with 9.2-RELEASE. However, if as > > is likely it does work around the problem, I will probably have a hard > > time motivating myself to come back to the problem, rather than just > > waiting for the next release to see whether it has been magically solved > > without me. > > CAUTION - If you performed a zpool upgrade after upgrading to 10.1 then > you can't read the zpool in 9.x so the rollback will fail. The way back > will involve creating a new pool and transferring data. I'm aware of the non-reversibility of zpool upgrades, which is why I usually wait a few months before upgrading the zpool (when I don't forget it altogether). On top of that I can't seem to remember how to install the new bootloader, which is necessary before upgrading the pool too because I have a ZFS root. So I won't upgrade the pool before looking up (again) how to upgrade the bootloader of a mounted disk. Thanks for your help, Natacha From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 13:17:18 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 86B98828 for ; Thu, 4 Dec 2014 13:17:18 +0000 (UTC) Received: from mail-wi0-f174.google.com (mail-wi0-f174.google.com [209.85.212.174]) (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 15633159 for ; Thu, 4 Dec 2014 13:17:17 +0000 (UTC) Received: by mail-wi0-f174.google.com with SMTP id h11so34755803wiw.1 for ; Thu, 04 Dec 2014 05:17:10 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=fVHnpbgwd/z0YE7HM2hdYigQK+fTw7ru5NRM9fJGqRs=; b=J2u295W91GPavkwPc0ipXnelBQF1xvgrmdl0dOPyykfNGJgj8dJZMJ9cqNCQs2oVMu g0im5nTw+Xhy00CMWWyxefjdfKs6xA5Mqk549lHQ6pkqQXbmw7NpCeyu9kmtx0juxRHg uKCD3h8ik1n5/Az0oaf7fFM88LVhFiPHGzc1zFmrSMh9s7wQzUU6e8uJP806SJhQc940 C1v+ounDwaG5txs3STnqu6fU77MSQwonE+cmbUVbUca9uUvUZ2Xr2h4Dwe3cGi2RnNgT 9ArFjpWvzUvML/bKirrrpwgXRBcBVRBSnCweSK8DDvw014s5UyyFHrU47LHyPuCbgZ2I wVaQ== X-Gm-Message-State: ALoCoQnVjN8lebKWKS+/xGYONS8SJcxBRGDiaEhrqJZOvBt8Nn/EiaNT/PzIRVN7HCXe2y7o5nB/ X-Received: by 10.180.103.38 with SMTP id ft6mr21629967wib.19.1417699030109; Thu, 04 Dec 2014 05:17:10 -0800 (PST) Received: from [10.10.1.68] (82-69-141-170.dsl.in-addr.zen.co.uk. [82.69.141.170]) by mx.google.com with ESMTPSA id ep9sm6697721wid.3.2014.12.04.05.17.09 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 04 Dec 2014 05:17:09 -0800 (PST) Message-ID: <54805F4C.1010909@multiplay.co.uk> Date: Thu, 04 Dec 2014 13:19:08 +0000 From: Steven Hartland User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Michael Schmiedgen , freebsd-stable@freebsd.org Subject: Re: ZFS 'mount error 5' hits production server References: <547F6E54.5020706@takwa.de> <547F98AF.9070701@multiplay.co.uk> <547FA5A9.1010600@gmx.net> <547FAF3C.5080002@multiplay.co.uk> <547FB3AB.6030003@gmx.net> <548044E6.1020703@gmx.net> <54804AF3.9020805@multiplay.co.uk> <5480535E.3010202@gmx.net> In-Reply-To: <5480535E.3010202@gmx.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Dec 2014 13:17:18 -0000 On 04/12/2014 12:28, Michael Schmiedgen wrote: > On 04.12.2014 12:52, Steven Hartland wrote: >> >>> Please tell if I should provide some more information. >> Did you try converting from tank from legacy to standard mount point? >> > > I already tried, but I cannot, because it is mounted. > > # zfs set mountpoint=/ tank > error: cannot unmount / (...or something) > > Or is there another way to do this? Off the top of my head, never had to do this, you'll need to boot from a something like an mfsroot cd mount the pool with an alt root and no mount then change the mount point from there. So something like: zpool import -R /mnt -N tank zfs set mountpoint=/ tank Regards Steve From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 14:55:55 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DD52FD4C for ; Thu, 4 Dec 2014 14:55:55 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 71DA5F45 for ; Thu, 4 Dec 2014 14:55:55 +0000 (UTC) Received: from [192.168.10.5] ([62.246.110.10]) by mail.gmx.com (mrgmx001) with ESMTPSA (Nemesis) id 0MF5FT-1YCj5v3Rn9-00GJvx; Thu, 04 Dec 2014 15:55:52 +0100 Message-ID: <548075FA.30007@gmx.net> Date: Thu, 04 Dec 2014 15:55:54 +0100 From: Michael Schmiedgen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Steven Hartland , freebsd-stable@freebsd.org Subject: Re: ZFS 'mount error 5' hits production server References: <547F6E54.5020706@takwa.de> <547F98AF.9070701@multiplay.co.uk> <547FA5A9.1010600@gmx.net> <547FAF3C.5080002@multiplay.co.uk> <547FB3AB.6030003@gmx.net> <548044E6.1020703@gmx.net> <54804AF3.9020805@multiplay.co.uk> <5480535E.3010202@gmx.net> <54805F4C.1010909@multiplay.co.uk> In-Reply-To: <54805F4C.1010909@multiplay.co.uk> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:iTYnx8/LQmAsr9r6E+EsTADVk2q8jmBkFS+zZ9lbWkfLJbFxm49 kWF+FCOEUuSdTIGQOFIDmACNUBW+VYDQSRFaaEf1oaOyBqgCKHx1RUZRJXWaVpk978FS7E7 R6CYOKWTl8MO/8JGRatCU0qFdGd5yQnVTWQhSOXtMYUQG/3vdDnsxHJbN7TJxWdVFXzlp9m EtK+hnTTF/Ks+uR7+b/mg== X-UI-Out-Filterresults: notjunk:1; X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Dec 2014 14:55:56 -0000 On 04.12.2014 14:19, Steven Hartland wrote: > >> Or is there another way to do this? > Off the top of my head, never had to do this, you'll need to boot from a > something like an mfsroot cd mount the pool with an alt root and no > mount then change the mount point from there. > > So something like: > zpool import -R /mnt -N tank > zfs set mountpoint=/ tank I booted from remote rescue and switched mountpoint to '/', but the issue remains :( Thanks, Michael From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 15:14:37 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 47B002BE for ; Thu, 4 Dec 2014 15:14:37 +0000 (UTC) Received: from mail.eskimo.com (mail.eskimo.com [204.122.16.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2FEEA231 for ; Thu, 4 Dec 2014 15:14:37 +0000 (UTC) Received: from shellx.eskimo.com (shellx.eskimo.com [204.122.16.2]) by mail.eskimo.com (Postfix) with ESMTP id 779501BE9 for ; Thu, 4 Dec 2014 07:05:13 -0800 (PST) Received: by shellx.eskimo.com (Postfix, from userid 51518) id 53030BDF; Thu, 4 Dec 2014 07:05:12 -0800 (PST) Date: Thu, 4 Dec 2014 07:05:12 -0800 From: Joseph Olatt To: freebsd-stable@freebsd.org Subject: 9.2-STABLE #0 r259072 -> 9.3 buildworld fails Message-ID: <20141204150512.GA8424@shellx.eskimo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) X-Virus-Scanned: clamav-milter 0.98.4 at mail.eskimo.com X-Virus-Status: Clean X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Dec 2014 15:14:37 -0000 I'm trying to upgrade to the latest 9.3-STABLE, after a fresh "svn update" and "make buildworld" stops with the following error: /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/config/i386/sse.md: In function 'output_936': /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/config/i386/sse.md: 4517: internal compiler error: Segmentation fault: 11 Please submit a full bug report, with preprocessed source if appropriate. See for instructions. *** [insn-output.o] Error code 1 Stop in /usr/src/gnu/usr.bin/cc/cc_int. *** [all] Error code 1 Stop in /usr/src/gnu/usr.bin/cc. *** [cross-tools] Error code 1 Stop in /usr/src. *** [_cross-tools] Error code 1 Stop in /usr/src. *** [buildworld] Error code 1 Stop in /usr/src. root@rain:/usr/src # Current "uname -a": FreeBSD rain 9.2-STABLE FreeBSD 9.2-STABLE #0 r259072: Sat Dec 7 19:52:04 CST 2013 root@rain:/usr/obj/usr/src/sys/RAIN i386 Anybody else on the list seeing anything similar? From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 15:27:04 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AE6ACC16 for ; Thu, 4 Dec 2014 15:27:04 +0000 (UTC) Received: from mail-la0-x229.google.com (mail-la0-x229.google.com [IPv6:2a00:1450:4010:c03::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 2BD5F3F2 for ; Thu, 4 Dec 2014 15:27:04 +0000 (UTC) Received: by mail-la0-f41.google.com with SMTP id hv19so9869993lab.0 for ; Thu, 04 Dec 2014 07:27:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:message-id:date:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=vfgPkxZZtsYvnfJJx0l0UX6Zczlb0FUUSSbtqPNOgLE=; b=IdhG+cpEu3vsvOgR2cMCOvFQWJBcYg48RlD//eS9uCR45myKkt3wxR4ScvEv22wjRe f/vEPMPoxXcBfx/hrj6ID0jbo8cotBYHMmdqsruAZmglmQgoiGoRydu/Ypklc7PNhbQc NOq9uv2Pr/IoISBQqKxlzGzi+qmbhAtda1Q5bVJ4Yl1/Zo5lJioDOI3DjpQ42qTWnsA/ NyMR+ynoYbr6HhBSpnJbwnIgsnaBmefOYcHlAf2Mxm2VQ4DiRW4ZNK3nX5Lr+VPGDVny 5LYJ6WkQlSOVijg23n8lRVj2YItsIAxnfcZPq2hOnEWLYVBkNlsCS1dcN0mKfj1dNZmV P8gQ== X-Received: by 10.112.170.36 with SMTP id aj4mr9932076lbc.3.1417706822133; Thu, 04 Dec 2014 07:27:02 -0800 (PST) Received: from limbo.b1t.lan (167.203-pool.nikopol.net. [213.111.203.167]) by mx.google.com with ESMTPSA id a1sm509136lbi.11.2014.12.04.07.27.01 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 04 Dec 2014 07:27:01 -0800 (PST) From: Volodymyr Kostyrko X-Google-Original-From: Volodymyr Kostyrko Message-ID: <54807D44.7040904@b1t.name> Date: Thu, 04 Dec 2014 17:27:00 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: 9.2-STABLE #0 r259072 -> 9.3 buildworld fails References: <20141204150512.GA8424@shellx.eskimo.com> In-Reply-To: <20141204150512.GA8424@shellx.eskimo.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Dec 2014 15:27:04 -0000 On 04.12.2014 17:05, Joseph Olatt wrote: > I'm trying to upgrade to the latest 9.3-STABLE, after a fresh "svn > update" and "make buildworld" stops with the following error: > > > /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/config/i386/sse.md: > In function 'output_936': > /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/config/i386/sse.md: > 4517: internal compiler error: Segmentation fault: 11 > Please submit a full bug report, > with preprocessed source if appropriate. > See for instructions. > *** [insn-output.o] Error code 1 > > Stop in /usr/src/gnu/usr.bin/cc/cc_int. > *** [all] Error code 1 > > Stop in /usr/src/gnu/usr.bin/cc. > *** [cross-tools] Error code 1 > > Stop in /usr/src. > *** [_cross-tools] Error code 1 > > Stop in /usr/src. > *** [buildworld] Error code 1 > > Stop in /usr/src. > root@rain:/usr/src # > > > Current "uname -a": > FreeBSD rain 9.2-STABLE FreeBSD 9.2-STABLE #0 r259072: Sat Dec 7 > 19:52:04 CST 2013 root@rain:/usr/obj/usr/src/sys/RAIN i386 > > > Anybody else on the list seeing anything similar? > Me. I have a derelict mother on VIA KT600 chipset with some memory problems. Sometimes it faults. Sometimes it tries to kill fs. Most times running compilation again works. Does it always breaks on the same command with the same output? -- Sphinx of black quartz judge my vow. From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 15:30:35 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5F128225 for ; Thu, 4 Dec 2014 15:30:35 +0000 (UTC) Received: from mail-wi0-f179.google.com (mail-wi0-f179.google.com [209.85.212.179]) (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 E45BE628 for ; Thu, 4 Dec 2014 15:30:34 +0000 (UTC) Received: by mail-wi0-f179.google.com with SMTP id ex7so28323260wid.12 for ; Thu, 04 Dec 2014 07:30:27 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=77iyS83PUGF3Z9zJXtQNn4AsyQZabADLiFps2aOadTk=; b=P/fL3B4bTU0WT38thGMIJPd+pzy0aqdExUwCnSBY34Zd7zIFFO5J7w606al5JBx4fv pcMYrpEN4b6BHWyZ5PnVEU9rjvgVkMlFKDLoK73mYR3hQMv3mePmF+JVWb/+Xr9+Jypa 9QswRiAeHI+HUUWQ3lk81umn+F6RCJ7paQOfkp4bT9dzqCau8SedUvwuCuvCQJngukL0 RH30iUH9jyXWjkc+7YmIhRNFQTziwjlR9OfG6gBuQ2uwoT/DKlqPEIjkhu2uWI+QwnxP tryutdM1nKhCSUQt3Obd+G64gD4BxT6PwvMKFdTOkaPMKNB+1v44Zbs8ydoDznxXgHfA 328Q== X-Gm-Message-State: ALoCoQkgQwkw+7XUs322eqmz9gXexT/dWkCADvg2EfiOFLBFitndBFCll8XTLB+HzsGxi7MxBXBn X-Received: by 10.180.74.108 with SMTP id s12mr22901454wiv.28.1417706628812; Thu, 04 Dec 2014 07:23:48 -0800 (PST) Received: from [10.10.1.68] (82-69-141-170.dsl.in-addr.zen.co.uk. [82.69.141.170]) by mx.google.com with ESMTPSA id p1sm40916396wjy.22.2014.12.04.07.23.47 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 04 Dec 2014 07:23:48 -0800 (PST) Message-ID: <54807CFB.1000105@multiplay.co.uk> Date: Thu, 04 Dec 2014 15:25:47 +0000 From: Steven Hartland User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Michael Schmiedgen , freebsd-stable@freebsd.org Subject: Re: ZFS 'mount error 5' hits production server References: <547F6E54.5020706@takwa.de> <547F98AF.9070701@multiplay.co.uk> <547FA5A9.1010600@gmx.net> <547FAF3C.5080002@multiplay.co.uk> <547FB3AB.6030003@gmx.net> <548044E6.1020703@gmx.net> <54804AF3.9020805@multiplay.co.uk> <5480535E.3010202@gmx.net> <54805F4C.1010909@multiplay.co.uk> <548075FA.30007@gmx.net> In-Reply-To: <548075FA.30007@gmx.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Dec 2014 15:30:35 -0000 On 04/12/2014 14:55, Michael Schmiedgen wrote: > On 04.12.2014 14:19, Steven Hartland wrote: >> >>> Or is there another way to do this? >> Off the top of my head, never had to do this, you'll need to boot from a >> something like an mfsroot cd mount the pool with an alt root and no >> mount then change the mount point from there. >> >> So something like: >> zpool import -R /mnt -N tank >> zfs set mountpoint=/ tank > > I booted from remote rescue and switched mountpoint to '/', but the > issue remains :( Ok silly question can you boot from a 10.1 cd and import the pool (use alt root) or is that only possible on 10.0? Regards Steve From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 15:46:53 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5677D830 for ; Thu, 4 Dec 2014 15:46:53 +0000 (UTC) Received: from mail.eskimo.com (mail.eskimo.com [204.122.16.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3B7D18AF for ; Thu, 4 Dec 2014 15:46:53 +0000 (UTC) Received: from shellx.eskimo.com (shellx.eskimo.com [204.122.16.2]) by mail.eskimo.com (Postfix) with ESMTP id 84B281531; Thu, 4 Dec 2014 07:46:52 -0800 (PST) Received: by shellx.eskimo.com (Postfix, from userid 51518) id 2CF4DD44; Thu, 4 Dec 2014 07:46:51 -0800 (PST) Date: Thu, 4 Dec 2014 07:46:50 -0800 From: Joseph Olatt To: Volodymyr Kostyrko Subject: Re: 9.2-STABLE #0 r259072 -> 9.3 buildworld fails Message-ID: <20141204154650.GA23348@shellx.eskimo.com> References: <20141204150512.GA8424@shellx.eskimo.com> <54807D44.7040904@b1t.name> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <54807D44.7040904@b1t.name> User-Agent: Mutt/1.5.21 (2010-09-15) X-Virus-Scanned: clamav-milter 0.98.4 at mail.eskimo.com X-Virus-Status: Clean Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Dec 2014 15:46:53 -0000 On Thu, Dec 04, 2014 at 05:27:00PM +0200, Volodymyr Kostyrko wrote: > On 04.12.2014 17:05, Joseph Olatt wrote: > >I'm trying to upgrade to the latest 9.3-STABLE, after a fresh "svn > >update" and "make buildworld" stops with the following error: > > > > > > /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/config/i386/sse.md: > > In function 'output_936': > > /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/config/i386/sse.md: > > 4517: internal compiler error: Segmentation fault: 11 > > Please submit a full bug report, > > with preprocessed source if appropriate. > > See for instructions. > > *** [insn-output.o] Error code 1 > > > > Stop in /usr/src/gnu/usr.bin/cc/cc_int. > > *** [all] Error code 1 > > > > Stop in /usr/src/gnu/usr.bin/cc. > > *** [cross-tools] Error code 1 > > > > Stop in /usr/src. > > *** [_cross-tools] Error code 1 > > > > Stop in /usr/src. > > *** [buildworld] Error code 1 > > > > Stop in /usr/src. > > root@rain:/usr/src # > > > > > >Current "uname -a": > > FreeBSD rain 9.2-STABLE FreeBSD 9.2-STABLE #0 r259072: Sat Dec 7 > > 19:52:04 CST 2013 root@rain:/usr/obj/usr/src/sys/RAIN i386 > > > > > >Anybody else on the list seeing anything similar? > > > > Me. I have a derelict mother on VIA KT600 chipset with some memory > problems. Sometimes it faults. Sometimes it tries to kill fs. Most > times running compilation again works. > > Does it always breaks on the same command with the same output? Yes. Ran it twice and both times it stopped at the same place with the same error. From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 15:56:33 2014 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E095ECCE; Thu, 4 Dec 2014 15:56:33 +0000 (UTC) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "tensor.andric.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 98A809EB; Thu, 4 Dec 2014 15:56:33 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7::a188:410a:c650:9766] (unknown [IPv6:2001:7b8:3a7:0:a188:410a:c650:9766]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 510A6B80A; Thu, 4 Dec 2014 16:56:25 +0100 (CET) Subject: Re: Trying to upgrade from 9.3-Stable to 10.1-Stable Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) Content-Type: multipart/signed; boundary="Apple-Mail=_320CE9C9-C18D-485A-9A3B-F47C8A287BD0"; protocol="application/pgp-signature"; micalg=pgp-sha1 X-Pgp-Agent: GPGMail 2.5b3 From: Dimitry Andric In-Reply-To: <547F7C05.10404@digiware.nl> Date: Thu, 4 Dec 2014 16:56:23 +0100 Message-Id: <67830F8F-569C-4F0F-B61A-BC30AF626088@FreeBSD.org> References: <547EFE22.6050801@digiware.nl> <1417620100.1064.72.camel@revolution.hippie.lan> <547F7C05.10404@digiware.nl> To: Willem Jan Withagen X-Mailer: Apple Mail (2.1993) Cc: Warren Block , "stable@freebsd.org" , Ian Lepore X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Dec 2014 15:56:34 -0000 --Apple-Mail=_320CE9C9-C18D-485A-9A3B-F47C8A287BD0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii On 03 Dec 2014, at 22:09, Willem Jan Withagen wrote: > > On 3-12-2014 16:21, Ian Lepore wrote: ... >> This looks like it ran out of memory... check syslog or dmesg, see if >> you have some "process killed; out of swap space" messages. Building >> clang needs a ton of memory. > > This is what dmesg says: > pid 251 (clang-tblgen), uid 0: exited on signal 11 (core dumped) > pid 252 (clang-tblgen), uid 0: exited on signal 11 (core dumped) > pid 253 (clang-tblgen), uid 0: exited on signal 11 (core dumped) > pid 25518 (clang-tblgen), uid 0: exited on signal 11 (core dumped) For some reason, the clang-tblgen binaries that were built during the bootstrap-tools stage segfault, while running parts of the cross-tools stage. Obviously, this should not happen, but since it only seems to happen for you, maybe you have something special in your build environment? Can you please give us a bit more information about your environment, such as: * Architecture (i386, amd64) and exact CPU type of your machine * Full contents of /etc/make.conf and /etc/src.conf * Environment variables that might influence the build, e.g. CC, CFLAGS, DEBUG_FLAGS, etc * The specific make command line you are using to build world, including all flags and arguments -Dimitry --Apple-Mail=_320CE9C9-C18D-485A-9A3B-F47C8A287BD0 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.26 iEYEARECAAYFAlSAhCwACgkQsF6jCi4glqNEJACffXpVfwUj4+PSCw32T/g5J/+F tG4An1pnZ3KNVLeLucIdIpStPI8mctSn =E8gq -----END PGP SIGNATURE----- --Apple-Mail=_320CE9C9-C18D-485A-9A3B-F47C8A287BD0-- From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 16:51:20 2014 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B07D53C3 for ; Thu, 4 Dec 2014 16:51:20 +0000 (UTC) Received: from tau.lfms.nl (tau.lfms.nl [93.189.130.30]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3EFBA11F for ; Thu, 4 Dec 2014 16:51:19 +0000 (UTC) Received: from sim.dt.lfms.nl (dt.lfms.nl [83.84.86.53]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by tau.lfms.nl (Postfix) with ESMTPS id 80A4B8931B for ; Thu, 4 Dec 2014 17:51:11 +0100 (CET) Received: from [192.168.130.112] (borax.dt.lfms.nl [192.168.130.112]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by sim.dt.lfms.nl (Postfix) with ESMTPS id 5842C9C09084 for ; Thu, 4 Dec 2014 17:51:11 +0100 (CET) From: Walter Hop Message-Id: <20FF25C9-B2D3-490C-BD01-6F834017BDA1@spam.lifeforms.nl> Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) Subject: Re: System hang on shutdown when running freebsd-update Date: Thu, 4 Dec 2014 17:51:11 +0100 References: <2B4EEDA7-C3D9-465A-B0C9-B5728D438077@spam.lifeforms.nl> <5B600B90-9967-4031-AB9B-40ADDBE56CAF@spam.lifeforms.nl> To: freebsd-stable@FreeBSD.org In-Reply-To: <5B600B90-9967-4031-AB9B-40ADDBE56CAF@spam.lifeforms.nl> X-Mailer: Apple Mail (2.1993) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Dec 2014 16:51:20 -0000 Another update. I narrowed down the issue due to /sbin/init being = replaced. This might be the magic that freebsd-update does to make the = crash happen. (Although there might be more situations that cause a = hang.) I can completely reliably trigger the hang on a default 10.1-RELEASE = install on UFS2 in VMware Fusion with the following procedure: # chflags noschg /sbin/init # cp -Rp /sbin/init /sbin/init2 # rm -f /sbin/init # mv /sbin/init2 /sbin/init # chflags schg /sbin/init # reboot =3D> Hang after "All buffers synced." This looks useful because we don=E2=80=99t have to do a full = freebsd-update to get the hang now. I=E2=80=99d be interested to see if others can reproduce, because for me = in VMware it=E2=80=99s 100% of the times. It doesn=E2=80=99t happen on 10.0 kernel, also not on 10.1 ZFS, and not = on 10.1 UFS2 with softupdates disabled. We updated 15 machines to 10.1 with a modified upgrade procedure (first = disable softupdates, then upgrade to 10.1, then re-enable softupdates). = Without softupdates there=E2=80=99s no lockup. So: 10.1 + UFS2 + softupdates + replacing /sbin/init =3D hang+100% CPU = on next reboot/root unmount/root remount as readonly. I don=E2=80=99t know if we can research more, I wonder what would happen = on CURRENT but I don=E2=80=99t have time to build right now... Cheers, WH > On 29 Nov 2014, at 13:17, Walter Hop = wrote: >=20 > I=E2=80=99m revisiting this issue, since unfortunately I still have it = more often than not when upgrading to 10.1-RELEASE. >=20 > As Kevin Oberman suspected earlier in the thread, the issue seems to = lie in unmounting. The same hang occurs when dropping to single user = mode and trying to re-mount root as readonly. >=20 > I=E2=80=99ve also had another unmount issue after upgrading to = 10.1-RELEASE: >=20 > All buffers synced. > softdep_waitidle: Failed to flush worklist for 0xfffff800027b4330 > unmount of / failed (BUSY) >=20 > I=E2=80=99ve created a PR with the information I have: = https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D195458 >=20 > With the EOL date of FreeBSD 10.0 on the horizon, it=E2=80=99s making = me a little skittish. > Any ideas of experiments I can do to get more info out of a = problematic box, or other options to take? >=20 > Thanks! > WH >=20 >> On 28 Oct 2014, at 23:09, Walter Hop = wrote: >>=20 >> I noticed this same hang after upgrading from 10.0-RELEASE to = 10.1-RC3 in a VM running under VMware Fusion, so the problem appears = still present. >>=20 >> I could only make it happen in the single uptime just after the = system was freebsd-updated from FreeBSD 10.0 to 10.1-RC3. >>=20 >> Here is a screenshot: http://lf.ms/wait-for-reboot.png >>=20 >> It did not make any progress after 2 hours of waiting. When = restarting the VM, the disk was dirty. >>=20 >> Some interesting facts: >> - Note "swapoff: /dev/da0p2: Cannot allocate memory" in the = screenshot which might pose a clue. I haven=E2=80=99t seen this = normally. >> - FreeBSD does respond to ping while it is busy, so it is not a = complete "freeze". >> - The VM is at 100% CPU while this is going on. >=20 > --=20 > Walter Hop | PGP key: https://lifeforms.nl/pgp >=20 > _______________________________________________ > 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" --=20 Walter Hop | PGP key: https://lifeforms.nl/pgp From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 17:27:46 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AD30374D for ; Thu, 4 Dec 2014 17:27:46 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3B475831 for ; Thu, 4 Dec 2014 17:27:45 +0000 (UTC) Received: from [192.168.10.5] ([62.246.110.10]) by mail.gmx.com (mrgmx002) with ESMTPSA (Nemesis) id 0LsCdj-1Xrs1348Wl-013yW1; Thu, 04 Dec 2014 18:27:43 +0100 Message-ID: <54809990.6070402@gmx.net> Date: Thu, 04 Dec 2014 18:27:44 +0100 From: Michael Schmiedgen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Steven Hartland , freebsd-stable@freebsd.org Subject: Re: ZFS 'mount error 5' hits production server References: <547F6E54.5020706@takwa.de> <547F98AF.9070701@multiplay.co.uk> <547FA5A9.1010600@gmx.net> <547FAF3C.5080002@multiplay.co.uk> <547FB3AB.6030003@gmx.net> <548044E6.1020703@gmx.net> <54804AF3.9020805@multiplay.co.uk> <5480535E.3010202@gmx.net> <54805F4C.1010909@multiplay.co.uk> <548075FA.30007@gmx.net> <54807CFB.1000105@multiplay.co.uk> In-Reply-To: <54807CFB.1000105@multiplay.co.uk> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:uOh+xjuHuIamaZDIX/qw8Ho0kY+QhhWBeAKsiC/IUybRrK5v5HT O4N6YdHdAu420Kw0pC6ftp/FuZFOTkFxJDRVYXP7csL1HamgjYOw37FtkUWz2SHPoYzhvHb 8oJWAO0o+ZHrah6M8o3Qwj+BsWdtlZJJJfve095zZT93hWJqNmwHaCfo3B9Z3O1xQrtgIec BjgTGelahg1/btUUrG8vg== X-UI-Out-Filterresults: notjunk:1; X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Dec 2014 17:27:46 -0000 On 04.12.2014 16:25, Steven Hartland wrote: > Ok silly question can you boot from a 10.1 cd and import the pool (use > alt root) or is that only possible on 10.0? At the moment it is only possible to boot 10.0 as rescue via network boot. I can observe and when 10.1 is available I can try to import it. Thanks, Michael From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 17:37:48 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4B35FBC1 for ; Thu, 4 Dec 2014 17:37:48 +0000 (UTC) Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) (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 D0A8995A for ; Thu, 4 Dec 2014 17:37:47 +0000 (UTC) Received: by mail-wg0-f50.google.com with SMTP id k14so23242290wgh.37 for ; Thu, 04 Dec 2014 09:37:45 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=ZEyJssbrnBPB7IIDeI2FDapTBfKsYwFbf4kVwsQ0CF0=; b=TCFHfFLRm1ojO1ukJDogmMemeXtk1uf2UdN2KCLVeiNOzA0pJEzWOKYnHLmq7bOqrb PJenORbfyYcLwzvHg3bXkqUxT2SB5WrLnSPiJeqc3cM9aoXXyU3pDwEfCIQ32TQd1dyC /gBJ0A0d/mcwXUXngl0Jq7pG8ZrDRHd34V8mOsjfSLDPGKAW89YvpLR4z6JN+L0FPKtw 5ayxscz4fc8n9r6awi/aJvLrmTGRzPmJfxA/m5StcHOCTcFNTMadEJjZ+Et8zYH4mRCI FLmVcbokm/CmHAPlsf8GwYGzzM+Tc6IAaB0ZlAJagNWnyDgiQJhTx5WvkY5mvEf/PJLI AIpQ== X-Gm-Message-State: ALoCoQmQo2DFzInlvrFaXSuCvX60gUhirKsUi6suGhgRON1U7x3lD2mWvqN/tS+mdE7/PjK9e+wW X-Received: by 10.180.20.6 with SMTP id j6mr425970wie.59.1417714244517; Thu, 04 Dec 2014 09:30:44 -0800 (PST) Received: from [10.10.1.68] (82-69-141-170.dsl.in-addr.zen.co.uk. [82.69.141.170]) by mx.google.com with ESMTPSA id ly9sm5789162wjb.24.2014.12.04.09.30.43 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 04 Dec 2014 09:30:43 -0800 (PST) Message-ID: <54809ABB.5080006@multiplay.co.uk> Date: Thu, 04 Dec 2014 17:32:43 +0000 From: Steven Hartland User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Michael Schmiedgen , freebsd-stable@freebsd.org Subject: Re: ZFS 'mount error 5' hits production server References: <547F6E54.5020706@takwa.de> <547F98AF.9070701@multiplay.co.uk> <547FA5A9.1010600@gmx.net> <547FAF3C.5080002@multiplay.co.uk> <547FB3AB.6030003@gmx.net> <548044E6.1020703@gmx.net> <54804AF3.9020805@multiplay.co.uk> <5480535E.3010202@gmx.net> <54805F4C.1010909@multiplay.co.uk> <548075FA.30007@gmx.net> <54807CFB.1000105@multiplay.co.uk> <54809990.6070402@gmx.net> In-Reply-To: <54809990.6070402@gmx.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Dec 2014 17:37:48 -0000 On 04/12/2014 17:27, Michael Schmiedgen wrote: > On 04.12.2014 16:25, Steven Hartland wrote: >> Ok silly question can you boot from a 10.1 cd and import the pool (use >> alt root) or is that only possible on 10.0? > > At the moment it is only possible to boot 10.0 as rescue > via network boot. I can observe and when 10.1 is available > I can try to import it. We use mm's excellent mfsbsd ISO images which can be found here: http://mfsbsd.vx.sk/ Regards Steve From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 17:57:57 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AEA6834C for ; Thu, 4 Dec 2014 17:57:57 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3F5EABBD for ; Thu, 4 Dec 2014 17:57:56 +0000 (UTC) Received: from [192.168.10.5] ([62.246.110.10]) by mail.gmx.com (mrgmx002) with ESMTPSA (Nemesis) id 0MI5JG-1Y0SHU0z0Q-003yFP; Thu, 04 Dec 2014 18:57:54 +0100 Message-ID: <5480A0A4.6070906@gmx.net> Date: Thu, 04 Dec 2014 18:57:56 +0100 From: Michael Schmiedgen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Steven Hartland , freebsd-stable@freebsd.org Subject: Re: ZFS 'mount error 5' hits production server References: <547F6E54.5020706@takwa.de> <547F98AF.9070701@multiplay.co.uk> <547FA5A9.1010600@gmx.net> <547FAF3C.5080002@multiplay.co.uk> <547FB3AB.6030003@gmx.net> <548044E6.1020703@gmx.net> <54804AF3.9020805@multiplay.co.uk> <5480535E.3010202@gmx.net> <54805F4C.1010909@multiplay.co.uk> <548075FA.30007@gmx.net> <54807CFB.1000105@multiplay.co.uk> <54809990.6070402@gmx.net> <54809ABB.5080006@multiplay.co.uk> In-Reply-To: <54809ABB.5080006@multiplay.co.uk> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:kttcXyflb3tebc3ZjFpK6fU/3CFlw3LJ81q1ExqALutdmhkvrCQ OHRIZdMcxWSzvPProhRAGd1Gc75EdW4M1oAhGxuotidAGRXKBnQsBIgQgLcn9SFzqt0+3fB g9Em15z8ZiApJCGeDl8rUW0FK0gIttbxPFoGhy78vT7ugr5hAovcXL2duK1c/nNexc2bM9O J4afP8t5rWtjlwW8sw2/g== X-UI-Out-Filterresults: notjunk:1; X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Dec 2014 17:57:57 -0000 On 04.12.2014 18:32, Steven Hartland wrote: > We use mm's excellent mfsbsd ISO images which can be found here: > http://mfsbsd.vx.sk/ Our provider uses it too, they boot it over net to aid in rescue mode. You can trigger it in the webinterface. But at the moment only 10.0 is available. I got no physical access to the machine, so I have to wait until they offer 10.1. Thanks again, Michael From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 18:07:24 2014 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 555616BF; Thu, 4 Dec 2014 18:07:24 +0000 (UTC) Received: from smtp.digiware.nl (smtp.digiware.nl [31.223.170.169]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 08901CC6; Thu, 4 Dec 2014 18:07:23 +0000 (UTC) Received: from rack1.digiware.nl (unknown [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id EEEF716A403; Thu, 4 Dec 2014 19:07:19 +0100 (CET) X-Virus-Scanned: amavisd-new at digiware.nl Received: from smtp.digiware.nl ([127.0.0.1]) by rack1.digiware.nl (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U9D9NsrcHT0z; Thu, 4 Dec 2014 19:07:18 +0100 (CET) Received: from [IPv6:2001:4cb8:3:1:b48d:cc13:4c87:ed56] (unknown [IPv6:2001:4cb8:3:1:b48d:cc13:4c87:ed56]) by smtp.digiware.nl (Postfix) with ESMTP id 593E416A407; Thu, 4 Dec 2014 19:07:18 +0100 (CET) Message-ID: <5480A2CF.9060504@digiware.nl> Date: Thu, 04 Dec 2014 19:07:11 +0100 From: Willem Jan Withagen Organization: Digiware Management b.v. User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Dimitry Andric Subject: Re: Trying to upgrade from 9.3-Stable to 10.1-Stable References: <547EFE22.6050801@digiware.nl> <1417620100.1064.72.camel@revolution.hippie.lan> <547F7C05.10404@digiware.nl> <67830F8F-569C-4F0F-B61A-BC30AF626088@FreeBSD.org> In-Reply-To: <67830F8F-569C-4F0F-B61A-BC30AF626088@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Warren Block , "stable@freebsd.org" , Ian Lepore X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Dec 2014 18:07:24 -0000 On 2014-12-04 16:56, Dimitry Andric wrote: > On 03 Dec 2014, at 22:09, Willem Jan Withagen wrote: >> >> On 3-12-2014 16:21, Ian Lepore wrote: > ... >>> This looks like it ran out of memory... check syslog or dmesg, see if >>> you have some "process killed; out of swap space" messages. Building >>> clang needs a ton of memory. >> >> This is what dmesg says: >> pid 251 (clang-tblgen), uid 0: exited on signal 11 (core dumped) >> pid 252 (clang-tblgen), uid 0: exited on signal 11 (core dumped) >> pid 253 (clang-tblgen), uid 0: exited on signal 11 (core dumped) >> pid 25518 (clang-tblgen), uid 0: exited on signal 11 (core dumped) > > For some reason, the clang-tblgen binaries that were built during the > bootstrap-tools stage segfault, while running parts of the cross-tools > stage. Obviously, this should not happen, but since it only seems to > happen for you, maybe you have something special in your build > environment? > > Can you please give us a bit more information about your environment, > such as: > > * Architecture (i386, amd64) and exact CPU type of your machine > * Full contents of /etc/make.conf and /etc/src.conf > * Environment variables that might influence the build, e.g. CC, CFLAGS, > DEBUG_FLAGS, etc > * The specific make command line you are using to build world, including > all flags and arguments This was pilot error. To reduce buildtime on this poor atom, I disabled building clang in 9.x... But did have a very very old version left over from one of the first builds. (that took too long) So I was using those old tools. Once I disabled that in /etc/src.conf make toolchain builds soothly. Thanx for helping me realise that. --WjW From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 19:33:44 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 704A9F71 for ; Thu, 4 Dec 2014 19:33:44 +0000 (UTC) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.81]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3488E97B for ; Thu, 4 Dec 2014 19:33:44 +0000 (UTC) Received: from smtp.greenhost.nl ([213.108.104.138]) by smarthost1.greenhost.nl with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1Xwc9e-0008D0-VA for freebsd-stable@freebsd.org; Thu, 04 Dec 2014 20:33:40 +0100 Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes To: freebsd-stable@freebsd.org Date: Thu, 04 Dec 2014 20:33:33 +0100 Subject: restore a periodic backup of pkg db MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: User-Agent: Opera Mail/12.16 (FreeBSD) X-Authenticated-As-Hash: bdb49c4ff80bd276e321aade33e76e02752072e2 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: - X-Spam-Score: -1.0 X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED, BAYES_40 autolearn=disabled version=3.3.1 X-Scan-Signature: 964c6a2bc69af72888bec91466701c23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Dec 2014 19:33:44 -0000 Hi, In /var/backup is a daily backup of the pkg db. The backup is not made by 'pkg backup', but by 'pkg shell .dump' as I read in /usr/local/etc/periodic/daily/411.pkg-backup. How do I restore this properly? I can't use pkg backup -r because the backup is a file containing sql statements. Restoring by 'xzcat /var/backup/pkg.sql.xz | pkg shell' gives errors like the one below. (It does not understand hex strings very well. Regards, Ronald. [root@sheeva /var/db/pkg]# xzcat /var/backups/pkg.sql.xz | pkg shell Error: near line 33904: near "'0001308D03020101030002010104000101010300020101030001010103000E01010300060101040005010106000101010400010101040002010103000101010400030101050006010105000301010400010101040002010103000701010500040101040001010104000701010400020101040003010104000101010500060101030001010105000601010600030101030001010103030001010105000201010400010101040004010104000201010500030101040002010104000301010500010101040009010105000101010300010101040001010105000301010300020101040001010106000901010300010101030003010104000101010600020101040001010104000201010600010101060001010106000B0101030004010103000801010303000101010303000101010303000101010303000101010303000201010300080101050008010104000201010303000401010500030101040002010104000601010500010101040006010106000101010300030101040001010103000F0101050002010106000B0101030001010105000101350B0B01010600AF0101010600'": syntax error From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 20:26:06 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BFFEEB3A for ; Thu, 4 Dec 2014 20:26:06 +0000 (UTC) Received: from mail-lb0-x231.google.com (mail-lb0-x231.google.com [IPv6:2a00:1450:4010:c04::231]) (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 3C254EEA for ; Thu, 4 Dec 2014 20:26:06 +0000 (UTC) Received: by mail-lb0-f177.google.com with SMTP id b6so5251994lbj.36 for ; Thu, 04 Dec 2014 12:26:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:message-id:date:user-agent:mime-version:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=Ob0+LMSDrm6PWcGCvYNHAtrsNq62MnVmvoWJ6PUMkw0=; b=0D5QY2PIQDcQfRpGYCyx9M5xPG2b/2mTScRIs2iElvwad6AXpbeJ/ahrHp7p/qm6Pq 4DBlxKKaP0VmFE26+3MuEKDCd1d1lbnnqGdK0xKyIP4Z+MLi+BK/dBCowJjZoJyxN5+x XUjW6u4iLg6V0crEwc8p0spW4A+FtXmmnXmRdkbWyh397qgKdWLMBhv3/H+EQGwYw4vx mjnn5bdG6US6bFIWIQkZsn0Yr5VhvW5djNavGqpZvN0rKv6f+E6hqNYN44WM7zuf6ntl vApUHFf8o8Eg4/Igl9bpa3asKxW4AOdgJYh3C59RJyVXEW5KrfFSCLLki/U4h9jsAJhr 7ILw== X-Received: by 10.152.36.232 with SMTP id t8mr11385841laj.6.1417724764213; Thu, 04 Dec 2014 12:26:04 -0800 (PST) Received: from limbo.b1t.lan (167.203-pool.nikopol.net. [213.111.203.167]) by mx.google.com with ESMTPSA id rb2sm7617414lbb.19.2014.12.04.12.26.03 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 04 Dec 2014 12:26:03 -0800 (PST) From: Volodymyr Kostyrko X-Google-Original-From: Volodymyr Kostyrko Message-ID: <5480C35A.1040807@b1t.name> Date: Thu, 04 Dec 2014 22:26:02 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 CC: freebsd-stable@freebsd.org Subject: Re: 9.2-STABLE #0 r259072 -> 9.3 buildworld fails References: <20141204150512.GA8424@shellx.eskimo.com> <54807D44.7040904@b1t.name> <20141204154650.GA23348@shellx.eskimo.com> In-Reply-To: <20141204154650.GA23348@shellx.eskimo.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Dec 2014 20:26:06 -0000 On 04.12.2014 17:46, Joseph Olatt wrote: > On Thu, Dec 04, 2014 at 05:27:00PM +0200, Volodymyr Kostyrko wrote: >> On 04.12.2014 17:05, Joseph Olatt wrote: >>> I'm trying to upgrade to the latest 9.3-STABLE, after a fresh "svn >>> update" and "make buildworld" stops with the following error: >>> >>> >>> /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/config/i386/sse.md: >>> In function 'output_936': >>> /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/config/i386/sse.md: >>> 4517: internal compiler error: Segmentation fault: 11 >>> Please submit a full bug report, >>> with preprocessed source if appropriate. >>> See for instructions. >>> *** [insn-output.o] Error code 1 >>> >>> Stop in /usr/src/gnu/usr.bin/cc/cc_int. >>> *** [all] Error code 1 >>> >>> Stop in /usr/src/gnu/usr.bin/cc. >>> *** [cross-tools] Error code 1 >>> >>> Stop in /usr/src. >>> *** [_cross-tools] Error code 1 >>> >>> Stop in /usr/src. >>> *** [buildworld] Error code 1 >>> >>> Stop in /usr/src. >>> root@rain:/usr/src # >>> >>> >>> Current "uname -a": >>> FreeBSD rain 9.2-STABLE FreeBSD 9.2-STABLE #0 r259072: Sat Dec 7 >>> 19:52:04 CST 2013 root@rain:/usr/obj/usr/src/sys/RAIN i386 >>> >>> >>> Anybody else on the list seeing anything similar? >>> >> >> Me. I have a derelict mother on VIA KT600 chipset with some memory >> problems. Sometimes it faults. Sometimes it tries to kill fs. Most >> times running compilation again works. >> >> Does it always breaks on the same command with the same output? > > > Yes. Ran it twice and both times it stopped at the same place with the > same error. So this has nothing to do with bad memory. Try building WITH_CLANG_IS_CC or even WITHOUT_GCC. Those should be added to the /etc/src.conf: WITH_CLANG_IS_CC=yes WITHOUT_GCC=yes Meanwhile, can you name your processor or list what is in your /etc/make.conf? -- Sphinx of black quartz judge my vow. From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 20:56:59 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DD3C74CE for ; Thu, 4 Dec 2014 20:56:59 +0000 (UTC) Received: from udns.ultimatedns.net (unknown [IPv6:2602:d1:b4d6:e600:4261:86ff:fef6:aa2a]) (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 B2D812EA for ; Thu, 4 Dec 2014 20:56:59 +0000 (UTC) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id sB4KvIxk099835; Thu, 4 Dec 2014 12:57:18 -0800 (PST) (envelope-from bsd-lists@bsdforge.com) To: freebsd-stable@freebsd.org, "Ronald Klop" In-Reply-To: References: From: "Chris H" Subject: Re: restore a periodic backup of pkg db Date: Thu, 04 Dec 2014 12:57:19 -0800 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: <11af9c0faee95463a12bfbae7620a48a@ultimatedns.net> Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Dec 2014 20:56:59 -0000 On Thu, 04 Dec 2014 20:33:33 +0100 "Ronald Klop" wrote > Hi, > > In /var/backup is a daily backup of the pkg db. The backup is not made by > 'pkg backup', but by 'pkg shell .dump' as I read in > /usr/local/etc/periodic/daily/411.pkg-backup. > > How do I restore this properly? > I can't use pkg backup -r because the backup is a file containing > sql statements. > Restoring by 'xzcat /var/backup/pkg.sql.xz | pkg shell' gives errors like > the one below. (It does not understand hex strings very well. > > Regards, > Ronald. I ran into an issue, where pkg(8) corrupted the working sqlite3(1) DB while I was building a meta-port. I looked to sqlite3, and the backup copy, to recreate the DB. Problem was; sqlite3 couldn't work with the backup. bapt@ requested a copy of the file, which I sent. But haven't heard back. In the meantime, I simply unpacked the copy that periodic(8) made. Then re-named the (borked) working DB, and re-named the periodic(8) backup to reflect the name of the (borked) working copy. What you will need to do, is determine *which* periodic(8) copy is your local.sqlite3 copy. Other than that, it should be a *fairly* trivial task. --Chris > > > [root@sheeva /var/db/pkg]# xzcat /var/backups/pkg.sql.xz | pkg shell > Error: near line 33904: near > "'0001308D03020101030002010104000101010300020101030001010103000E0101030006010 > 10400050101060001010104000101010400020101030001010104000301010500060101050003 > 01010400010101040002010103000701010500040101040001010104000701010400020101040 > 00301010400010101050006010103000101010500060101060003010103000101010303000101 > 01050002010104000101010400040101040002010105000301010400020101040003010105000 > 10101040009010105000101010300010101040001010105000301010300020101040001010106 > 00090101030001010103000301010400010101060002010104000101010400020101060001010 > 1060001010106000B010103000401010300080101030300010101030300010101030300010101 > 03030001010103030002010103000801010500080101040002010103030004010105000301010 > 40002010104000601010500010101040006010106000101010300030101040001010103000F01 > 01050002010106000B0101030001010105000101350B0B01010600AF0101010600'": > syntax error > _______________________________________________ > 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-stable@FreeBSD.ORG Thu Dec 4 23:26:47 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E592134D for ; Thu, 4 Dec 2014 23:26:47 +0000 (UTC) Received: from mail.eskimo.com (mail.eskimo.com [204.122.16.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CB1AF855 for ; Thu, 4 Dec 2014 23:26:47 +0000 (UTC) Received: from shellx.eskimo.com (shellx.eskimo.com [204.122.16.2]) by mail.eskimo.com (Postfix) with ESMTP id E3FBCDD8; Thu, 4 Dec 2014 15:26:46 -0800 (PST) Received: by shellx.eskimo.com (Postfix, from userid 51518) id BD576D44; Thu, 4 Dec 2014 15:26:45 -0800 (PST) Date: Thu, 4 Dec 2014 15:26:45 -0800 From: Joseph Olatt To: Volodymyr Kostyrko Subject: Re: 9.2-STABLE #0 r259072 -> 9.3 buildworld fails Message-ID: <20141204232645.GA5570@shellx.eskimo.com> References: <20141204150512.GA8424@shellx.eskimo.com> <54807D44.7040904@b1t.name> <20141204154650.GA23348@shellx.eskimo.com> <5480C35A.1040807@b1t.name> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5480C35A.1040807@b1t.name> User-Agent: Mutt/1.5.21 (2010-09-15) X-Virus-Scanned: clamav-milter 0.98.4 at mail.eskimo.com X-Virus-Status: Clean Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Dec 2014 23:26:48 -0000 On Thu, Dec 04, 2014 at 10:26:02PM +0200, Volodymyr Kostyrko wrote: > On 04.12.2014 17:46, Joseph Olatt wrote: > >On Thu, Dec 04, 2014 at 05:27:00PM +0200, Volodymyr Kostyrko wrote: > >>On 04.12.2014 17:05, Joseph Olatt wrote: > >>>I'm trying to upgrade to the latest 9.3-STABLE, after a fresh "svn > >>>update" and "make buildworld" stops with the following error: > >>> > >>> > >>> /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/config/i386/sse.md: > >>> In function 'output_936': > >>> /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/config/i386/sse.md: > >>> 4517: internal compiler error: Segmentation fault: 11 > >>> Please submit a full bug report, > >>> with preprocessed source if appropriate. > >>> See for instructions. > >>> *** [insn-output.o] Error code 1 > >>> > >>> Stop in /usr/src/gnu/usr.bin/cc/cc_int. > >>> *** [all] Error code 1 > >>> > >>> Stop in /usr/src/gnu/usr.bin/cc. > >>> *** [cross-tools] Error code 1 > >>> > >>> Stop in /usr/src. > >>> *** [_cross-tools] Error code 1 > >>> > >>> Stop in /usr/src. > >>> *** [buildworld] Error code 1 > >>> > >>> Stop in /usr/src. > >>> root@rain:/usr/src # > >>> > >>> > >>>Current "uname -a": > >>> FreeBSD rain 9.2-STABLE FreeBSD 9.2-STABLE #0 r259072: Sat Dec 7 > >>> 19:52:04 CST 2013 root@rain:/usr/obj/usr/src/sys/RAIN i386 > >>> > >>> > >>>Anybody else on the list seeing anything similar? > >>> > >> > >>Me. I have a derelict mother on VIA KT600 chipset with some memory > >>problems. Sometimes it faults. Sometimes it tries to kill fs. Most > >>times running compilation again works. > >> > >>Does it always breaks on the same command with the same output? > > > > > >Yes. Ran it twice and both times it stopped at the same place with the > >same error. > > So this has nothing to do with bad memory. Try building > WITH_CLANG_IS_CC or even WITHOUT_GCC. Those should be added to the > /etc/src.conf: > > WITH_CLANG_IS_CC=yes > WITHOUT_GCC=yes > > Meanwhile, can you name your processor or list what is in your > /etc/make.conf? I think you are correct here. I wondered why GCC was being invoked. Unfortunately, I'm unable to test your suggestion. I've put another hard disk in system, installed 10.1-RELEASE and updated the sources to 10-STABLE and am currently building world without any issues. /etc/make.conf was completely empty (I had checked that). The processor is: i386 (an old Dell Inspiron 8200! FreeBSD allows these old laptops to continue to live and be of service...) Thanks for taking the time. From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 23:44:44 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4ADA58F3 for ; Thu, 4 Dec 2014 23:44:44 +0000 (UTC) Received: from mail-la0-x22a.google.com (mail-la0-x22a.google.com [IPv6:2a00:1450:4010:c03::22a]) (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 BBB7EA50 for ; Thu, 4 Dec 2014 23:44:43 +0000 (UTC) Received: by mail-la0-f42.google.com with SMTP id gd6so1745898lab.15 for ; Thu, 04 Dec 2014 15:44:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=gXOl/yCa7E5vaFtVvFGXta0oCKwCTF0S9nv/dhiAIW0=; b=O3rxK/T5gDLHYHbkKXvUmlkYGhO1IOlK209jv/IRROmF66f3Z78izCarQ/Xc+5yips dj/nHAhhLdUWVU1xiiPv95hEE/secp5asaNyNtxseko1mnEGTjFuzjt/L838v+iJjl1/ Q7PAz+sag7B0zSuCX0va9lVxKYna/fDw6HlSaNGQQk9WI1x85mPIxSPR3LeEePZ40Jwa HAxhfk8OgqtJo5pZcYyaQAdXk0pUZ3gbD2L+VKCrCLOz1IRpWKuISueNYbMYEwaMjREM Zp4xB17/9BLZKljuzH7qJyAFIkhfPHyimwQ+KyZpfmL4i0RdoASwDs/bD6F7AitfZOjZ 0J5g== X-Received: by 10.112.45.228 with SMTP id q4mr82110lbm.35.1417736681855; Thu, 04 Dec 2014 15:44:41 -0800 (PST) Received: from limbo.b1t.lan (167.203-pool.nikopol.net. [213.111.203.167]) by mx.google.com with ESMTPSA id v7sm5459192lbb.2.2014.12.04.15.44.41 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 04 Dec 2014 15:44:41 -0800 (PST) Message-ID: <5480F1E8.10802@gmail.com> Date: Fri, 05 Dec 2014 01:44:40 +0200 From: Volodymyr Kostyrko User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 CC: freebsd-stable@freebsd.org Subject: Re: 9.2-STABLE #0 r259072 -> 9.3 buildworld fails References: <20141204150512.GA8424@shellx.eskimo.com> <54807D44.7040904@b1t.name> <20141204154650.GA23348@shellx.eskimo.com> <5480C35A.1040807@b1t.name> <20141204232645.GA5570@shellx.eskimo.com> In-Reply-To: <20141204232645.GA5570@shellx.eskimo.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Dec 2014 23:44:44 -0000 On 05.12.2014 01:26, Joseph Olatt wrote: > On Thu, Dec 04, 2014 at 10:26:02PM +0200, Volodymyr Kostyrko wrote: >>>>> Anybody else on the list seeing anything similar? >>>>> >>>> >>>> Me. I have a derelict mother on VIA KT600 chipset with some memory >>>> problems. Sometimes it faults. Sometimes it tries to kill fs. Most >>>> times running compilation again works. >>>> >>>> Does it always breaks on the same command with the same output? >>> >>> >>> Yes. Ran it twice and both times it stopped at the same place with the >>> same error. >> >> So this has nothing to do with bad memory. Try building >> WITH_CLANG_IS_CC or even WITHOUT_GCC. Those should be added to the >> /etc/src.conf: >> >> WITH_CLANG_IS_CC=yes >> WITHOUT_GCC=yes >> >> Meanwhile, can you name your processor or list what is in your >> /etc/make.conf? > > I think you are correct here. I wondered why GCC was being invoked. > Unfortunately, I'm unable to test your suggestion. I've put another hard > disk in system, installed 10.1-RELEASE and updated the sources to > 10-STABLE and am currently building world without any issues. Good luck then. :) > /etc/make.conf was completely empty (I had checked that). > > The processor is: i386 (an old Dell Inspiron 8200! FreeBSD allows > these old laptops to continue to live and be of service...) The question is rather about processor type. GCC is famous for incorrectly generating code for some old chips assuming SSE2 support for ones that can only do SSE (like some Athlons). -- Sphinx of black quartz judge my vow. From owner-freebsd-stable@FreeBSD.ORG Fri Dec 5 00:23:36 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4A7BBFAC for ; Fri, 5 Dec 2014 00:23:36 +0000 (UTC) Received: from mail-pa0-x235.google.com (mail-pa0-x235.google.com [IPv6:2607:f8b0:400e:c03::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 16EB6E62 for ; Fri, 5 Dec 2014 00:23:36 +0000 (UTC) Received: by mail-pa0-f53.google.com with SMTP id kq14so18743985pab.26 for ; Thu, 04 Dec 2014 16:23:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:subject:message-id:date:to:mime-version; bh=PI3r+ki9iunJyuaKwU8VWGSFZ1igYyiU074xi9BqxcY=; b=V4R+saRROuC6pMGjlzYgHB5caZ/vMYLIkJbnJeCd+n5O54oWYVVokTaMqdEvBXoR82 dtnZ5Ir1CspcoC7O9bCewpugD0ComyUovk4ZU0S/KDV9GO7Nt6klyWCnZZab9YzJyRga uNAHRD0p/k9OPYQ8yetXm8j2vbZh55Z9DJ89JPY8VGLFEbYCjBQNESQwZUwJdYMfy/b8 +bWq+yv68g4r8V/UMQcSEAKiPbCvIS6KorEq+Cr1exBmmFZXL83FTyqbM/Aede69ULBV Eun6jptKGrCeWfw7dUivCqZ0PB9aHnmpzUV/+8U8jDLnV9PN/fhtS0Zc8drvocl6xMaj cUWw== X-Received: by 10.68.201.226 with SMTP id kd2mr29997549pbc.75.1417739015625; Thu, 04 Dec 2014 16:23:35 -0800 (PST) Received: from [10.51.2.189] ([199.101.130.202]) by mx.google.com with ESMTPSA id a13sm24502340pdm.44.2014.12.04.16.23.33 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 04 Dec 2014 16:23:34 -0800 (PST) From: George Kola Subject: Freed UMA keg Lost pages of memory Message-Id: <34C30B88-EB9C-4AF6-B986-257170604F1C@gmail.com> Date: Thu, 4 Dec 2014 16:23:33 -0800 To: freebsd-stable@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) X-Mailer: Apple Mail (2.1993) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Dec 2014 00:23:36 -0000 We are running FreeBSD 10.1 and we had 4 1 TB SSDs in L2ARC which we = removed and made into a separate zpool.=20 I ran sysctl and noticed a strange message showing this lost memory. I have pasted output of sysctl -a |grep UMA. Any idea why this is = happening ? Any fixes or suggested solution ? hosts (1/10): sjc1-prod1-01.voxer.com Freed UMA keg (zio_data_buf_1024) was not empty (333 items). Lost 171 = pages of memory. Freed UMA keg (zio_data_buf_1536) was not empty (138 items). Lost 583 = pages of memory. Freed UMA keg (zio_data_buf_2048) was not empty (84 items). Lost 148 = pages of memory. Freed UMA keg (zio_data_buf_1024) was not empty (380 items). Lost 175 = pages of memory. Freed UMA keg (zio_data_buf_1536) was not empty (154 items). Lost 328 = pages of memory. Freed UMA keg (zio_data_buf_2048) was not empty (67 items). Lost 91 = pages of memory. Freed UMA keg (zio_data_buf_1024) was not empty (256 items). Lost 95 = pages of memory. Freed UMA keg (zio_data_buf_1536) was not empty (170 items). Lost 383 = pages of memory. Freed UMA keg (zio_data_buf_2048) was not empty (117 items). Lost 257 = pages of memory. hosts (1/10): sjc1-prod1-02.voxer.com Freed UMA keg (zio_data_buf_1024) was not empty (336 items). Lost 175 = pages of memory. Freed UMA keg (zio_data_buf_1536) was not empty (157 items). Lost 638 = pages of memory. Freed UMA keg (zio_data_buf_2048) was not empty (83 items). Lost 150 = pages of memory. Freed UMA keg (zio_data_buf_1024) was not empty (329 items). Lost 140 = pages of memory. Freed UMA keg (zio_data_buf_1536) was not empty (216 items). Lost 425 = pages of memory. Freed UMA keg (zio_data_buf_2048) was not empty (85 items). Lost 130 = pages of memory. Freed UMA keg (zio_data_buf_1024) was not empty (437 items). Lost 173 = pages of memory. Freed UMA keg (zio_data_buf_1536) was not empty (165 items). Lost 576 = pages of memory. Freed UMA keg (zio_data_buf_2048) was not empty (103 items). Lost 273 = pages of memory. Thanks, George From owner-freebsd-stable@FreeBSD.ORG Fri Dec 5 00:34:10 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 254684DD for ; Fri, 5 Dec 2014 00:34:10 +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 0D041F72 for ; Fri, 5 Dec 2014 00:34:09 +0000 (UTC) Received: from zeta.ixsystems.com (unknown [12.229.62.2]) (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 A05DF1A5C1; Thu, 4 Dec 2014 16:34:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=delphij.net; s=anubis; t=1417739649; x=1417754049; bh=yuJIjB2Cp40XfiOnQci+mWlF9QfzQtr+55o3Sx3dq8o=; h=Date:From:Reply-To:To:Subject:References:In-Reply-To; b=f3ymVL9OzOeC2wrjLt0Xb/S6tXlGYtLmAwkEIG7IE2hXxtgFSVSIMe/zEwNlHOuRl BJM5JgADVs4XL4tI4YtdoeinbENYWb/umqaYPsSZVrgd8Di9fPkxSdSzUrTDJNbzpb c2cHUf7aAI/Jd1PuU97zigwcg4iSAqij5proaX2U= Message-ID: <5480FD81.9060203@delphij.net> Date: Thu, 04 Dec 2014 16:34:09 -0800 From: Xin Li Reply-To: d@delphij.net Organization: The FreeBSD Project MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: Freed UMA keg Lost pages of memory References: <34C30B88-EB9C-4AF6-B986-257170604F1C@gmail.com> In-Reply-To: <34C30B88-EB9C-4AF6-B986-257170604F1C@gmail.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Dec 2014 00:34:10 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 12/04/14 16:23, George Kola wrote: > We are running FreeBSD 10.1 and we had 4 1 TB SSDs in L2ARC which > we removed and made into a separate zpool. I ran sysctl and noticed > a strange message showing this lost memory. I have pasted output of > sysctl -a |grep UMA. Any idea why this is happening ? Any fixes or > suggested solution ? This may be fixed by r275492 of stable/10. There is a known memory leak in L2ARC code when compression is used. Cheers, - -- Xin LI https://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.1.0 (FreeBSD) iQIcBAEBCgAGBQJUgP19AAoJEJW2GBstM+nsLm4P/RlU/MaNdaUjO447/Anw/5Ok 3GKjVfFP8RbOyO7LyG6lMSOhXS2OWLqFXwLBthF3ISdOKT7pbJLw0Dus6FEJAAYh tU7eIWBsLfiEaloxQmC8J3AutFLRFYkY01Vq3Vh4zeLJoYfbOvSA8Z7d/KYgDOiw Kkjs8uROf7+Op3zx26C4mdryw8D8yxyq6kmbuJwQ6VofblqFu2UtGt5lpXuuJLLh OfixO+mg61hy8hNRLsEZCirSOAWatplha0rdu15Gi/wr/mCSWvi22u/IZ7mmp5di aIouGy/1g6VXoINFpGEHmFX395/NE4bPep3sDhy/TEI8S2hPxJf0bXy99SzRTbiy YPMH1rxougcQXjP27gu2nC6IAWNFQiTJo6h6cV+2XReeMC21IeEaz+yrvWV64AJ1 iNGHTS+RKtgrTjNdYsGdX1OQ+H+s0p4BUf/8MSyhakSJzCJS8wnhet4Qj2+YpfwX SJtG5Ox7TKTJSfmMRJh95aP1uS3I75xNmCmbLrmQ0ytFfjoD4jjz908gc/zwyb3t /pWlzdqLS1Paw8cn+yryrc4uMd0MRGnyOHMKL1Ut00VFjtUrFXhuqkdjDBBBtzzM kHINlkCQ7cfCBnA6T6RvobGZ2MdGNgXnAiahLOtXqTBK3W4Btfqd5JX8WfVlXtwL ONzglteBql7rQZWpEm/x =qzsA -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Fri Dec 5 07:51:13 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 619203B5 for ; Fri, 5 Dec 2014 07:51:13 +0000 (UTC) Received: from mail3.transactionware.com (mail.transactionware.com [203.14.245.7]) by mx1.freebsd.org (Postfix) with SMTP id BD9D192 for ; Fri, 5 Dec 2014 07:51:11 +0000 (UTC) Received: (qmail 26644 invoked by uid 907); 5 Dec 2014 07:44:28 -0000 Received: from Unknown (HELO jmmacpro.tmst.com.au) (203.14.245.130) (smtp-auth username janm, mechanism plain) by mail3.transactionware.com (qpsmtpd/0.84) with (DHE-RSA-AES256-SHA encrypted) ESMTPSA; Fri, 05 Dec 2014 18:44:28 +1100 From: Jan Mikkelsen Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: 10.1 regression: process using serial port becomes unkillable when no modem control signals Message-Id: Date: Fri, 5 Dec 2014 18:44:51 +1100 To: FreeBSD Stable Mailing List Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) X-Mailer: Apple Mail (2.1993) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Dec 2014 07:51:13 -0000 Hi, I have just found this problem on a machine upgraded to 10.1. When running mgetty on a serial port with nothing connected and then = killing it the process becomes unkillable. This prevents =E2=80=9Cshutdown= -r=E2=80=9D from completing, which is particularly annoying. Giving the serial port a device which provides the right modem control = signals lets the process exit immediately. The same hardware with 9.3 = was fine. Below is the kernel stack trace on the unkillable process. Does this ring any bells for anyone? Thanks, Jan Mikkelsen (kgdb) bt #0 sched_switch (td=3D0xfffff80236e1a920, newtd=3D, flags=3D) at = /usr/home/janm/p4/freebsd-image-std-2014.2/FreeBSD/src/sys/kern/sched_ule.= c:1945 #1 0xffffffff80939ba1 in mi_switch (flags=3D260, newtd=3D0x0) at = /usr/home/janm/p4/freebsd-image-std-2014.2/FreeBSD/src/sys/kern/kern_synch= .c:494 #2 0xffffffff80976d6b in sleepq_catch_signals = (wchan=3D0xfffff8000c7344b8, pri=3D0) at = /usr/home/janm/p4/freebsd-image-std-2014.2/FreeBSD/src/sys/kern/subr_sleep= queue.c:426 #3 0xffffffff80976c1f in sleepq_wait_sig (wchan=3D0x0, pri=3D0) at = /usr/home/janm/p4/freebsd-image-std-2014.2/FreeBSD/src/sys/kern/subr_sleep= queue.c:631 #4 0xffffffff808e345a in _cv_wait_sig (cvp=3D0xfffff8000c7344b8, = lock=3D0xfffff8000c734408) at = /usr/home/janm/p4/freebsd-image-std-2014.2/FreeBSD/src/sys/kern/kern_condv= ar.c:258 #5 0xffffffff809957a5 in ttydev_leave (tp=3D0xfffff8000c734400) at = /usr/home/janm/p4/freebsd-image-std-2014.2/FreeBSD/src/sys/kern/tty.c:1392= #6 0xffffffff80994d30 in ttydev_close (dev=3D, = fflag=3D0, devtype=3D0, td=3D0x0) at = /usr/home/janm/p4/freebsd-image-std-2014.2/FreeBSD/src/sys/kern/tty.c:353 #7 0xffffffff8081ec63 in devfs_close (ap=3D0xfffffe0c541d57e0) at = /usr/home/janm/p4/freebsd-image-std-2014.2/FreeBSD/src/sys/fs/devfs/devfs_= vnops.c:592 #8 0xffffffff80e6d281 in VOP_CLOSE_APV (vop=3D, = a=3D) at vnode_if.c:535 #9 0xffffffff809df673 in vn_close (vp=3D0xfffff80236a6f588, flags=3D3, = file_cred=3D0xfffff806a300b200, td=3D0xfffff80236e1a920) at = vnode_if.h:225 #10 0xffffffff809de4c8 in vn_closefile (fp=3D0xfffff8001243d9b0, = td=3D0xfffff80236e1a920) at = /usr/home/janm/p4/freebsd-image-std-2014.2/FreeBSD/src/sys/kern/vfs_vnops.= c:1557 #11 0xffffffff808204bc in devfs_close_f (fp=3D0xfffff8001243d9b0, = td=3D0x0) at = /usr/home/janm/p4/freebsd-image-std-2014.2/FreeBSD/src/sys/fs/devfs/devfs_= vnops.c:611 #12 0xffffffff808ed249 in _fdrop (fp=3D0xfffff8001243d9b0, td=3D0x0) at = file.h:343 #13 0xffffffff808ef9ae in closef (fp=3D, td=3D) at = /usr/home/janm/p4/freebsd-image-std-2014.2/FreeBSD/src/sys/kern/kern_descr= ip.c:2335 #14 0xffffffff808ef5c9 in fdescfree (td=3D0xfffff80236e1a920) at = /usr/home/janm/p4/freebsd-image-std-2014.2/FreeBSD/src/sys/kern/kern_descr= ip.c:2103 #15 0xffffffff808fb8fb in exit1 (td=3D0xfffff80236e1a920, rv=3D) at = /usr/home/janm/p4/freebsd-image-std-2014.2/FreeBSD/src/sys/kern/kern_exit.= c:329 #16 0xffffffff808fb37e in sys_sys_exit (td=3D0x0, uap=3D) at = /usr/home/janm/p4/freebsd-image-std-2014.2/FreeBSD/src/sys/kern/kern_exit.= c:153 #17 0xffffffff80d4f521 in amd64_syscall (td=3D0xfffff80236e1a920, = traced=3D0) at subr_syscall.c:134 From owner-freebsd-stable@FreeBSD.ORG Fri Dec 5 09:57:13 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AE3E63D3; Fri, 5 Dec 2014 09:57:13 +0000 (UTC) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (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 38776A9; Fri, 5 Dec 2014 09:57:13 +0000 (UTC) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.14.9/8.14.9) with ESMTP id sB59v2T1017850 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 5 Dec 2014 11:57:02 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.9.2 kib.kiev.ua sB59v2T1017850 Received: (from kostik@localhost) by tom.home (8.14.9/8.14.9/Submit) id sB59v0nZ017849; Fri, 5 Dec 2014 11:57:00 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Fri, 5 Dec 2014 11:57:00 +0200 From: Konstantin Belousov To: Jan Mikkelsen Subject: Re: 10.1 regression: process using serial port becomes unkillable when no modem control signals Message-ID: <20141205095659.GF97072@kib.kiev.ua> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.0 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on tom.home Cc: marcel@freebsd.org, FreeBSD Stable Mailing List X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Dec 2014 09:57:13 -0000 On Fri, Dec 05, 2014 at 06:44:51PM +1100, Jan Mikkelsen wrote: > Hi, > > I have just found this problem on a machine upgraded to 10.1. > > When running mgetty on a serial port with nothing connected and then killing it the process becomes unkillable. This prevents ???shutdown -r??? from completing, which is particularly annoying. > > Giving the serial port a device which provides the right modem control signals lets the process exit immediately. The same hardware with 9.3 was fine. > > Below is the kernel stack trace on the unkillable process. > > Does this ring any bells for anyone? This sounds as something that might be fixed by r272786 and r272789 in HEAD. I did not looked into details too close. The changes are not in stable/10, apply manually and test. > > Thanks, > > Jan Mikkelsen > > (kgdb) bt > #0 sched_switch (td=0xfffff80236e1a920, newtd=, flags=) at /usr/home/janm/p4/freebsd-image-std-2014.2/FreeBSD/src/sys/kern/sched_ule.c:1945 > #1 0xffffffff80939ba1 in mi_switch (flags=260, newtd=0x0) at /usr/home/janm/p4/freebsd-image-std-2014.2/FreeBSD/src/sys/kern/kern_synch.c:494 > #2 0xffffffff80976d6b in sleepq_catch_signals (wchan=0xfffff8000c7344b8, pri=0) at /usr/home/janm/p4/freebsd-image-std-2014.2/FreeBSD/src/sys/kern/subr_sleepqueue.c:426 > #3 0xffffffff80976c1f in sleepq_wait_sig (wchan=0x0, pri=0) at /usr/home/janm/p4/freebsd-image-std-2014.2/FreeBSD/src/sys/kern/subr_sleepqueue.c:631 > #4 0xffffffff808e345a in _cv_wait_sig (cvp=0xfffff8000c7344b8, lock=0xfffff8000c734408) at /usr/home/janm/p4/freebsd-image-std-2014.2/FreeBSD/src/sys/kern/kern_condvar.c:258 > #5 0xffffffff809957a5 in ttydev_leave (tp=0xfffff8000c734400) at /usr/home/janm/p4/freebsd-image-std-2014.2/FreeBSD/src/sys/kern/tty.c:1392 > #6 0xffffffff80994d30 in ttydev_close (dev=, fflag=0, devtype=0, td=0x0) at /usr/home/janm/p4/freebsd-image-std-2014.2/FreeBSD/src/sys/kern/tty.c:353 > #7 0xffffffff8081ec63 in devfs_close (ap=0xfffffe0c541d57e0) at /usr/home/janm/p4/freebsd-image-std-2014.2/FreeBSD/src/sys/fs/devfs/devfs_vnops.c:592 > #8 0xffffffff80e6d281 in VOP_CLOSE_APV (vop=, a=) at vnode_if.c:535 > #9 0xffffffff809df673 in vn_close (vp=0xfffff80236a6f588, flags=3, file_cred=0xfffff806a300b200, td=0xfffff80236e1a920) at vnode_if.h:225 > #10 0xffffffff809de4c8 in vn_closefile (fp=0xfffff8001243d9b0, td=0xfffff80236e1a920) at /usr/home/janm/p4/freebsd-image-std-2014.2/FreeBSD/src/sys/kern/vfs_vnops.c:1557 > #11 0xffffffff808204bc in devfs_close_f (fp=0xfffff8001243d9b0, td=0x0) at /usr/home/janm/p4/freebsd-image-std-2014.2/FreeBSD/src/sys/fs/devfs/devfs_vnops.c:611 > #12 0xffffffff808ed249 in _fdrop (fp=0xfffff8001243d9b0, td=0x0) at file.h:343 > #13 0xffffffff808ef9ae in closef (fp=, td=) at /usr/home/janm/p4/freebsd-image-std-2014.2/FreeBSD/src/sys/kern/kern_descrip.c:2335 > #14 0xffffffff808ef5c9 in fdescfree (td=0xfffff80236e1a920) at /usr/home/janm/p4/freebsd-image-std-2014.2/FreeBSD/src/sys/kern/kern_descrip.c:2103 > #15 0xffffffff808fb8fb in exit1 (td=0xfffff80236e1a920, rv=) at /usr/home/janm/p4/freebsd-image-std-2014.2/FreeBSD/src/sys/kern/kern_exit.c:329 > #16 0xffffffff808fb37e in sys_sys_exit (td=0x0, uap=) at /usr/home/janm/p4/freebsd-image-std-2014.2/FreeBSD/src/sys/kern/kern_exit.c:153 > #17 0xffffffff80d4f521 in amd64_syscall (td=0xfffff80236e1a920, traced=0) at subr_syscall.c:134 > > > _______________________________________________ > 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-stable@FreeBSD.ORG Fri Dec 5 17:23:28 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0A124BB3 for ; Fri, 5 Dec 2014 17:23:28 +0000 (UTC) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id ECED9A7E for ; Fri, 5 Dec 2014 17:23:27 +0000 (UTC) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id 0BDAA95C for ; Fri, 5 Dec 2014 17:23:26 +0000 (UTC) Date: Fri, 5 Dec 2014 17:23:25 +0000 (GMT) From: jenkins-admin@freebsd.org To: freebsd-stable@freebsd.org Message-ID: <1545486089.6.1417800206014.JavaMail.jenkins@jenkins-9.freebsd.org> In-Reply-To: <1935080296.5.1417793502022.JavaMail.jenkins@jenkins-9.freebsd.org> References: <1935080296.5.1417793502022.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: Jenkins build is back to normal : Build-UFS-image #596 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Jenkins-Job: Build-UFS-image X-Jenkins-Result: SUCCESS X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Dec 2014 17:23:28 -0000 See From owner-freebsd-stable@FreeBSD.ORG Sat Dec 6 07:13:54 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 23C5A549 for ; Sat, 6 Dec 2014 07:13:54 +0000 (UTC) Received: from denrei.darkbsd.org (denrei.darkbsd.org [IPv6:2001:41d0:1:f442::1]) by mx1.freebsd.org (Postfix) with ESMTP id C8099C75 for ; Sat, 6 Dec 2014 07:13:53 +0000 (UTC) Received: from denrei.darkbsd.org (localhost [127.0.0.1]) by denrei.darkbsd.org (Postfix) with ESMTP id C246E9CB; Sat, 6 Dec 2014 08:13:35 +0100 (CET) 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=9CTGwIznJnztTI31POQGnlc+N5o=; b=g 4eLCM+vPAW/AVIA/oI1M9unKtzQ0097DdyLYAjgSkjFKmrWZ+3tvaCNqA1bXtHcI J2nikNltxjdcf/oTN0fOMLfjtRh5mEuk0Yj4PswM+tLWHoDM92y4MHN6Xz86ASMo kILXN2LoDrGnferuLRAfPxRX1JQVqye1aD+XJtcrbQ= 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=c0tPlocIhurRkQVOd8ub28yQBXm HY9Knu1FGXni2tovBKtVxobE0NaQl4FYsQETd+qQ0XimAR7bTZulxndzjOCcbVMD bAlZXsTTWjzFaAUTPFlyR3Dzm8+VNBMsB/UDLV5qj8bftq+FIXuBvhXRwCS5KKwA d+z4h77OnSN96r2k= 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=1417850005; bh=pOKefYclTHvTzuVFLM2aKCW du6kzmygG/lElxe/SisI=; b=gC5MQdBM/4uemtsNUry7zMO2Ex72NGwVaPGqS0x QZhRzqQ/vE6wByORT2gfI4weFJ+wA6kESZUGWUNlmV4ylYE8IQyyZm/HbG2p4aRK fyXUbUVUhA45NKfhVwtkf17HZXUO6hkfR2Nzy/4eyMDSe3DRK4UJXUcyvvYGuvGW Jsd0= 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 7iWUExSmbyr7; Sat, 6 Dec 2014 08:13:25 +0100 (CET) Received: from [192.168.3.42] (archer.yomi.darkbsd.org [192.168.3.42]) (Authenticated sender: darksoul@darkbsd.org) by denrei.darkbsd.org (Postfix) with ESMTPSA id 9196A9CA; Sat, 6 Dec 2014 08:13:23 +0100 (CET) Message-ID: <5482AC8E.4050408@darkbsd.org> Date: Sat, 06 Dec 2014 16:13:18 +0900 From: Stephane LAPIE User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: =?UTF-8?B?T2xpdmllciBDb2NoYXJkLUxhYmLDqQ==?= , Kai Gallasch Subject: Re: 10.1 RC4 r273903 - zpool scrub on ssd mirror - ahci command timeout References: <20141106003240.344dedf6@orwell> In-Reply-To: X-Enigmail-Version: 1.5.2 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="4ddGswSdwOtJkXiebcJUQTWE9VQVkCBVp" Cc: "freebsd-stable@freebsd.org Stable" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Dec 2014 07:13:54 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --4ddGswSdwOtJkXiebcJUQTWE9VQVkCBVp Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 11/24/2014 02:56 AM, Olivier Cochard-Labb=C3=A9 wrote: > On Thu, Nov 6, 2014 at 12:32 AM, Kai Gallasch wrote: > >> Hi. >> >> Not sure if this is 10.1 related or more a problem of the ssd >> model and/or ahci controller.. >> >> >> I find the following kernel message in the output of 'dmesg': (after >> running zpool scrub two times) >> >> >> ahcich2: Timeout on slot 15 port 0 >> ahcich2: is 00000000 cs 000f0000 ss 000f8000 rs 000f8000 tfd 40 serr >> 00000000 cmd 0024cf17 (ada2:ahcich2:0:0:0): READ_FPDMA_QUEUED. ACB: 60= >> 8b a6 1d 56 40 0d 00 00 00 00 00 (ada2:ahcich2:0:0:0): CAM status: >> Command timeout (ada2:ahcich2:0:0:0): Retrying command >> ahcich2: Timeout on slot 23 port 0 >> ahcich2: is 00000000 cs 0f000000 ss 0f800000 rs 0f800000 tfd 40 serr >> 00000000 cmd 0024d817 (ada2:ahcich2:0:0:0): READ_FPDMA_QUEUED. ACB: 60= >> 1b 23 81 bc 40 06 00 00 00 00 00 (ada2:ahcich2:0:0:0): CAM status: >> Command timeout (ada2:ahcich2:0:0:0): Retrying command >> ahcich2: Timeout on slot 3 port 0 >> ahcich2: is 00000000 cs 00000030 ss 00000038 rs 00000038 tfd 40 serr >> 00000000 cmd 0024c317 (ada2:ahcich2:0:0:0): READ_FPDMA_QUEUED. ACB: 60= >> 26 bd 18 8e 40 12 00 00 00 00 00 (ada2:ahcich2:0:0:0): CAM status: >> Command timeout (ada2:ahcich2:0:0:0): Retrying command >> >> > Hi, > > I meet the same "CAM status: Command timeout" problem since my upgrade = from > 10.0 to 10.1 on a HP ProLiant MicroServer (AMD SB7x0/SB8x0/SB9x0 SATA > Controller). A "zpool scrub" is a way for generating this error message= but > writting big files (few GB) is another way too. > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.or= g" Hi, I'm encountering something along those lines too, with Transcend SSDs on AHCI controllers. (Although the controllers are set and identified as ATA, because of option ROM clash on that system, which I should eventually get down to fixing...) I have two ZFS pools : - 15 disks on a LSI controller - 2 SSDs on the aformentioned Intel AHCI controller Ever since upgrading to 10.1-RELEASE, eventually, I will get a warning in dmesg on either of the two SSDs : ata0: already running! ata1: already running! Source code for ATA indicates that it is just reprocessing the same query= , and gstat indicates that operations are stuck in the I/O queue without ever being purged. Once it comes to that, the only way to (temporarily) recover is to reboot= =2E Cheers, --=20 Stephane LAPIE, EPITA SRS, Promo 2005 "Even when they have digital readouts, I can't understand them." --MegaTokyo --4ddGswSdwOtJkXiebcJUQTWE9VQVkCBVp 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/ iF4EAREIAAYFAlSCrI8ACgkQDJ4OK7D3FWT6UwEAgQihwGc5n1wc4mWlX2udDquN IR8qb0LjTR7+t/d8CkQA+wa1sOWh1MQlG+K0D8jppY84C4JS7myeb+IB6Urvz4lX =2tKv -----END PGP SIGNATURE----- --4ddGswSdwOtJkXiebcJUQTWE9VQVkCBVp-- From owner-freebsd-stable@FreeBSD.ORG Sat Dec 6 08:48:11 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A022ADCF for ; Sat, 6 Dec 2014 08:48:11 +0000 (UTC) Received: from smtp24.services.sfr.fr (smtp24.services.sfr.fr [93.17.128.81]) by mx1.freebsd.org (Postfix) with ESMTP id 617F35E4 for ; Sat, 6 Dec 2014 08:48:10 +0000 (UTC) Received: from filter.sfr.fr (localhost [93.4.34.137]) by msfrf2402.sfr.fr (SMTP Server) with ESMTP id 46C5F700006F for ; Sat, 6 Dec 2014 09:42:44 +0100 (CET) Authentication-Results: sfrmc.priv.atos.fr; dkim=none (no signature); dkim-adsp=none (no policy) header.from=listjm@club-internet.fr Received: from [192.168.1.67] (137.34.4.93.rev.sfr.net [93.4.34.137]) by msfrf2402.sfr.fr (SMTP Server) with ESMTP id 209067000057 for ; Sat, 6 Dec 2014 09:42:43 +0100 (CET) X-SFR-UUID: 20141206084244133.209067000057@msfrf2402.sfr.fr Message-ID: <5482C181.9090500@club-internet.fr> Date: Sat, 06 Dec 2014 09:42:41 +0100 From: Juan =?iso-8859-1?b?UmFt824=?= Molina Menor User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: System hang on shutdown when running freebsd-update Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Dec 2014 08:48:11 -0000 > Another update. I narrowed down the issue due to /sbin/init being replaced. This might be the magic that freebsd-update does to make the crash happen. (Although there might be more situations that cause a hang.) > > I can completely reliably trigger the hang on a default 10.1-RELEASE install on UFS2 in VMware Fusion with the following procedure: > > # chflags noschg /sbin/init > # cp -Rp /sbin/init /sbin/init2 > # rm -f /sbin/init > # mv /sbin/init2 /sbin/init > # chflags schg /sbin/init > # reboot > => Hang after "All buffers synced." These commands do not trigger the issue here on a 10.1-RELEASE on VMware Player, but do it in a real system with the same release, both i386. When I last freebsd-updated this latter machine from 10.0 to 10.1-RELEASE, I also remember seeing the hang on shutdown. Hope it helps, Juan From owner-freebsd-stable@FreeBSD.ORG Sat Dec 6 10:45:14 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E88C0786 for ; Sat, 6 Dec 2014 10:45:14 +0000 (UTC) Received: from mail.webmatic.de (mail.webmatic.de [212.78.101.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.webmatic.de", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AAE4E61 for ; Sat, 6 Dec 2014 10:45:14 +0000 (UTC) Received: from mail.webmatic.de (localhost [127.0.0.1]) by mail.webmatic.de (Postfix) with ESMTP id 2EB548A020 for ; Sat, 6 Dec 2014 11:35:29 +0100 (CET) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Sat, 06 Dec 2014 11:35:29 +0100 From: Thomas Krause To: freebsd-stable@freebsd.org Subject: freebsd-update 10.0 -> 10.1 segmentation fault (nsswitch.conf w mysql) Message-ID: <1d89bae75778743583265187bc41a4ca@chef-ingenieur.de> X-Sender: freebsd-stable@chef-ingenieur.de User-Agent: Roundcube Webmail/1.0.3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Dec 2014 10:45:15 -0000 Hi, binary update from Freebsd 10.0 to 10.1 Release fails after 1st reboot with 10.1 kernel and running # freebsd-update install Segmentation fault I found, removing the mysql entry from /etc/nsswitch.conf helps. But running # freebsd-update install again, I get "Segmentation fault" again - the "old" nsswitch.conf with mysql entries were installed. How can I fix that (where come the old nsswitch.conf from - a find / doesn't help). Regards, Thomas. From owner-freebsd-stable@FreeBSD.ORG Sat Dec 6 12:40:34 2014 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 92880D75; Sat, 6 Dec 2014 12:40:34 +0000 (UTC) Received: from mail-wi0-x235.google.com (mail-wi0-x235.google.com [IPv6:2a00:1450:400c: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 20D96C4D; Sat, 6 Dec 2014 12:40:34 +0000 (UTC) Received: by mail-wi0-f181.google.com with SMTP id r20so1034217wiv.8 for ; Sat, 06 Dec 2014 04:40:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:subject:message-id:mime-version:content-type :content-disposition:user-agent; bh=zK22sKWwksK5JBy6S2KDENSQHaV0xY6rTjJJf9Gm0ps=; b=wy+ZU9+Sk1lvpO5r8dHnk7CjdbyqiyAxIJa0WCzlQjg9AKWGWVgI8+sxKnZb/o20uI Up+CqqNGsbkYxq2a6FCyFlaJ7WlX7WDQyJnMHm353n/itusbs5Hsr6IR7Z/U2Jc8U/eo I7ZDL4zhJ/in66ULainjQ9qS3iXNOmBpvxkdj/PPUahxuppkA9sxVzXShAVWlDyboRJt JFdguSETzqDIQfu/KRY6GHI81Fyhr0iab9BYUdIjRQusPMEWCQu+SWerp2OjUSrXMHnl Ew8a/MOt3Ir0e8VbpKxqIqGhzrTG2E6DodNCh4mvYaUlXPBRlkLEdViHCpopMPbtdGnp pGtw== X-Received: by 10.180.75.199 with SMTP id e7mr11304762wiw.21.1417869632434; Sat, 06 Dec 2014 04:40:32 -0800 (PST) Received: from ivaldir.etoilebsd.net ([2001:41d0:8:db4c::1]) by mx.google.com with ESMTPSA id pu3sm48561842wjc.14.2014.12.06.04.40.31 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 06 Dec 2014 04:40:31 -0800 (PST) Sender: Baptiste Daroussin Date: Sat, 6 Dec 2014 13:40:29 +0100 From: Baptiste Daroussin To: ports@FreeBSD.org, current@FreeBSD.org, stable@FreeBSD.org Subject: [CFT] pkg 1.4.0 rc2 Message-ID: <20141206124029.GB72593@ivaldir.etoilebsd.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="bAmEntskrkuBymla" Content-Disposition: inline User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Dec 2014 12:40:34 -0000 --bAmEntskrkuBymla Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi, We have released a new 1.4.0 rc2 version of pkg (available in ports-mgmt/pkg-devel) since first beta it has received tons of bug fixes and should be now way more reliable and able to handle ootb without mistakes upgrades like the gettext one and the perl one. All reported issues should have been fixed since. Please test that new version I would like to make it the final release if possible. Best regards, Bapt --bAmEntskrkuBymla Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEABECAAYFAlSC+ToACgkQ8kTtMUmk6Ey21ACfQTvjGJUDlmk1vT97qesTfbEc pkUAoIuObxTvCc7sH91X2UU0UavytSkS =878W -----END PGP SIGNATURE----- --bAmEntskrkuBymla-- From owner-freebsd-stable@FreeBSD.ORG Sat Dec 6 13:11:14 2014 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 50BD342A for ; Sat, 6 Dec 2014 13:11:14 +0000 (UTC) Received: from nm50-vm2.bullet.mail.bf1.yahoo.com (nm50-vm2.bullet.mail.bf1.yahoo.com [216.109.115.221]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id ED143F71 for ; Sat, 6 Dec 2014 13:11:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1417871465; bh=ShWUmJdVgx/ISyaSur05cdQQfTq7MBcr0z/jx7JHBLs=; h=Date:From:To:Subject:References:In-Reply-To:From:Subject; b=jm9eFPLdcD+PVZtnlvlPGWBOpy8MAoyjzKKEck0LD8N3kYdQLzKFVYvCZgXgpHf3dfBzCXDpvqP0bESckhaOCj6HNoKYdAiytTR5020UBmOe6vNh/nvHZmwMlX2yWmrwdRODAZ2Lvl5U+aU7ZDsdprSDvXJNGjuw6jVB96bP5iBLkzKJVUSVHBj6JMKgI6TkS7GWYq7iw99+fiNoHxdayt82xM8ZakmpZyVP3b3Xgh3W667rmPSR1V1Thm5FWKWhP6FiEwYYnPTO6aHzs40Hj8dnfmHhuSmQGqOb4DPZ0L4JE5bEwn+FBannVUgUExdPnH9ion1dr26NaTYyi7jwog== DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s2048; d=yahoo.com; b=Djm38HZUTX1ATXY8xkqazRGtTH51CWan+osdFPPk2D5s1o8zvsUI6h4yzR4YoKZ7ceAbtx8g+Kd9229rVHAppYvO7sbTvMQTtOkvuohOv8Vnd6lHdtJcCNv3rS/iGkppTQSbdLH9I+KBLpW02a6AESEM5mL7Eqn+eVeDpEsWhbSEhJgYOHiKU95DnmH0j5y4wfMjJWDv/kcbb1mxz0/R23mbhMAXRWy9ndoHJhKjLQDs3MoYs7a3An3rFUVZKCKrBC6K8gVOB4WlL+wSoejbihEKf+7IQ16J1eR/jEFz7KWWlJgqy4UBBKvA+VtY/oZHTHgSueHr5JqfOmTpw69k8A==; Received: from [98.139.212.152] by nm50.bullet.mail.bf1.yahoo.com with NNFMP; 06 Dec 2014 13:11:05 -0000 Received: from [68.142.230.72] by tm9.bullet.mail.bf1.yahoo.com with NNFMP; 06 Dec 2014 13:11:05 -0000 Received: from [127.0.0.1] by smtp229.mail.bf1.yahoo.com with NNFMP; 06 Dec 2014 13:11:05 -0000 X-Yahoo-Newman-Id: 317868.64003.bm@smtp229.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: C7JKpXIVM1kGJKjTUNhsjY7xFzG7xlGVkvT1kNtECUAuFVF ooe6a528wbTbh1r3b5sH.nlzOg_vUC7lsWGIW29ZSH6jY0H2t2F0Kue6temn 082L4bFotkxVv7fUvBnJCZtZ8yBai5Jr4XF2SS9TSuzN5r75ZS1JsUK0BiZZ 28cU4X32ka3uxwCDAt08cRtTwxTxOM0HoXMXeyxmdNIDKRH80GogfWxyVcEr WEMV_W_WfLZ45k08R2aupyxogWRyNkJfcpUC1t_05P8J4VoQMR0xt2YBrucT 3Lq.AY988Im5lFW5wNgBEr5LO8odov5hBXYZUgJOlrWTOA9nm7JovcSUgzim 3e5ZhMVUB0iwMvpynwolM3ULj2E.IcIdmKDEc_bEp8KBAX84hJb6pZxVlkDz 4IZj4JIGPHZ3QrI64v2VdhfsyWiiHRsneJWkAjdsU90VpiOrL3NQ0AeslO8P 8wZO3Q_MX8OFBiXghhPaoBKPyiIi59ZEAOK4igZ89T_CvgK51KgSajTp8rc_ Y4hzkileXnqiqv8gmZx_XwPAa68yjnykQ X-Yahoo-SMTP: 6IZaPQyswBAeyzp3urHRlQfBxGxx4Js3YAIn Message-ID: <548300AC.6020801@yahoo.com> Date: Sat, 06 Dec 2014 05:12:12 -0800 From: Jeffrey Bouquet User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Baptiste Daroussin , ports@FreeBSD.org, current@FreeBSD.org, stable@FreeBSD.org Subject: Re: [CFT] pkg 1.4.0 rc2 References: <20141206124029.GB72593@ivaldir.etoilebsd.net> In-Reply-To: <20141206124029.GB72593@ivaldir.etoilebsd.net> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Dec 2014 13:11:14 -0000 On 12/06/14 04:40, Baptiste Daroussin wrote: > Hi, > > We have released a new 1.4.0 rc2 version of pkg (available in > ports-mgmt/pkg-devel) since first beta it has received tons of bug fixes and > should be now way more reliable and able to handle ootb without mistakes > upgrades like the gettext one and the perl one. > > All reported issues should have been fixed since. > > Please test that new version I would like to make it the final release if > possible. > > Best regards, > Bapt The upgrade of pkg-devel went slightly more without problems. Did not test a direct deinstall/reinstall though. OTOH "pkg install xorriso xombrero" still wants to remove w3m-img , install w3m, guile 1.8, x246, along with the reinstall of those two. For which I "n" and pkg delete xorriso xombrero cd ../cache/pkg pkg clean pkg install xorr[tab] xomb[tab] to complete and install manually Works, but a few more commands in the way. I seem to have no guile installed (was using v2 for mcron) and libx264 installed. Just ignoring guile for now probably. From owner-freebsd-stable@FreeBSD.ORG Sat Dec 6 13:16:18 2014 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EE4155EB; Sat, 6 Dec 2014 13:16:18 +0000 (UTC) Received: from mail-wi0-x22c.google.com (mail-wi0-x22c.google.com [IPv6:2a00:1450:400c:c05::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 8D552FA7; Sat, 6 Dec 2014 13:16:18 +0000 (UTC) Received: by mail-wi0-f172.google.com with SMTP id n3so1062887wiv.11 for ; Sat, 06 Dec 2014 05:16:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=ar17nIx9CS37qG585IFTllHvx4McDOv8g881cWDyL4Y=; b=lrYxaRbMcyyIAZoZUl8RJdqhYhrseyt/kA0frfrZV1Q4PEQPnsNPVH+aLEEPw0NhMP hxMpEDJwqbhPsXg1CoBzGduuAdY1c0NwwECKZjcV2Bf5KMfVw9dGpF9aZw8pQcDH9CpS SyrXBva3aG5tQcaC6nM0kmeeHwqIxEbFddJhyynJDCys+I/eEZ5rzTDAm1qWci0sCOqU 6xiMFqGnHfyQzdxConXmTaXcAmqADp29Gj2n7fFMgMOSATg5ErP+f+4ZR1mz5xaYEEVn Tws8yNvOywdo08+aCAlU/p76bCtrtXkllm4kpwzIVCm9dwUu6gvMFh6yVKlvQ7UMdaap rJKA== X-Received: by 10.194.92.176 with SMTP id cn16mr31360171wjb.62.1417871777103; Sat, 06 Dec 2014 05:16:17 -0800 (PST) Received: from ivaldir.etoilebsd.net ([2001:41d0:8:db4c::1]) by mx.google.com with ESMTPSA id wa5sm22900331wjc.8.2014.12.06.05.16.15 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 06 Dec 2014 05:16:15 -0800 (PST) Sender: Baptiste Daroussin Date: Sat, 6 Dec 2014 14:16:13 +0100 From: Baptiste Daroussin To: Jeffrey Bouquet Subject: Re: [CFT] pkg 1.4.0 rc2 Message-ID: <20141206131613.GD72593@ivaldir.etoilebsd.net> References: <20141206124029.GB72593@ivaldir.etoilebsd.net> <548300AC.6020801@yahoo.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="qOrJKOH36bD5yhNe" Content-Disposition: inline In-Reply-To: <548300AC.6020801@yahoo.com> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: ports@FreeBSD.org, stable@FreeBSD.org, current@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Dec 2014 13:16:19 -0000 --qOrJKOH36bD5yhNe Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Dec 06, 2014 at 05:12:12AM -0800, Jeffrey Bouquet wrote: >=20 > On 12/06/14 04:40, Baptiste Daroussin wrote: > > Hi, > > > > We have released a new 1.4.0 rc2 version of pkg (available in > > ports-mgmt/pkg-devel) since first beta it has received tons of bug fixe= s and > > should be now way more reliable and able to handle ootb without mistakes > > upgrades like the gettext one and the perl one. > > > > All reported issues should have been fixed since. > > > > Please test that new version I would like to make it the final release = if > > possible. > > > > Best regards, > > Bapt > The upgrade of pkg-devel went slightly more without problems. Did not te= st > a direct deinstall/reinstall though. >=20 > OTOH "pkg install xorriso xombrero" still wants to remove w3m-img , insta= ll > w3m, guile 1.8, x246, along with the reinstall of those two. >=20 > For which I "n" and > pkg delete xorriso xombrero > cd ../cache/pkg > pkg clean > pkg install xorr[tab] xomb[tab] to complete and install manually > Works, but a few more commands in the way. >=20 > I seem to have no guile installed (was using v2 for mcron) and libx264 > installed. > Just ignoring guile for now probably. Sounds like a port problem that pkg is showing I'll dig into it. regards, Bapt --qOrJKOH36bD5yhNe Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEABECAAYFAlSDAZ0ACgkQ8kTtMUmk6Ez7RQCfQ1KAs6w26Bg4f4UwIWu+hMO3 rBcAn3Rk6a5ENlVaOCuK2Ca5Eqndxpxt =kXoG -----END PGP SIGNATURE----- --qOrJKOH36bD5yhNe-- From owner-freebsd-stable@FreeBSD.ORG Sat Dec 6 13:30:38 2014 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 98CD4AFB; Sat, 6 Dec 2014 13:30:38 +0000 (UTC) Received: from mail-wg0-x22b.google.com (mail-wg0-x22b.google.com [IPv6:2a00:1450:400c:c00::22b]) (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 2BDF210D; Sat, 6 Dec 2014 13:30:38 +0000 (UTC) Received: by mail-wg0-f43.google.com with SMTP id l18so2994937wgh.2 for ; Sat, 06 Dec 2014 05:30:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=Gk8YehboyQpI/2hh91Ay08fNqNy36uXX9Ez65KYKAeI=; b=BKIcfQs788sQ4YhnIMl2J5CvMXnahUPv7D9o9vWMeM1Hn5hITlPYe+DpihgBEUVsgP X7u70VSAYsfuUrU7aYfXwgcVp8vEBITjpHdKLO8uyl02lL9VSMNT/yEmKnFkNjzpITTJ 0057e0zIFXRzAGmwEQJGiwlkVJknyhp2AMNsSYsHCzcsQwHuU5bebW8t3WHkiYSX/Grf a7dZrVdMm7C63iDm05XNI+b+tJ/OBhmraqkjmXBZwUYU/IDZuDfZOnYMXgnam7XH/JGv Cdsd9pvyGtao/eSmGdQqiEyoBPJ9khEsOETH740x3qG9Gqg/sMPYasIW5ndFvadDMYd4 uvdg== X-Received: by 10.194.249.70 with SMTP id ys6mr30937498wjc.61.1417872636666; Sat, 06 Dec 2014 05:30:36 -0800 (PST) Received: from ivaldir.etoilebsd.net ([2001:41d0:8:db4c::1]) by mx.google.com with ESMTPSA id jp3sm1906200wid.9.2014.12.06.05.30.35 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 06 Dec 2014 05:30:35 -0800 (PST) Sender: Baptiste Daroussin Date: Sat, 6 Dec 2014 14:30:33 +0100 From: Baptiste Daroussin To: Jeffrey Bouquet Subject: Re: [CFT] pkg 1.4.0 rc2 Message-ID: <20141206133033.GA94381@ivaldir.etoilebsd.net> References: <20141206124029.GB72593@ivaldir.etoilebsd.net> <548300AC.6020801@yahoo.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="vkogqOf2sHV7VnPd" Content-Disposition: inline In-Reply-To: <548300AC.6020801@yahoo.com> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: ports@FreeBSD.org, stable@FreeBSD.org, current@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Dec 2014 13:30:38 -0000 --vkogqOf2sHV7VnPd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Dec 06, 2014 at 05:12:12AM -0800, Jeffrey Bouquet wrote: >=20 > On 12/06/14 04:40, Baptiste Daroussin wrote: > > Hi, > > > > We have released a new 1.4.0 rc2 version of pkg (available in > > ports-mgmt/pkg-devel) since first beta it has received tons of bug fixe= s and > > should be now way more reliable and able to handle ootb without mistakes > > upgrades like the gettext one and the perl one. > > > > All reported issues should have been fixed since. > > > > Please test that new version I would like to make it the final release = if > > possible. > > > > Best regards, > > Bapt > The upgrade of pkg-devel went slightly more without problems. Did not te= st > a direct deinstall/reinstall though. >=20 > OTOH "pkg install xorriso xombrero" still wants to remove w3m-img , insta= ll > w3m, guile 1.8, x246, along with the reinstall of those two. Right so the is a problem in the way ports express dependencies and can onl= y be solved with some provides/requires we do not know yet how to express with t= he ports tree :( Regards, Bapt --vkogqOf2sHV7VnPd Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEABECAAYFAlSDBPcACgkQ8kTtMUmk6ExayACgsAgv+Jw4U1AMKj+HB/EIa3fh K1EAmwTRbycD+J8M1yQaL/Nd3k5rcGXD =RW/N -----END PGP SIGNATURE----- --vkogqOf2sHV7VnPd-- From owner-freebsd-stable@FreeBSD.ORG Sat Dec 6 19:31:50 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 365A1C62 for ; Sat, 6 Dec 2014 19:31:50 +0000 (UTC) Received: from mail-wi0-x22c.google.com (mail-wi0-x22c.google.com [IPv6:2a00:1450:400c:c05::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 BC507896 for ; Sat, 6 Dec 2014 19:31:49 +0000 (UTC) Received: by mail-wi0-f172.google.com with SMTP id n3so1524831wiv.11 for ; Sat, 06 Dec 2014 11:31:47 -0800 (PST) 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; bh=KKDHHh83BchgX8aOV6xXR7Yd3zzr/481jjPlvw9iVWQ=; b=cA73Znq++M2azX8hDMg4tK4eN9jMdKV0sRWzd8Q/vpS5jDTUP0r+vARIlJyYplJRBo 894RpWQrsbQhRUbJlJSlgcjSDb2YN3fIriMo/ve2NRzQQKZsbHtM3az0FTVkdpZBWnYF ELGn1gLyxXogtnLyHl3nv8LgSuNDGZkfX1WIo1Ior/M9QjUIFU8+9XZbsrDBOen1/U7g uQbsdFL22/bSsSkwo9bAFpOcYz6Gajp7kqZ+ZEQugRun5Pv834/w6BZn3N+uevNY91hc xRNWVURcwpdhcJxwDWkr2N0+CiBs5YQz2U50vDdDRAcK4/QmbqyTgmQWCe6elwMVPKYZ 1kVA== MIME-Version: 1.0 X-Received: by 10.194.172.72 with SMTP id ba8mr34380918wjc.13.1417894307700; Sat, 06 Dec 2014 11:31:47 -0800 (PST) Received: by 10.27.46.14 with HTTP; Sat, 6 Dec 2014 11:31:47 -0800 (PST) In-Reply-To: <1d89bae75778743583265187bc41a4ca@chef-ingenieur.de> References: <1d89bae75778743583265187bc41a4ca@chef-ingenieur.de> Date: Sat, 6 Dec 2014 13:31:47 -0600 Message-ID: Subject: Re: freebsd-update 10.0 -> 10.1 segmentation fault (nsswitch.conf w mysql) From: Scot Hetzel To: Thomas Krause Content-Type: text/plain; charset=ISO-8859-1 Cc: FreeBSD Stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Dec 2014 19:31:50 -0000 On Sat, Dec 6, 2014 at 4:35 AM, Thomas Krause wrote: > Hi, > binary update from Freebsd 10.0 to 10.1 Release fails after > 1st reboot with 10.1 kernel and running > > # freebsd-update install > Segmentation fault > > I found, removing the mysql entry from /etc/nsswitch.conf helps. > But running > > # freebsd-update install > > again, I get "Segmentation fault" again - the "old" nsswitch.conf > with mysql entries were installed. > > How can I fix that (where come the old nsswitch.conf from - a > find / doesn't help). > What port are you using to provide the MySQL support for nsswitch? I checked the net/libnss-mysql port, and it doesn't touch nsswitch.conf. Did you check your ${PREFIX}/etc/rc.d scripts to see if a script is modifying /etc/nsswitch.conf? -- DISCLAIMER: No electrons were maimed while sending this message. Only slightly bruised. From owner-freebsd-stable@FreeBSD.ORG Sat Dec 6 22:14:24 2014 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6400E9D8 for ; Sat, 6 Dec 2014 22:14:24 +0000 (UTC) Received: from smtp.digiware.nl (smtp.digiware.nl [31.223.170.169]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 215D3935 for ; Sat, 6 Dec 2014 22:14:23 +0000 (UTC) Received: from rack1.digiware.nl (unknown [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id C8DDF16A402 for ; Sat, 6 Dec 2014 23:14:14 +0100 (CET) X-Virus-Scanned: amavisd-new at digiware.nl Received: from smtp.digiware.nl ([127.0.0.1]) by rack1.digiware.nl (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qJJwTTDy3qEU; Sat, 6 Dec 2014 23:14:04 +0100 (CET) Received: from [192.168.10.9] (vaio [192.168.10.9]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.digiware.nl (Postfix) with ESMTPSA id AB54D16A401 for ; Sat, 6 Dec 2014 23:14:04 +0100 (CET) Message-ID: <54837FAC.801@digiware.nl> Date: Sat, 06 Dec 2014 23:14:04 +0100 From: Willem Jan Withagen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: "stable@freebsd.org" Subject: missing /usr/lib/libc_nonshared.a Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Dec 2014 22:14:24 -0000 Hi, Still trying to upgrade from 9.3 to 10.1, which seemed to get going. Completely started over again with cleaned out /etc/{make.src}.conf. Then build/installed 9.3 again which also included clang this time. but building the toolchain generates: -------------------------------------------------------------- >>> stage 2.3: build tools -------------------------------------------------------------- cd /usr/src10; MAKEOBJDIRPREFIX=/usr/obj INSTALL="sh /usr/src10/tools/install.sh" PATH=/usr/obj/usr/src10/tmp/legacy/usr/sbin:/usr/obj/usr/src10/tmp/legacy/usr/bin:/usr/obj/usr/src10/tmp/legacy/usr/games:/usr/obj/usr/src10/tmp/legacy/bin:/sbin:/bin:/usr/sbin:/usr/bin WORLDTMP=/usr/obj/usr/src10/tmp VERSION="FreeBSD 10.1-STABLE amd64 1001503" MAKEFLAGS="-m /usr/src10/tools/build/mk -m /usr/src10/share/mk" COMPILER_TYPE=gcc /usr/obj/usr/src10/make.amd64/bmake -f Makefile.inc1 TARGET=amd64 TARGET_ARCH=amd64 DESTDIR= BOOTSTRAPPING=903506 SSP_CFLAGS= -DNO_LINT -DNO_CPU_CFLAGS -DNO_WARNS -DNO_CTF -DEARLY_BUILD -DNO_TESTS build-tools ===> bin/csh (obj,build-tools) grep 'ERR_' /usr/src10/bin/csh/../../contrib/tcsh/sh.err.c | grep '^#define' >> sh.err.h cc -E -O2 -pipe -I. -I/usr/src10/bin/csh -I/usr/src10/bin/csh/../../contrib/tcsh -D_PATH_TCSHELL='"/bin/csh"' -std=gnu99 -I/usr/obj/usr/src10/tmp/legacy/usr/include /usr/src10/bin/csh/../../contrib/tcsh/tc.const.c /usr/src10/bin/csh/../../contrib/tcsh/sh.char.h /usr/src10/bin/csh/config.h /usr/src10/bin/csh/../../contrib/tcsh/config_f.h /usr/src10/bin/csh/../../contrib/tcsh/sh.types.h sh.err.h -D_h_tc_const | grep 'Char STR' | sed -e 's/Char \([a-zA-Z0-9_]*\)\(.*\)/extern Char \1[];/' | sort >> tc.const.h cc -o gethost -L/usr/obj/usr/src10/tmp/legacy/usr/lib -O2 -pipe -I. -I/usr/src10/bin/csh -I/usr/src10/bin/csh/../../contrib/tcsh -D_PATH_TCSHELL='"/bin/csh"' -std=gnu99 -I/usr/obj/usr/src10/tmp/legacy/usr/include /usr/src10/bin/csh/../../contrib/tcsh/gethost.c /usr/bin/ld: cannot find /usr/lib/libc_nonshared.a *** Error code 1 ----------------- Now I can fudge around this, by getting this lib from another 10.x system, but changes are that things are nog 100% compatible. So how do I get this lib first, before starting to build bin/csh. The other question is: why am I still using gcc for the toolchain even since I now have clang onboard? THanx, --WjW From owner-freebsd-stable@FreeBSD.ORG Sat Dec 6 22:35:31 2014 Return-Path: Delivered-To: stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1C296E7B; Sat, 6 Dec 2014 22:35:31 +0000 (UTC) Received: from smtp.digiware.nl (unknown [IPv6:2001:4cb8:90:ffff::3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D2C73AD1; Sat, 6 Dec 2014 22:35:30 +0000 (UTC) Received: from rack1.digiware.nl (unknown [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id 5DD6716A402; Sat, 6 Dec 2014 23:35:28 +0100 (CET) X-Virus-Scanned: amavisd-new at digiware.nl Received: from smtp.digiware.nl ([127.0.0.1]) by rack1.digiware.nl (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wIupouNghdtf; Sat, 6 Dec 2014 23:34:59 +0100 (CET) Received: from [192.168.10.9] (vaio [192.168.10.9]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.digiware.nl (Postfix) with ESMTPSA id 3DEC116A401; Sat, 6 Dec 2014 23:34:59 +0100 (CET) Message-ID: <54838493.5020603@digiware.nl> Date: Sat, 06 Dec 2014 23:34:59 +0100 From: Willem Jan Withagen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Baptiste Daroussin , ports@FreeBSD.org, current@FreeBSD.org, stable@FreeBSD.org Subject: Re: [CFT] pkg 1.4.0 rc2 References: <20141206124029.GB72593@ivaldir.etoilebsd.net> In-Reply-To: <20141206124029.GB72593@ivaldir.etoilebsd.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Dec 2014 22:35:31 -0000 On 6-12-2014 13:40, Baptiste Daroussin wrote: > Hi, > > We have released a new 1.4.0 rc2 version of pkg (available in > ports-mgmt/pkg-devel) since first beta it has received tons of bug fixes and > should be now way more reliable and able to handle ootb without mistakes > upgrades like the gettext one and the perl one. > > All reported issues should have been fixed since. > > Please test that new version I would like to make it the final release if > possible. I missed the previous announcement, but this is "bothering" me for some time already.... I'm using this simple cronic script to reduce traffic from scripts with nothing serious to report. But pkg still triggers: ----- # sudo cronic pkg audit -F Cronic detected failure or error output for the command: pkg audit -F RESULT CODE: 0 ERROR OUTPUT: pkg: vulnxml file up-to-date ------ And I wonder why this informational message is reported on STDERR, and other real problems on STDOUT... ------ sudo cronic pkg audit Cronic detected failure or error output for the command: pkg audit RESULT CODE: 1 ERROR OUTPUT: STANDARD OUTPUT: phpMyAdmin-4.2.13 is vulnerable: phpMyAdmin -- XSS and DoS vulnerabilities CVE: CVE-2014-9219 CVE: CVE-2014-9218 WWW: http://portaudit.FreeBSD.org/c9c46fbf-7b83-11e4-a96e-6805ca0b3d42.html 1 problem(s) in the installed packages found. ------ I would atleast to have case 1) also write to STDOUT. And perhaps have case 2) report on STDERR. --WjW