[debian-lan-devel] Softupdate wheezy

Julien Lambot jlambot at gmail.com
Sun Apr 21 22:26:11 UTC 2013


Hi Andreas
Thanks for your time and replies.
I'll explain further hereunder.
Obviously I was confused on the way bind mount was supposed to work.


> I am not sure if I understand you correctly.  Is this on the server or
> on the clients?  Where the filesystem the home directories live on the
> server should not make much difference. They are bind mounted from
> wherever they are to /srv/nfs4/home to be exported.  Take a look at
> /etc/fstab and /etc/exports.
>

Sorry if i was unclear. The mount issue was on the server.

>
> > I went to this conclusion because I did an installation again on kvm and
> > everything went fine with only one filesystem for the server. Virtual
> > clients did install and run successfully.
>
> That's good to hear!
>

Indeed, it worked flawlessly :)

>
> > I tried several other bind mount and simple mounts but I don't get it
> > properly mounted.
> > Have you some idea about that?
> > I would just like to mount the /srv/nfs4/home0 onto
> /dev/mapper/vg00-lvhome
> > and have /lan/mainserver/home0 correctly linked.
>
> Usually it's the other way round:  You mount the partition on where your
> home directories are going to live.


Sure! I wasn't clear. I meant to mount a directory onto a physical
partiton/volume...
;)


> Then you bind mount that
> directory to '/srv/nfs4/home0' to make it available for exports,
> cf. /etc/fstab:
>
> [...]
> /dev/vg_system/home     /lan/mainserver/home0   ext4    usrquota ...
> [...]
> /lan/mainserver/home0    /srv/nfs4/home0        none    bind    ...
>

>
> Hope that helps a bit.  As I'm not sure if I go you right, please
> describe your problems and modifications in more detail if I got
> something wrong.
>

It worked fine this way !
Mount point has now enough space.

I am testing back the other issue with client logins now. I will keep you
informed.
For now on, the same error on the client side (though "mainserver" is
correctly resolved by the client).
Apr 22 00:03:37 workstation01 rpc.gssd[1694]: ERROR: unable to resolve
10.10.12.10 to hostname: Name or service not known
Apr 22 00:03:37 workstation01 rpc.gssd[1694]: ERROR: failed to read service
info

So, I will continue to split config files and check why this doesn't
resolves for rpc.gssd.

Then, when mainserver.intern is added to /etc/hosts, and ..... tadaaaa it's
OK :)

I will further test Debian-Lan and keep you posted.

Regards

Julien
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/debian-lan-devel/attachments/20130422/32c046c0/attachment.html>


More information about the debian-lan-devel mailing list