obile device nfs needs to be mounted on demand.
After gvfs installation:
The nfs share icon disappeared from the desktop. So I need to mount by a
terminal command.
Is there a way to have gvfs and have icons of nfs shares (defined in
/etc.fstab) on the desktop?
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
>>> - 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 thou
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
imple fix to Jessie by uploading it to
>> stable-proposed-updates. What do you think? Also, do you think that
>> /etc/systemd/system/remote-fs-pre.target.d/nfs.conf belongs to systemd
>> package or to nfs-common? I would say it belongs to nfs-common as that
>> one provid
md
> package or to nfs-common? I would say it belongs to nfs-common as that
> one provides the required tools and services to mount NFS shares on a
> client.
So the fix I gave you is a fix that shouldn't be copied verbatim into
a Debian package. /etc/systemd is administrator
after that systemd tries to mount the NFS
> filesystem
>
> - in parallel, first rpcbind and then nfs-common is started
Thanks a lot for disassembling and explaining the boot procedure. I see
that the problem here is that systemd doesn't wait for rpcbind.service
and nfs-commo
(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
/network/interfaces) will wait until
>> the interface is up before continuing
>
> I changed 'allow-hotplug eth0' to 'auto eth0' in /etc/network/interfaces
> now. Unfortunately it didn't have any effect. Still the same error
> message during boot p
n /etc/init.d/networking (which is used to set up the
> interfaces in Debian from /etc/network/interfaces) will wait until
> the interface is up before continuing
I changed 'allow-hotplug eth0' to 'auto eth0' in /etc/network/interfaces
now. Unfortunately it didn
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)
>>>
gt;
> i have a similar warning/error.
>
> interestingly my nfs mount seems to work for some reason even
> though it claims that there was a problem.
You mean that your systemd reports a ordering cycle in dmesg? And your
NFS shares are automatically mounted during boot process ne
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:
>>
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 share
mail /var/vmail nfs4 _netdev,sec=krb5i,bg 0 0
results in unmounted NFS shares after reboot and:
[FAILED] Failed to mount /var/vmail.
See 'systemctl status var-vmail.mount' for details.
[DEPEND] Dependency failed for Remote File Systems.
Starting Trigger Flushing of
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
entries in /etc/fstab for such
> cases, but it seems like Debian doesn't support this option, right?
>
> Is there any other solution to mount NFS shares during boot process on
> Debian Jessie systems? Mounting the manually (or by rc.local) later is
> not an option for me. Several
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?
Is there any other solution to mount NFS shares during boot process on
Debian Jessie systems? Mo
Hello,
So as we've found out, the problem is caused by mountnfs script not
expecting --all. This can be temporarily fixed by adding this:
[ "$ADDRFAM" = "inet" ] || [ "$ADDRFAM" = "inet6" ] || exit 0
just after '[ "$IFACE" != "lo" ] || exit 0'
into /etc/network/if-up.d/mountnfs. This is going to
Hi,
I've also been hit by this bug. (using wheezy as well)
>From what I've seen, it only adds a trailing slash when mounting
with the nfsvers=3 (or =2) option.
If you can confirm this behavior then I see no reason not to call it a
bug ! :-)
--
Laurent
--
To UNSUBSCRIBE, email to debian-user
I just upgraded from Squeeze to Wheezy and noticed that now NFS exports
have an extra trailing slash in /proc/mounts (aka /etc/mtab, aka
/proc/self/mounts).
> server:/vol/export1/ on /server/mountpath type nfs (rw,nosuid,nodev,noatime…)
But the trailing slash is not originated in /etc/fstab.
>
Le mardi 26 octobre 2010, Simon Brandmair a écrit :
> On Tue, 26 Oct 2010 17:00:03 +0200 Denis Laxalde wrote:
> > Recently nfs shares stopped being automatically mounted on 2 of my
> > machines. These are up-to-date squeeze systems and the nfs server
> > runs lenny. This us
On Tue, 26 Oct 2010 17:00:03 +0200 Denis Laxalde wrote:
> Recently nfs shares stopped being automatically mounted on 2 of my
> machines. These are up-to-date squeeze systems and the nfs server runs
> lenny. This used to work fine until one or two months ago. I cannot see
> any relevan
Denis Laxalde schreef:
> Hello,
>
> Recently nfs shares stopped being automatically mounted on 2 of my
> machines. These are up-to-date squeeze systems and the nfs server runs
> lenny. This used to work fine until one or two months ago.
> I cannot see any relevant message in l
On Tue, Oct 26, 2010 at 11:57 AM, Denis Laxalde wrote:
> Le mardi 26 octobre 2010, Erwan David a écrit :
>> Are you sure they speak the same version of nfs ? squeeze is nfsv4 by
>> default, and I think lenny is nfsv3, so a nfsvers option might help.
>
> I don't know, but from nfs manual says that
Le mardi 26 octobre 2010, Erwan David a écrit :
> Are you sure they speak the same version of nfs ? squeeze is nfsv4 by
> default, and I think lenny is nfsv3, so a nfsvers option might help.
I don't know, but from nfs manual says that "if this option (nfsvers) is
not specified, the client attempt
On Tue, Oct 26, 2010 at 04:41:12PM CEST, Denis Laxalde
said:
> Hello,
>
> Recently nfs shares stopped being automatically mounted on 2 of my
> machines. These are up-to-date squeeze systems and the nfs server runs
> lenny. This used to work fine until one or two months ago.
>
Hello,
Recently nfs shares stopped being automatically mounted on 2 of my
machines. These are up-to-date squeeze systems and the nfs server runs
lenny. This used to work fine until one or two months ago.
I cannot see any relevant message in logs.
Any help would be appreciated
Cheers,
Denis
nfs shares on all machines but one; I am unable to mount
nfs shares on my Ubuntu 8.10 box.
Home Network:
Debian Sid, 686 desktop, wired connection
Ubuntu 8.10, 686 desktop, wireless connection
Debian 5.0, laptop, wireless connection
Each is configured as both nfs server and
On Fri, Apr 18, 2008 at 04:39:03PM +0100, John Talbut wrote:
> I have a small home network with nfs set up so that the computers can share
> files. Commonly only one of the computers is running, particularly at
> first. I would like the running computer(s) to automount the nfs share
I have a small home network with nfs set up so that the computers can share
files. Commonly only one of the computers is running, particularly at first. I
would like the running computer(s) to automount the nfs shares from the other
computers when they come on line.
I have been using a line
Paul Johnson wrote:
> On Tuesday 18 October 2005 12:05 pm, David Dawson wrote:
>> I am experimenting with NSF mounts over the internet.
>> So far, the share works on the local network between my two local
>> machines, but only "sort of" on the remote machine.
>
> Try setting up a VPN with the re
NFS may be attempting to use UDP - Unreliable Datagram Protocol (IIRC).
I believe you'll find the acronym means "User Datagram Protocol".
Yes, sure, but since when haven't the backronyms been more apt?
Regards, Max
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubsc
Andrew M.A. Cater wrote:
On Tue, Oct 18, 2005 at 05:45:20PM -0700, Paul Johnson wrote:
On Tuesday 18 October 2005 12:05 pm, David Dawson wrote:
I am experimenting with NSF mounts over the internet.
So far, the share works on the local network between my two local
machines, but only "sort of"
On Tue, Oct 18, 2005 at 05:45:20PM -0700, Paul Johnson wrote:
> On Tuesday 18 October 2005 12:05 pm, David Dawson wrote:
> > I am experimenting with NSF mounts over the internet.
> > So far, the share works on the local network between my two local
> > machines, but only "sort of" on the remote ma
On Tuesday 18 October 2005 12:05 pm, David Dawson wrote:
> I am experimenting with NSF mounts over the internet.
> So far, the share works on the local network between my two local
> machines, but only "sort of" on the remote machine.
Try setting up a VPN with the remote network and using that fo
On tirsdag 18 oktober 2005, 21:05, David Dawson wrote:
> the remote machine can ls the share, send and receive small files
> (say 100 bytes) but when an attempt to send or receive a larger file
> is made, the konqueror process reports 'stalled' and goes into
> uninterruptable sleep.
Uh, ouch. Well
I am experimenting with NSF mounts over the internet.
So far, the share works on the local network between my two local
machines, but only "sort of" on the remote machine.
The two local machines are running Debian Sarge and the NSF server is
running the 2.6.8-2-386 Debian kernel.
The other local m
Hi Ethan!
It seems that the NFS server only supports version 2 as Tommi stated.
Thanks for the tips though!
Jason.
--On Monday, October 9, 2000 3:24 am -0800 Ethan Benson <[EMAIL PROTECTED]>
wrote:
On Mon, Oct 09, 2000 at 01:11:17PM +0200, Jason Quigley wrote:
Hi!
I am trying to set up an
Hi Tommi!
I put in a switch on the mount command to go to version 2. That did the trick,
it mounts and I can see the directories from the command line (unfortunately,
not the Finder, but that's another story :).
Many thanks,
Jason.
--On Monday, October 9, 2000 2:24 pm +0300 Tommi Komulainen
On Mon, Oct 09, 2000 at 01:11:17PM +0200, Jason Quigley wrote:
> I am trying to set up an NFS share from my Debian server to allow a test
> system
> (Mac OS X) to access it. When I try to mount from the client machine I get:
>
> The server's syslog has:
> Oct 9 13:07:35 cubeship kernel: svc: un
On Mon, Oct 09, 2000 at 01:11:17PM +0200, Jason Quigley wrote:
> Hi!
>
> I am trying to set up an NFS share from my Debian server to allow a test
> system
> (Mac OS X) to access it. When I try to mount from the client machine I get:
>
>
>
> [tangy:~/Mounts] jason% mount -o ro 192.168.1.1:/mnt
Hi!
I am trying to set up an NFS share from my Debian server to allow a test system
(Mac OS X) to access it. When I try to mount from the client machine I get:
[tangy:~/Mounts] jason% mount -o ro 192.168.1.1:/mnt/hungry-monster/data/
/Users/jason/Dimwit/
[tangy:~/Mounts] jason% ls -l
ls: D
47 matches
Mail list logo
