From owner-freebsd-questions@FreeBSD.ORG Fri Feb 8 12:45:20 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 3ABB59B3; Fri, 8 Feb 2013 12:45:20 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (alchemy.franken.de [194.94.249.214]) by mx1.freebsd.org (Postfix) with ESMTP id A11BF293; Fri, 8 Feb 2013 12:45:19 +0000 (UTC) Received: from alchemy.franken.de (localhost [127.0.0.1]) by alchemy.franken.de (8.14.5/8.14.5/ALCHEMY.FRANKEN.DE) with ESMTP id r18CjAG5075962; Fri, 8 Feb 2013 13:45:10 +0100 (CET) (envelope-from marius@alchemy.franken.de) Received: (from marius@localhost) by alchemy.franken.de (8.14.5/8.14.5/Submit) id r18CjA8q075961; Fri, 8 Feb 2013 13:45:10 +0100 (CET) (envelope-from marius) Date: Fri, 8 Feb 2013 13:45:10 +0100 From: Marius Strobl To: Anton Shterenlikht Subject: Re: mount: /dev/da0p1: Invalid argument Message-ID: <20130208124510.GA75868@alchemy.franken.de> References: <20130208121432.GV2522@kib.kiev.ua> <201302081230.r18CUpkL034751@mech-cluster241.men.bris.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201302081230.r18CUpkL034751@mech-cluster241.men.bris.ac.uk> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: kostikbel@gmail.com, freebsd-questions@freebsd.org, freebsd-sparc64@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Feb 2013 12:45:20 -0000 On Fri, Feb 08, 2013 at 12:30:51PM +0000, Anton Shterenlikht wrote: > From kostikbel@gmail.com Fri Feb 8 12:25:21 2013 > > On Fri, Feb 08, 2013 at 12:01:41PM +0000, Anton Shterenlikht wrote: > > I need to transfer some files from sparc64 -current > > box onto amd64 9.1-RELEASE laptop. > > The amd64 laptop has no network connection yet, > > so I'm trying to achive this with a USB flash drive.=20 > >=20 > > The problem is that I always end up with > >=20 > > # mount /dev/da0p1 /mnt/ > > mount: /dev/da0p1: Invalid argument > > #=20 > >=20 > > If I do newfs on the sparc64 box, then I can't > > mount it on the amd64 box, and vice versa. > >=20 > > I tried just "newfs /dev/da0", and using gpart, > > e.g.: > >=20 > > # gpart show /dev/da0 > > =3D> 34 4029373 da0 GPT (1.9G) > > 34 2048 1 freebsd-ufs (1.0M) > > 2082 4027325 - free - (1.9G) > >=20 > > # > >=20 > > and then "newfs /dev/da0p1", or similar, > > but no luck. > >=20 > > I tried sparc64 VTOC8 partition scheme too - no help. > >=20 > > I can mount the device and use it as expected, > > i.e. copy files to/from it on either box, but > > the other box doesn't seem to understand the file > > system. > >=20 > > I tried loading various modules in desperation, > > e.g. on the sparc64 side: > >=20 > > # kldstat=20 > > Id Refs Address Size Name > > 1 9 0xc0000000 a80e58 kernel > > 2 1 0x101bca000 104000 geom_part_mbr.ko > > 3 1 0x101cce000 110000 geom_label.ko > > 4 1 0x101dde000 108000 geom_part_gpt.ko > > #=20 > >=20 > > but still no use.=20 > >=20 > > Am I missing something simple? > > UFS on FreeBSD is not endian-agnostic. It uses the host byte order > for multibyte values. > > As result, you can share UFS volumes only between hosts with the same > endianess, like i386/amd64/ia64 little endian or sparc64/mips big endian. > AFAIK, NetBSD has such support. > > Wow... I didn't realise that. > I thought UFS (1 or 2) takes all care > of endian-ness. Do you mean that even > I had say a SCSI internal disk with UFS2, > I couldn't move it between a little and > a big endian freebsd boxes? > > So what is the advice for transferring data > via USB in such cases? Any other gpart partition > I could use? > FAT should work and ZFS is also endian-agnostic. I don't know how well these code paths of the latter are tested though and we seem to have grown bugs in this regard at least in the area of intra- ZFS-version compatibility (which due to lack of understanding of the ZFS internals I'm not able to fix) since the split from (Open) Solaris. Marius