All of lore.kernel.org
 help / color / mirror / Atom feed
From: steve <steve-dZ4O0aZtNmBWk0Htik3J/w@public.gmane.org>
To: "McCall,
	Andy (IT.PFMS)"
	<Andy.McCall-JGeVbDYbwmjRZ1oM81ef8Q@public.gmane.org>
Cc: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: DFS root namespace mounting problem...
Date: Tue, 05 Aug 2014 18:16:00 +0200	[thread overview]
Message-ID: <1407255360.4226.1.camel@hh16.hh3.site> (raw)
In-Reply-To: <44E091A70C02494A806AD35E6F93AB1A32B89D-44HqyMtr/CW7efwRAOVE6/PBkhW9OzgPksZubNBzXmQ@public.gmane.org>

On Tue, 2014-08-05 at 16:22 +0100, McCall, Andy (IT.PFMS) wrote:
> >> I've just swapped /usr/sbin/cifs.upcall out for a script that echo's 
> >> test to /tmp/text.txt and cifs.upcall isn't actually being called at all in my case.
> >
> >You may already have a ticket.
> 
> It might be that the test of swapping out cifs.upcall for a script won't work, but
> I tried it on a second identical build server on the farm that hasn't been touched
> yet and that also didn't produce /tmp/text.txt, so either the test is invalid or
> cifs.upcall isn't getting called.

Is this the problem:
//fqdn/share
mounts OK, but
//domain/share
doesn't.

  parent reply	other threads:[~2014-08-05 16:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-05 13:11 DFS root namespace mounting problem McCall, Andy (IT.PFMS)
     [not found] ` <44E091A70C02494A806AD35E6F93AB1A32B89B-44HqyMtr/CW7efwRAOVE6/PBkhW9OzgPksZubNBzXmQ@public.gmane.org>
2014-08-05 14:14   ` steve
     [not found]     ` <1407248098.1426.7.camel-HkULYb+WTT7YCGPCin2YbQ@public.gmane.org>
2014-08-05 14:26       ` McCall, Andy (IT.PFMS)
     [not found]         ` <44E091A70C02494A806AD35E6F93AB1A32B89C-44HqyMtr/CW7efwRAOVE6/PBkhW9OzgPksZubNBzXmQ@public.gmane.org>
2014-08-05 15:12           ` steve
     [not found]             ` <1407251579.2941.8.camel-HkULYb+WTT7YCGPCin2YbQ@public.gmane.org>
2014-08-05 15:22               ` McCall, Andy (IT.PFMS)
     [not found]                 ` <44E091A70C02494A806AD35E6F93AB1A32B89D-44HqyMtr/CW7efwRAOVE6/PBkhW9OzgPksZubNBzXmQ@public.gmane.org>
2014-08-05 16:16                   ` steve [this message]
     [not found]                     ` <1407255360.4226.1.camel-HkULYb+WTT7YCGPCin2YbQ@public.gmane.org>
2014-08-06  9:09                       ` McCall, Andy (IT.PFMS)

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

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

  git send-email \
    --in-reply-to=1407255360.4226.1.camel@hh16.hh3.site \
    --to=steve-dz4o0aztnmbwk0htik3j/w@public.gmane.org \
    --cc=Andy.McCall-JGeVbDYbwmjRZ1oM81ef8Q@public.gmane.org \
    --cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /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. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.