unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: emacs@martins.cc
Cc: 32520@debbugs.gnu.org
Subject: bug#32520: 26.1; problem with CIFS mounts
Date: Fri, 24 Aug 2018 22:31:51 +0300	[thread overview]
Message-ID: <83pny78st4.fsf@gnu.org> (raw)
In-Reply-To: <2757.1535127885@monster.martins.cc> (emacs@martins.cc)

> From: emacs@martins.cc
> Date: Fri, 24 Aug 2018 09:24:45 -0700
> 
> I automount windows shares under a common mountpoint, say /cifs.
> 
> When I cd to or references something like:
>   /cifs/<host>/<share>/path/to/file_or_dir
> the windows share is mounted on
>   /cifs/<host>/<share>
> and the process can get to .../path/to/file_or_dir.
> 
> When I visit one of those directories with emacs 26 (maybe
> also files on that share), I get a bunch of syslog warnings
> from the CIFS subsystem.
> 
> Sometimes they just say:
> 
>   [608270.512407] CIFS VFS: BAD_NETWORK_NAME: \\host\.dir-locals-2.el
>   [608270.512744] CIFS VFS: cifs_mount failed w/return code = -2
>   [608270.517939] CIFS VFS: BAD_NETWORK_NAME: \\host\.dir-locals.el
>   [608270.518326] CIFS VFS: cifs_mount failed w/return code = -2

I guess Emacs tries to go up the directory tree too far, it should
stop at /cifs/<host>/<share/.  But how should it know it isn't
supposed to go up from /cifs/<host>/<share/ ?

> It is clogging my syslog with bogus messages, as I do visit
> lots of files and directories on remote windows share every
> day.

Does it cause any other trouble?





  parent reply	other threads:[~2018-08-24 19:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-24 16:24 bug#32520: 26.1; problem with CIFS mounts emacs
2018-08-24 18:06 ` Glenn Morris
2018-08-24 18:35   ` emacs
2018-08-24 20:30     ` Glenn Morris
2018-08-24 21:20       ` emacs
2018-08-24 22:36         ` Noam Postavsky
2018-08-24 22:53           ` emacs
2018-08-24 19:31 ` Eli Zaretskii [this message]
2018-08-24 20:25   ` emacs

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83pny78st4.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=32520@debbugs.gnu.org \
    --cc=emacs@martins.cc \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).