From owner-freebsd-arm@freebsd.org  Thu Jul 14 00:14:01 2016
Return-Path: <owner-freebsd-arm@freebsd.org>
Delivered-To: freebsd-arm@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 740E7B98881
 for <freebsd-arm@mailman.ysv.freebsd.org>;
 Thu, 14 Jul 2016 00:14:01 +0000 (UTC)
 (envelope-from paul@gromit.dlib.vt.edu)
Received: from gromit.dlib.vt.edu (gromit.dlib.vt.edu [128.173.126.120])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "gromit.dlib.vt.edu",
 Issuer "Chumby Certificate Authority" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id 5128312DE
 for <freebsd-arm@freebsd.org>; Thu, 14 Jul 2016 00:14:01 +0000 (UTC)
 (envelope-from paul@gromit.dlib.vt.edu)
Received: from mather.chumby.lan (c-71-63-91-41.hsd1.va.comcast.net
 [71.63.91.41])
 (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by gromit.dlib.vt.edu (Postfix) with ESMTPSA id 29970A1C;
 Wed, 13 Jul 2016 20:14:00 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: Bizarre clone attempt failures on Raspberry Pi2...
From: Paul Mather <paul@gromit.dlib.vt.edu>
In-Reply-To: <d2eb4035-e494-1a7b-98e5-2aa87efe0763@denninger.net>
Date: Wed, 13 Jul 2016 20:13:59 -0400
Cc: freebsd-arm@freebsd.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <EDE65B12-4961-4CEF-8AE9-BFDA4FD508A5@gromit.dlib.vt.edu>
References: <548783e1-9047-68f7-5f50-449db684d602@denninger.net>
 <d2eb4035-e494-1a7b-98e5-2aa87efe0763@denninger.net>
To: Karl Denninger <karl@denninger.net>
X-Mailer: Apple Mail (2.3124)
X-BeenThere: freebsd-arm@freebsd.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Porting FreeBSD to ARM processors." <freebsd-arm.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arm/>
List-Post: <mailto:freebsd-arm@freebsd.org>
List-Help: <mailto:freebsd-arm-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jul 2016 00:14:01 -0000


> On Jul 13, 2016, at 3:54 PM, Karl Denninger <karl@denninger.net> =
wrote:
>=20
> Oh, there is one difference:
>=20
> tunefs -p on the new device *works* (no idea why however since there's
> no slice there) where it FAILS on the original:
>=20
> root@Test-MCP:/home/karl # tunefs -p /dev/mmcsd0s2


Shouldn't this be /dev/mmcsd0s2a?  You're referencing the entire BSD =
slice in the above command, not the UFS partition upon which the rootfs =
lives.


> tunefs: /dev/mmcsd0s2: could not read superblock to fill out disk
>=20
> root@Test-MCP:/home/karl # tunefs -p /dev/da0s2
> tunefs: POSIX.1e ACLs: (-a)                                disabled
> tunefs: NFSv4 ACLs: (-N)                                   disabled
> tunefs: MAC multilabel: (-l)                               disabled
> tunefs: soft updates: (-n)                                 enabled
> tunefs: soft update journaling: (-j)                       disabled
> tunefs: gjournal: (-J)                                     disabled
> tunefs: trim: (-t)                                         disabled
> tunefs: maximum blocks per file in a cylinder group: (-e)  4096
> tunefs: average file size: (-f)                            16384
> tunefs: average number of files in a directory: (-s)       64
> tunefs: minimum percentage of free space: (-m)             8%
> tunefs: space to hold for metadata blocks: (-k)            6408
> tunefs: optimization preference: (-o)                      time
> tunefs: volume label: (-L)                                 rootfs

Cheers,

Paul.=