Linux NFS development
 help / color / mirror / Atom feed
From: dE <de.techno@gmail.com>
To: linux-nfs@vger.kernel.org
Subject: Re: Cant get to export this particular directory.
Date: Thu, 05 Feb 2015 08:04:24 +0530	[thread overview]
Message-ID: <54D2D6B0.4010402@gmail.com> (raw)
In-Reply-To: <20150204173039.421c3192@harpe.intellique.com>

On 02/04/15 22:00, Emmanuel Florac wrote:
> Le Wed, 04 Feb 2015 21:38:35 +0530
> dE <de.techno@gmail.com> écrivait:
>
>> No, the previous directory is (huge)
>>
>> /dev/sda15 on /home/test/huge type reiser4 (rw,noatime)
> And does exporting from some other place in the same filesystem
> (/home/test/huge/whatever) work ?
>
> I suppose reiser4 is 64 bits. what's the inode number of
> /home/test/huge/temp_small/subdir ?
> I've seen problems on some systems mounting inodes with large (not 32
> bits compatible) numbers.
>
> Another problem I've seen was when mixing clients with 3.8 kernel and
> servers with 3.2 kernels.
>

No. For any directory it doesn't work.

There is a stranger behavior. If I mount the parent directory of the 
export like /home/test/huge/temp_small or /home/test/huge (when 
/home/test/huge/whatever is exported), it mounts and only the exported 
directory is accessible/seen. However all_squash flag does not appear to 
be working with /home/test/huge/temp_small; I cant access 
/home/test/huge/temp_small/subdir as root.

But it appears to be working for localhost.

The inodes are 32 bit. e.g. 297618, 264250, 280589 etc...

On one end I'm running the server on 3.17 and the client on 3.10.

  reply	other threads:[~2015-02-05  2:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-04 15:15 Cant get to export this particular directory dE
2015-02-04 16:03 ` Emmanuel Florac
2015-02-04 16:08   ` dE
2015-02-04 16:30     ` Emmanuel Florac
2015-02-05  2:34       ` dE [this message]
2015-02-05 10:58     ` Boaz Harrosh
2015-02-05 12:00       ` Mkrtchyan, Tigran
2015-02-05 14:05         ` Christoph Hellwig
2015-02-05  7:31 ` Mkrtchyan, Tigran

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=54D2D6B0.4010402@gmail.com \
    --to=de.techno@gmail.com \
    --cc=linux-nfs@vger.kernel.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