From: Norbert van Bolhuis <nvbolhuis-bYiImlzuGf1HoQZOM9yvow@public.gmane.org>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: exportfs: Warning: /adir does not support NFS export.
Date: Wed, 11 Nov 2009 08:13:53 +0100 [thread overview]
Message-ID: <4AFA6431.9010405@aimvalley.nl> (raw)
In-Reply-To: <20091110180747.GA15000@fieldses.org>
J. Bruce Fields wrote:
> On Tue, Nov 10, 2009 at 05:44:17PM +0100, Norbert van Bolhuis wrote:
>> I get the following exportfs 1.2.0 warning:
>>
>> exportfs: Warning: /adir does not support NFS export.
>>
>> Although everything works fine, I'm worried about this.
>>
>> The directoy "/adir" is the path to a ISOZFS loop mounted image.
>
> What's ISOZFS?
>
The ISO9660 filesystem (with rockridge extension), see mkzftree(1).
>> The ISO(Z)FS image itself resides on a UBIFS filesystem (/flashfs/isozfs_image.iso).
>> The root dir ("/"), as well as "/adir" and "/flashfs" is initramfs.
>>
>> So afaik I'm exporting a ISOFS, this is supported by nfsd (in the kernel), so
>> why is the warning there ?
>>
>> I know UBIFS doesn't support to be (nfsd) exported by the kernel,
>> but ISO(Z)FS and initramfs do, right ?
>>
>> Am I doing something illegal ?
>
> Which distribution are you using? Is it something that worked before,
> and stopped working, or is this the first time you've tried it?
>
> --b.
I'm building an embedded linux system.
This is the first time I try this.
next prev parent reply other threads:[~2009-11-11 7:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-10 16:44 exportfs: Warning: /adir does not support NFS export Norbert van Bolhuis
[not found] ` <4AF99861.7030103-bYiImlzuGf1HoQZOM9yvow@public.gmane.org>
2009-11-10 18:07 ` J. Bruce Fields
2009-11-11 7:13 ` Norbert van Bolhuis [this message]
[not found] ` <4AFA6431.9010405-bYiImlzuGf1HoQZOM9yvow@public.gmane.org>
2009-11-11 14:13 ` J. Bruce Fields
2009-11-11 14:16 ` Norbert van Bolhuis
[not found] ` <4AFAC74A.5000503-bYiImlzuGf1HoQZOM9yvow@public.gmane.org>
2009-11-11 17:53 ` J. Bruce Fields
2009-11-12 7:41 ` Norbert van Bolhuis
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=4AFA6431.9010405@aimvalley.nl \
--to=nvbolhuis-byiimlzugf1hoqzom9yvow@public.gmane.org \
--cc=bfields@fieldses.org \
--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