All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Gardner <rob.gardner@hp.com>
To: "\"Fábio Jr.\"" <fjuniorlista@gmail.com>
Cc: "nfs@lists.sourceforge.net" <nfs@lists.sourceforge.net>
Subject: Re: [NFS] Export especific file extension
Date: Tue, 28 Jul 2009 07:53:57 -0600	[thread overview]
Message-ID: <4A6F02F5.9090002@hp.com> (raw)
In-Reply-To: <4A6EFEE9.1070708@gmail.com>

=46=E1bio Jr. wrote:
> Rob Gardner escreveu:
>  =20
>> F=E1bio Jr. wrote:
>>    =20
>>> Rob Gardner escreveu:
>>> =20
>>>      =20
>>>> F=E1bio Jr. wrote:
>>>>   =20
>>>>        =20
>>>>> Hello all.
>>>>>
>>>>> Is there a way to export only some specific file extensions from =
a=20
>>>>> directory, like exporting only the files in /home/fabio with the=20
>>>>> .jpg extension?
>>>>>      =20
>>>>>          =20
>>>> You could do this pretty easily by exporting a 'fuse' filesystem=20
>>>> layered on top of your home directory.
>>>>
>>>> Rob Gardner
>>>> HP
>>>>
>>>>    =20
>>>>        =20
>>> Thanks Rob for the reply,
>>>
>>> This means that if I use this FUSE, I can export via NFS only the=20
>>> file extension that I need? let me explain my problem, not really a=
=20
>>> problem, but a doubt.
>>>
>>> I have one storage that have my aplication files. This storage is=20
>>> mounted via NFS in my 3 aplication servers. Now I will put another=20
>>> server, to serve only static files (jpg,png,css,js basically), and=20
>>> though that maybe there is a way to export only these files from th=
e=20
>>> storage. The problem is that these files are not organized in=20
>>> diferent folders.
>>>
>>> Maybe my first question doesn't explained my real necessity, but yo=
ur=20
>>> answer will make me search a little more about FUSE.
>>>      =20
>> I think your first question explained your need clearly. FUSE is a=20
>> filesystem layer that lets you filter requests through a user progra=
m=20
>> such as a python script. So, for instance, every time a process open=
s=20
>> a file, a function is called in your script, and you can look at the=
=20
>> name of the file being opened, and there decide whether or not to=20
>> allow the file to be opened. I think this would solve your problem=20
>> easily. Though all the storage is "exported", only files with certai=
n=20
>> names (ie, *.jpg, etc) could be opened. You could also decide which=20
>> files get enumerated with readdir, etc.
>>
>> Rob Gardner
>> HP
>>
>>
>>    =20
> Oh yes, I think I didn't understand you answer.. but now all became=20
> clear in my mind. I'm afraid that using this solution maybe cause an=20
> increase on storage processor load, because for every request the scr=
ipt=20
> must be executed. I already have some issues with server availability=
,=20
> and perhaps the solution of a problem becomes the worsening of anothe=
r.
>
> Still thanks for the reply and thanks for helping to clear my mind.

It's a valid concern, but fuse does not "execute a script" for every=20
operation. The script is always running, sort of like a server for the=20
pseudo-filesystem. Each requests causes a few lines in the script to be=
=20
executed. There is no process creation and dispatch for each operation,=
=20
only a process wakeup for each operation. It is impressively lightweigh=
t=20
and it's worth trying before dismissing it as a resource drain.

But anyway, here's another idea for you-- Export a new directory that=20
contains links to only those the files you want to export.


Rob Gardner
HP



-----------------------------------------------------------------------=
-------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30=
-Day=20
trial. Simplify your report design, integration and deployment - and fo=
cus on=20
what you do best, core application coding. Discover what's new with=20
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that nfs@lists.sourceforge.net is being discontinued.
Please subscribe to linux-nfs@vger.kernel.org instead.
    http://vger.kernel.org/vger-lists.html#linux-nfs


  reply	other threads:[~2009-07-28 13:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-27 20:31 [NFS] Export especific file extension "Fábio Jr."
2009-07-27 22:20 ` Rob Gardner
2009-07-28 11:06   ` "Fábio Jr."
2009-07-28 13:20     ` Rob Gardner
2009-07-28 13:36       ` "Fábio Jr."
2009-07-28 13:53         ` Rob Gardner [this message]
2009-07-28 14:40           ` "Fábio Jr."
2009-07-28 15:58             ` Rob Gardner
2009-07-28 16:21               ` J. Bruce Fields

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=4A6F02F5.9090002@hp.com \
    --to=rob.gardner@hp.com \
    --cc=fjuniorlista@gmail.com \
    --cc=nfs@lists.sourceforge.net \
    /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.