All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gionatan Danti <g.danti-N44kj/XGErOonA0d6jMUrA@public.gmane.org>
To: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Gionatan Danti <g.danti-N44kj/XGErOonA0d6jMUrA@public.gmane.org>
Subject: Problem with Samba re-share of a CIFS mount
Date: Tue, 11 Feb 2014 10:30:13 +0100	[thread overview]
Message-ID: <52F9EDA5.1020004@assyoma.it> (raw)

Hi all,
I have a strange problem trying to re-share, via Samba, a CIFS mount.

Let first explain my network topology:

Win2008R2 w/SMB share -> low speed link -> Linux Box -> WIN7 clients

In short, a Win2008 R2 share is being accessed by some W7 clients over a 
slow (~8 Mb/s downstream, ~1 Mb/s upstream) ADSL link. To speed up read 
operation on the branch office, I thought to use a Linux Box with 
cachefilesd and a CONFIG_CIFS_FSCACHE enabled kernel. The Linux box will 
mount the Win2008R2 share and, thanks to cachefilesd, it will maintain 
an "hot cache" of the read data. This CIFS mount is then shared, via 
Samba, to the other client Win7 PCs.

However, the problem is that when re-sharing the CIFS mount, the Win7 
clients often see the many directories inside the mount as a regular 
files, and not directories! In other words, if I have a directory "test" 
inside the mount, the client PC will see a _file_ called "test". When 
double-clicking on that "file", the Win7 client even ask to select the 
application to open it.

The strange this is that this problem happen with some Linux kernel 
version, but not with others. These are my results:

1) Stock CentOS 6.5 x86-64 system (kernel 2.6.32-431.1.2.0.1, cifs-utils 
4.8.1-19, samba 3.6.9-167): no problem here, but this kernel does not 
have CONFIG_CIFS_FSCACHE, so I can not use it for speeding up read access;

2) CentOS 6.5 x86-64 with ElRepo updates (kernel 3.10.28-1): here 
CONFIG_CIFS_FSCACHE is enabled, but I have the problem described above;

3) Debian 7 amd64 with latest updates (kernel 3.2.54-2, cifs-utils 
2:5.5-1): CONFIG_CIFS_FSCACHE is enabled, problem happens;

4) Fedora 20 x86-64 (kernel 3.12.8-300, cifs-utils 6.3-1, samba 
4.1.3-2): CONFIG_CIFS_FSCACHE is enabled and problem does _not_ happen, 
however this is a client distro and I am not so comfortable to put it 
into production.

Anyone has any explanation of what is happening here?
Regards.

-- 
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: g.danti-N44kj/XGErOonA0d6jMUrA@public.gmane.org - info-N44kj/XGErOonA0d6jMUrA@public.gmane.org
GPG public key ID: FF5F32A8

             reply	other threads:[~2014-02-11  9:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-11  9:30 Gionatan Danti [this message]
     [not found] ` <52F9EDA5.1020004-N44kj/XGErOonA0d6jMUrA@public.gmane.org>
2014-02-11 15:33   ` Problem with Samba re-share of a CIFS mount Jeff Layton
     [not found]     ` <20140211103302.6d74b90d-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2014-02-11 15:50       ` Gionatan Danti
     [not found]         ` <52FA46D5.8020904-N44kj/XGErOonA0d6jMUrA@public.gmane.org>
2014-02-11 16:59           ` Steve French
     [not found]             ` <CAH2r5mvXh2A_LOm5y7BpgKS6bQhNGjEDR8CYn=K2CnMv01HQeQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-02-11 17:05               ` Gionatan Danti
2014-02-11 17:45           ` Jeff Layton
     [not found]             ` <20140211124536.5fdcb56f-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2014-02-11 18:01               ` Steve French
     [not found]                 ` <CAH2r5mvQ590zaniv3cDuu+Do0N9TePasTaEFkrNSAdatTiaZ5Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-02-13 11:37                   ` Jeff Layton
     [not found]                     ` <20140213063738.1b345466-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2014-02-13 17:29                       ` Gionatan Danti
     [not found]                         ` <52FD0109.5030909-N44kj/XGErOonA0d6jMUrA@public.gmane.org>
2014-02-13 18:04                           ` Steve French
     [not found]                             ` <CAH2r5msMZsnC8hxh6=P=f_vsuB=DR_Hv9xyLUEZtG+WpzYU=Sg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-02-14 10:27                               ` Gionatan Danti
2014-02-13 19:40                           ` Jeff Layton
     [not found]                             ` <20140213144038.2101ea44-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2014-02-14  2:14                               ` Suresh Jayaraman
     [not found]                                 ` <52FDC978020000F4000256F9-ce6RLXgGx+vWGUEhTRrCg1aTQe2KTcn/@public.gmane.org>
2014-02-14 12:06                                   ` Jeff Layton
2014-02-14 10:25                               ` Gionatan Danti
     [not found]                                 ` <52FDEF0D.8010708-N44kj/XGErOonA0d6jMUrA@public.gmane.org>
2014-02-14 12:17                                   ` Jeff Layton
     [not found]                                     ` <20140214071724.725d8545-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2014-02-14 14:10                                       ` Gionatan Danti
2014-02-14 12:08                           ` Jeff Layton
     [not found]                             ` <20140214070846.09904331-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2014-02-14 14:05                               ` Gionatan Danti
2014-02-11 18:09               ` Gionatan Danti

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=52F9EDA5.1020004@assyoma.it \
    --to=g.danti-n44kj/xgeroona0d6jmura@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.