Hi,
On 07/16/2015 09:04 AM, n n wrote:
> trying to mount nfs-shares at boot I have exactly the problem mentioned by
> Christian:
> (in Message-id: <558e8105.5030...@iwakd.de>)
>
>> - On some systems with static IP addresses (and
>> /etc/network/interfaces), I had the problem that even thou
>>> - On some systems with static IP addresses (and
>>> /etc/network/interfaces), I had the problem that even though the
>>> interface was conisdered up and ready by the kernel, the switch it
>>> was connected to needed 30s or so to realize that fully (and
>>> packets were simply
n n wrote:
> trying to mount nfs-shares at boot I have exactly the problem mentioned by
> Christian:
> (in Message-id: <558e8105.5030...@iwakd.de>)
>> - On some systems with static IP addresses (and
>> /etc/network/interfaces), I had the problem that even though the
>> interface was c
Hi there,
trying to mount nfs-shares at boot I have exactly the problem mentioned by
Christian:
(in Message-id: <558e8105.5030...@iwakd.de>)
> - On some systems with static IP addresses (and
> /etc/network/interfaces), I had the problem that even though the
> interface was conisdered u
[ bringing pkg-systemd-maintainers into the loop here ]
Am 27.06.2015 um 20:14 schrieb Christian Seiler:
> On 06/27/2015 08:02 PM, Jonas Meurer wrote:
>> Am 27.06.2015 um 16:07 schrieb Christian Seiler:
>>> Could you try to do the following:
>>>
>>> 1. create a directory /etc/systemd/system/remote
On 06/27/2015 08:02 PM, Jonas Meurer wrote:
> Am 27.06.2015 um 16:07 schrieb Christian Seiler:
>> Could you try to do the following:
>>
>> 1. create a directory /etc/systemd/system/remote-fs-pre.target.d
>> 2. create a file /etc/systemd/system/remote-fs-pre.target.d/nfs.conf
>>with the followin
Hi Christian,
Am 27.06.2015 um 16:07 schrieb Christian Seiler:
> (Ccing the bugtracker because it appears you've stumbled upon a bug
> that also a few other people had, see below. Please don't reply to the
> bugtracker yourself unless you feel it's relevant for the bug report.)
>
> Link to thread
(Ccing the bugtracker because it appears you've stumbled upon a bug
that also a few other people had, see below. Please don't reply to the
bugtracker yourself unless you feel it's relevant for the bug report.)
Link to thread on debian-user for people reading the bug report:
https://lists.debian.or
On 06/27/2015 03:12 PM, Jonas Meurer wrote:
> So I'm pretty sure that NFS is setup correctly both on server and
> client. My problem is about mounting the NFS share automatically during
> the boot process.
Looks like it, yes.
>> However, since you need the interface at boot anyway, you don't
Hi Christian,
thanks for the comprehensive reply. It helps a lot to better understand
the details of systemd NFS mount handling.
Am 27.06.2015 um 12:55 schrieb Christian Seiler:
> On 06/26/2015 07:44 PM, Arno Schuring wrote:
>>> On 2015-06-26 18:38 +0200, Jonas Meurer wrote:
>>> mount.nfs4 prints
On 06/26/2015 07:44 PM, Arno Schuring wrote:
>> From: svenj...@gmx.de
>> Date: Fri, 26 Jun 2015 19:28:37 +0200
>> On 2015-06-26 18:38 +0200, Jonas Meurer wrote:
Process: 352 ExecMount=/bin/mount -n nfs-server:/vmail /var/vmail
-t
nfs4 -o sec=krb5i,_netdev (code=exited, status=32)
>>>
Hi Brian,
Am 27.06.2015 um 07:29 schrieb bri...@aracnet.com:
> On Fri, 26 Jun 2015 19:28:37 +0200
> Sven Joachim wrote:
>
>
>> Maybe rpcbind was started too late, see bug #763315[1] on that topic.
>> What is the output of "systemctl status rpcbind.service"?
>
> i have a similar warning/error.
Hi Sven,
Am 26.06.2015 um 19:28 schrieb Sven Joachim:
> On 2015-06-26 18:38 +0200, Jonas Meurer wrote:
>>> # grep nfs /etc/fstab
>>> nfs-server:/vmail /var/vmail nfs4 _netdev,sec=krb5i,bg 0 0
>>
>> results in unmounted NFS shares after reboot and:
>>
>>>
>>> Jun 26 16:29:02 clt mount[352]: mount.n
On 15-06-26 5:42 PM, Jonas Meurer wrote:
> Problem seems to be that the NFS mounts are mounted directly after
> the root fs, before the network is set up properly. Also, the mountnfs
> if-up.d hook from /etc/network/if-up.d/mountnfs doesn't work for
> systemd systems.
>
> Here's the relevant output
On Fri, 26 Jun 2015 19:28:37 +0200
Sven Joachim wrote:
> Maybe rpcbind was started too late, see bug #763315[1] on that topic.
> What is the output of "systemctl status rpcbind.service"?
>
> Cheers,
>Sven
>
>
> 1. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763315
>
i have a s
> From: svenj...@gmx.de
> Date: Fri, 26 Jun 2015 19:28:37 +0200
>
> On 2015-06-26 18:38 +0200, Jonas Meurer wrote:
>>>
>>> # systemctl status var-vmail.mount
>>> ● var-vmail.mount - /var/vmail
>>> Loaded: loaded (/etc/fstab)
>>> Active: failed (Result: exit-code) since Fri 2015-06-26 16:29:02
>>>
On 2015-06-26 18:38 +0200, Jonas Meurer wrote:
> Oops, I searched only in fstab(5) and nfs(5) manpages. Still, the
> option doesn't work:
>
>> # grep nfs /etc/fstab
>> nfs-server:/vmail /var/vmail nfs4 _netdev,sec=krb5i,bg 0 0
>
> results in unmounted NFS shares after reboot and:
>
>> [FAILED] Fai
Hi again,
Am 2015-06-26 18:15, schrieb Sven Joachim:
On 2015-06-26 17:42 +0200, Jonas Meurer wrote:
While searching the web I learned that Ubuntu and Redhat based distros
seem to support the '_netdev' option to entries in /etc/fstab for such
cases, but it seems like Debian doesn't support this
On 2015-06-26 17:42 +0200, Jonas Meurer wrote:
> While searching the web I learned that Ubuntu and Redhat based distros
> seem to support the '_netdev' option to entries in /etc/fstab for such
> cases, but it seems like Debian doesn't support this option, right?
Huh, what makes you think so? The
> Am 26.06.2015 um 17:42 schrieb Jonas Meurer :
>
> Hello,
>
> I fail to configure my Debian/Jessie server system in a way that the
> NFS mounts are mounted automatically on boot.
>
> Problem seems to be that the NFS mounts are mounted directly after
> the root fs, before the network is set up p
20 matches
Mail list logo
