Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: Sergey Urushkin <urushkin-MKmKHxvQ5r6HXe+LvDLADg@public.gmane.org>
To: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: DFS and ls: cannot access /some/path: Object is remote
Date: Mon, 08 Oct 2012 16:18:34 +0400	[thread overview]
Message-ID: <5072C49A.6010108@telros.ru> (raw)

Hi!
I have a problem using DFS share with a number of user applications
(like libreoffice, thunderbird, etc.). The problem is that I can't enter
to any part of a dfs share (link to another share) via file manager,
because fm can't list contents of directory with dfs links properly. In
terminal it looks like this:

/tmp/test - mounted dfs share
/tmp/test/all - real directory on the server with dfs share
/tmp/test/all/* - dfs links

# ls /tmp/test/all/*
ls: cannot access /tmp/test/all/admin: Object is remote
ls: cannot access /tmp/test/all/drivers: Object is remote
ls: cannot access /tmp/test/all/linux-iso: Object is remote

Same time, listing of the one link works fine:
# ls /tmp/test/all/linux-iso
file1
file2
file3

After listing "linux-iso":
1) with kernel 3.2 listing of * looks the same;
2) with kernel 3.6.1 listing of * looks differ:
# ls /tmp/test/all/*
ls: cannot access /tmp/test/all/admin: Object is remote
ls: cannot access /tmp/test/all/drivers: Object is remote

/tmp/test/all/linux-iso:
file1
file2
file3

and user apps now see "linux-iso" as directory. It's better then 3.2 ...
... but after some amount of time "linux-iso" link becomes unavailable
(Object is remote) again.

So, the question: is there a way to make kernel list contents of all dfs
links in the directory/share. I see two ways to do so:
1) show dfs links as directories, not links (without actual connection
to it, if it's possible)
2) try to connect and mount every link when app try to list the
directory with links (it will be slow, but it will work at least)

Thanks.

-- 
Best regards,
Sergey Urushkin

                 reply	other threads:[~2012-10-08 12:18 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=5072C49A.6010108@telros.ru \
    --to=urushkin-mkmkhxvq5r6hxe+lvdladg@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox