linux-bcache.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kent Overstreet <kent.overstreet@gmail.com>
To: Martin McClure <martin.mcclure@gemtalksystems.com>
Cc: linux-bcache@vger.kernel.org
Subject: Re: Can a bcachefs filesystem be exported via NFS?
Date: Tue, 7 Jun 2016 19:45:46 -0800	[thread overview]
Message-ID: <20160608034546.GA1538@kmo-pixel> (raw)
In-Reply-To: <5755E9CA.4060609@gemtalksystems.com>

On Mon, Jun 06, 2016 at 02:23:22PM -0700, Martin McClure wrote:
> Can a bcachefs filesystem be exported via NFS?
> 
> I have a bcachefs filesystem mounted on /meteor4. When I try to export
> it, I get:
> 
> ---
> root@meteor:~# service nfs-kernel-server restart
>  * Stopping NFS kernel daemon   [ OK ]
>  * Unexporting directories for NFS kernel daemon...      [ OK ]
>  * Exporting directories for NFS kernel daemon...
> exportfs: /meteor4 does not support NFS export
> ---
> 
> and the system log says:
> 
> Jun  6 14:11:28 meteor rpc.mountd[31541]: /meteor3 and /meteor4 have
> same filehandle for *, using first
> 
> Not sure what this is about. /meteor3 is a vanilla ext4 partition.
> 
> If I try to access /meteor4 from another machine via NFS, Meteor's log
> shows this:
> 
> Jun  6 14:15:10 meteor rpc.mountd[31541]: Cannot export /meteor4,
> possibly unsupported filesystem or fsid= required
> 
> So I'm guessing it's not yet supported, but wanted to check in case I'm
> doing something wrong.

Thanks for noticing - yeah, not supported yet. And it's going to need an on disk
format change for i_generation, erg. Excuse me while I go punch myself...

  reply	other threads:[~2016-06-08  3:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-06 21:23 Can a bcachefs filesystem be exported via NFS? Martin McClure
2016-06-08  3:45 ` Kent Overstreet [this message]
2016-06-16 18:46   ` Eric Wheeler

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=20160608034546.GA1538@kmo-pixel \
    --to=kent.overstreet@gmail.com \
    --cc=linux-bcache@vger.kernel.org \
    --cc=martin.mcclure@gemtalksystems.com \
    /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;
as well as URLs for NNTP newsgroup(s).