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

Andy Ruhl <acruhl@gmail.com> wrote:
> On 9/3/05, Jan Schaumann <jschauma@netmeister.org> wrote:

> > I have a problem with mountd that I simply can't figure out:
> >=20
> > I have a file /etc/exports consistin entirely of the following line:
> >=20
> > /hold   -maproot=3Droot   192.168.0.2
> >=20
> > When I start mountd, I get a message saying
> >=20
> > /hold     -maproot", line 1: Can't export /hold: Invalid argument
> >=20
> > /hold is a directory, under which a partition is mounted.
> >=20
> > What could cause mount(2) to return EINVAL on /hold ?  According to the
> > manual page, EINVAL should be returned if ``The super block for the file
> > system had a bad magic number or an out of range block size.''  I've
> > fsck'd the filesystem (with an alternate super block to make sure), and
> > still I get the same error.
> >=20
> > Does anybody have any ideas what's going on here?
>=20
> I suppose it could still receive "bad" values for either one of those
> reasons, if what it got was something it wasn't expecting? Maybe it's
> a filesystem that it isn't expecting or something? Or you newfs'd it
> with some options NFS doesn't like for some reason?

Well, the thing that really gets me is that this is a system that has
been working fine for the longest time.  The filesystem hasn't changed.

I just can't make any sense of this.

-Jan

--=20
The Internet interprets censorship as damage and routes around it.
	-- John Gilmore

--bjuZg6miEcdLYP6q
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (NetBSD)

iD8DBQFDGyiUfFtkr68iakwRAjIkAJ9S3DW7SYJkHb/9MydMu476hsH0RACcCQKx
Mj6ViR8SyubAwF6tkIZ/css=
=wefV
-----END PGP SIGNATURE-----

--bjuZg6miEcdLYP6q--