From: "\"Fábio Jr.\"" <fjuniorlista@gmail.com>
To: Rob Gardner <rob.gardner@hp.com>
Cc: "nfs@lists.sourceforge.net" <nfs@lists.sourceforge.net>
Subject: Re: [NFS] Export especific file extension
Date: Tue, 28 Jul 2009 11:40:11 -0300 [thread overview]
Message-ID: <4A6F0DCB.3090903@gmail.com> (raw)
In-Reply-To: <4A6F02F5.9090002@hp.com>
Rob Gardner escreveu:
> F=E1bio Jr. wrote:
>> Rob Gardner escreveu:
>> =20
>>> F=E1bio Jr. wrote:
>>> =20
>>>> Rob Gardner escreveu:
>>>> =20
>>>> =20
>>>>> F=E1bio Jr. wrote:
>>>>> =20
>>>>>> Hello all.
>>>>>>
>>>>>> Is there a way to export only some specific file extensions from=
=20
>>>>>> a directory, like exporting only the files in /home/fabio with=20
>>>>>> the .jpg extension?
>>>>>> =20
>>>>> You could do this pretty easily by exporting a 'fuse' filesystem=20
>>>>> layered on top of your home directory.
>>>>>
>>>>> Rob Gardner
>>>>> HP
>>>>>
>>>>> =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=20
>>>> the 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=20
>>>> your 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=20
>>> program such as a python script. So, for instance, every time a=20
>>> process opens a file, a function is called in your script, and you=20
>>> can look at the name of the file being opened, and there decide=20
>>> whether or not to allow the file to be opened. I think this would=20
>>> solve your problem easily. Though all the storage is "exported",=20
>>> only files with certain names (ie, *.jpg, etc) could be opened. You=
=20
>>> could also decide which 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=20
>> script must be executed. I already have some issues with server=20
>> availability, and perhaps the solution of a problem becomes the=20
>> worsening of another.
>>
>> 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 th=
e=20
> pseudo-filesystem. Each requests causes a few lines in the script to=20
> be executed. There is no process creation and dispatch for each=20
> operation, only a process wakeup for each operation. It is=20
> impressively lightweight and it's worth trying before dismissing it a=
s=20
> a resource drain.
>
Hmm.. that's interesting, but, how many requests this script can handle=
?=20
This can vary in diferent systems or configs, or even can be measured?
> 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.
>
Unfortunately, even if I wanted to, it's not possible to do this in my=20
scenario, since I have aprox. 4 milion files only in jpeg format in=20
different folders, not counting the other extensions. The major problem=
=20
was the planning phase, that not counted with so many files and not=20
prepared the files organization to better performance. But for smallers=
=20
systems, its a very good solution.
[]s
=46=E1bio jr.
-----------------------------------------------------------------------=
-------
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
next prev parent reply other threads:[~2009-07-28 14:41 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
2009-07-28 14:40 ` "Fábio Jr." [this message]
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=4A6F0DCB.3090903@gmail.com \
--to=fjuniorlista@gmail.com \
--cc=nfs@lists.sourceforge.net \
--cc=rob.gardner@hp.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 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.