Skip site navigation (1)Skip section navigation (2) 
Date:      Fri, 8 Feb 2013 12:30:51 GMT
From:      Anton Shterenlikht <mexas@bristol.ac.uk>
To:        kostikbel@gmail.com, mexas@bristol.ac.uk
Cc:        freebsd-questions@freebsd.org, freebsd-sparc64@freebsd.org
Subject:   Re: mount: /dev/da0p1: Invalid argument
Message-ID:  <201302081230.r18CUpkL034751@mech-cluster241.men.bris.ac.uk>
In-Reply-To: <20130208121432.GV2522@kib.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help 
	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?

In the end I burned a CD with the files in question,
but it's a bit of a waste, as I only need to
move over several KB of data (wireless setup).

Thanks

Anton

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201302081230.r18CUpkL034751>