Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 8 Feb 2013 14:14:32 +0200
From:      Konstantin Belousov <kostikbel@gmail.com>
To:        Anton Shterenlikht <mexas@bristol.ac.uk>
Cc:        freebsd-questions@freebsd.org, freebsd-sparc64@freebsd.org
Subject:   Re: mount: /dev/da0p1: Invalid argument
Message-ID:  <20130208121432.GV2522@kib.kiev.ua>
In-Reply-To: <201302081201.r18C1fuK034685@mech-cluster241.men.bris.ac.uk>
References:  <201302081201.r18C1fuK034685@mech-cluster241.men.bris.ac.uk>

next in thread | previous in thread | raw e-mail | index | archive | help

--4PjXPRN4SCmYnrHw
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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.

--4PjXPRN4SCmYnrHw
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (FreeBSD)

iQIcBAEBAgAGBQJRFOwoAAoJEJDCuSvBvK1BoTAP/ittIZAN06eVRcXoQo7TD9yu
R5WU+ihk9/nCNBsAsXWvMBnBpn9C59A4vUeHXDiVluX4Rgk9xtjvNGdn9I4eJ3gw
kDxHm+U9Jo+IaAmenN5Z1FTMQJV+jX2FczZXwztXP2RkPPCtK6BxYV5MmVrFDCNE
1W8CJjtcOzC3WB4d5t9M5+G2kpY7DqqjtMkam/6xI3YH7eKkxJAsZCDAv1/Nis7d
AjomDVglxiuLzlMwcVfg/D7opt9Lp+kcu0nUOY6xSzlnA3szoflXvYQ2m0xodoqb
X95oBCD+F7cFxug6/B6Oaxi+G9gbgQMGA/p7Mxfvm0LKzn7YoiksUxLVM+Pit84q
Ka/k+pwv4RjwAtuByOkdZvtX3H+WXvIdoi08oX5pr4MChnxR0U+j+Uw1PfScZx/a
pGokWLcWwbYLfyqx96XUz6odpGRHG6KAA4HExYqPIHPbPoXIrxBMEEsMy0M4yFhM
bL59W6fDlD5SBx4Tv1gx+Ai0izpJ3PziRAiyItb0YuHGi/KzDkQe/svLq2w36gAL
mFxoTbTsLDZfVL55vVzCuuvfActBvQDOQbiBOu2iDOZzqvZZIIVNiWrJFYyre98x
r9kBjsxz03OuTqm8CMgF2i93VXqNav09VS2Vlu/TgfRFWVCSYYaCT7pKU6jTPYXR
a9W3ki7Qp4+28ajQsV2H
=1kUB
-----END PGP SIGNATURE-----

--4PjXPRN4SCmYnrHw--



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