From owner-freebsd-sparc64@freebsd.org Sat Oct 17 19:46:41 2015 Return-Path: Delivered-To: freebsd-sparc64@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 B0565A17529 for ; Sat, 17 Oct 2015 19:46:41 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "gold.funkthat.com", Issuer "gold.funkthat.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 948EAEB for ; Sat, 17 Oct 2015 19:46:41 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (localhost [127.0.0.1]) by gold.funkthat.com (8.14.5/8.14.5) with ESMTP id t9HJkeQH066176 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 17 Oct 2015 12:46:40 -0700 (PDT) (envelope-from jmg@gold.funkthat.com) Received: (from jmg@localhost) by gold.funkthat.com (8.14.5/8.14.5/Submit) id t9HJkeuD066175; Sat, 17 Oct 2015 12:46:40 -0700 (PDT) (envelope-from jmg) Date: Sat, 17 Oct 2015 12:46:40 -0700 From: John-Mark Gurney To: Vasile Buruiana Cc: freebsd-sparc64@freebsd.org Subject: Re: UFS mount failure - disk slice created on and64, unable to mount on sparc64 Message-ID: <20151017194640.GA65715@funkthat.com> References: <20151017184425.GR67524@funkthat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 9.1-PRERELEASE amd64 X-PGP-Fingerprint: 54BA 873B 6515 3F10 9E88 9322 9CB1 8F74 6D3F A396 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-TipJar: bitcoin:13Qmb6AeTgQecazTWph4XasEsP7nGRbAPE X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? User-Agent: Mutt/1.5.21 (2010-09-15) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (gold.funkthat.com [127.0.0.1]); Sat, 17 Oct 2015 12:46:40 -0700 (PDT) X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Oct 2015 19:46:41 -0000 Vasile Buruiana wrote this message on Sat, Oct 17, 2015 at 22:38 +0300: > Yesm I played with a harddisk connected via IDE to the sun and later > to the laptop via USB-to-IDE adapter. Currently I'm trying to > buildworkd+buildkernel on the sun using some contents of the /usr/obj > cross-compiled on the amd-64 laptop to speed up the process (that's > how I found the problem), so I'm writing these from my memory: > > This happened on the SUN: > > gpart create -s mbr ada0 > gpart add -t freebsd ada0 > gpart create -s bsd ada0s1 > gpart add -s 1G -t freebsd-zfs ada0s1 > > newfs -U /dev/ada0s1 > > copy stuff, umount, invalid argument while attempting to mount on the laptop. Expected as the UFS file system is big endian, and tried to mount on a little endian machine.. > gpart create -s vtoc8 ada0 > gpart add -t freebsd ada0 > gpart create -s bsd da0s1 > gpart add -s 1G -t freebsd-zfs ada0s1 > newfs -U /dev/ada0s1 > > copy suff, unmount, again invalid argument while attempting to mount > on the laptop. same... > Same when creating on the laptop and mounting on the sun. > > When moving the harddisk from one unit to the other, at boot (or at > usb insert) the kernel reports: > g_dev_taste: make_dev_p() failed (gp->name=da0a, error=17) or ada0a Not sure about this.. asking on -current or -stable and -geom might get you more info on this.. > and many slices appear in /dev: > da0a > da0aa > da0ab > da0b > da0c > da0ca > da0cb > (or ada0s1a, ada0s1aa, ada0s1ab, ada0s1b, ada0s1bb, ada0s1c, ada0s1ca > on the sparc64....) > > and so on, same for mbr/vtoc8, same for bsd/zfs. > > These are some geom-relaed errors as I read on some other mailing > lists, so I tried to identify the problem by simplifying things until > I reduced everything to image file attached to md. > > The Sparc also ran a FreeBSD 6.1-release perfectly, the ufs mbr > partition could be mounted on a x86 for fsck or other maintenance with > absolutely no problems. Seems that the advances in technology are > still causing headaches in keeping the things simple. Hmm... Are you sure about this? iirc, there was a utility that you could run to switch the endianness of a UFS FS, could you have been using this utility? > I will try to makefs -B big on the amd64 but I doubt i will also be > able to mount it on the same machine. Correct, you will not be able to mount an FS created w/ -B big on the laptop as it will be the wrong endianness, but it will mount fine on the sparc64 system... > On 10/17/15, John-Mark Gurney wrote: > > Vasile Buruiana wrote this message on Sat, Oct 17, 2015 at 21:32 +0300: > >> Found a bug in FreeBSD 10.2. > >> An UFS disk slice created under sparc64 cannot be mounted under amd64. > >> And reverse: UFS disk slice created under amd64 cannot be mounted > >> under sparc64. This also happens with hard disks on both MBR and VTOC8 > >> partition schemes, on both UFS and ZFS filesystems. > > > > Sadly, this is due to the fact that sparc64 is big endian, and our UFS > > implementation isn't bi-endian... If you need to make a UFS file system > > on amd64 for use on sparc64, use the makefs utility w/ the option -B big > > to create it... > > > > Just ran into the same issue on an EdgeRouter Lite, which is a big > > endian MIPS64 machine... > > > > Though I'm a bit surprized that it happens w/ ZFS as ZFS is suppose > > to support either endianness automaticly.. Did you try this on raw > > disks? -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not."