LISTSERV mailing list manager LISTSERV 16.5

Help for XROOTD-L Archives


XROOTD-L Archives

XROOTD-L Archives


XROOTD-L@LISTSERV.SLAC.STANFORD.EDU


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

XROOTD-L Home

XROOTD-L Home

XROOTD-L  February 2005

XROOTD-L February 2005

Subject:

Re: How do we export multiple directories from xrootd.cf

From:

Jerome LAURET <[log in to unmask]>

Date:

28 Feb 2005 14:00:03 -0500Mon, 28 Feb 2005 14:00:03 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (155 lines)


The files are statically placed by a distributed disk
system I presented at one or the other CHEP. Works fine but
sucks to actually do that statically (so one possible advantage
of Xrootds goal #3 leading to dynamic population). The diverse
partitions are not fixed i.e. some node may have one more more
but not all (or all) of the mentionned partitions. The path is
HPSS is /home/starreco/XXX while on local disk it is /YYY/XXX
where /YYY is /?/starlib "?" standing for one of data0, data1,
data2 or home. Of course, if I could map /home/starreco/XXX
to /?/starlib/XXX that would surely help reducing the namespace
(replica Catalog) down to nothing (goal #2).

No SRM involved at this stage (SRM manages big gatekeeper
local storage or NFS based cache, not the 200 nodes storage ...
yet). This would be goal #4 (or a variant).

> in a multi experiment setup, I "tricked" the system by using soft
> links, making one single filesystem being visible using two different
> prefix, but I don't think this is exactly what you want in your
> particular case.

Jean Yves, I can play tricks using soft-links of
directories and use /home only, I think (this is the only
one which is more or less always present although may be
a soft-link itself to another FS). Looking for the best way
to do that ...

 > AFAIK, there is no simple directive or soft link trick for that. The
 > best bet is the cache filesystem, see the mps/cache-filesystem doc:
 >
 > http://xrootd.slac.stanford.edu/doc/mps_config/mps_config.htm

... and as far as I understand the presence of multiple
disks on one node along with purge/migration and MPS component
is possible (??!) In your figure /kanga and /cache0, /cache1 etc ..
is /kanga "populated" by links to the cache(s) ??


Thanks,


              ,,,,,
             ( o o )
          --m---U---m--
              Jerome

PS : Is there a problem in setting the Reply-to of this list to
      be the list itself ?? I receive duplicate Emails for about
      every post since poeople use 'Reply-all' to cope for Reply-to,
      From discrepencies.


Peter Elmer wrote:

> Hi Jerome,
>
> On Mon, Feb 28, 2005 at 11:24:18AM -0500, Jerome LAURET wrote:
>
>> I beleive we asked how to do that at some point (hide the path
>> arranegement) except that we could not figure out on how to mix
>> /home and /data into a single substitution. Your case of
>> oss.localroot /kanga and oss.remoteroot /kanga or /xrootd at SLAC
>> ar a bit too convenient. Can we trick olb with soft-link or there
>> is a simple syntax which can take care of all /data + /home (the
>> path afterward is all and the same) ??
>
>
> I guess there is nothing special to differentiate the 4 partitions
> {/data0, /data1, /data2, /home}? i.e. all files can in principle go
> on any of the 4 partitions?
>
> AFAIK, there is no simple directive or soft link trick for that. The
> best bet is the cache filesystem, see the mps/cache-filesystem doc:
>
> http://xrootd.slac.stanford.edu/doc/mps_config/mps_config.htm
>
> What currently manages the data on those partitions? Has it just been
> statically placed there or is it being actively managed/staged by
> something? (SRM?)
>
> Pete
>
>
>> Peter Elmer wrote:
>>
>>
>>> Hi Pavel,
>>>
>>> On Sun, Feb 27, 2005 at 01:05:46PM +0100, Pavel Jakl wrote:
>>>
>>>
>>>> we are using in our conf files export multiple directories and
>>>> all data
>>>
>>>> from these directives are accessible:
>>>
>>>> xrootd.export /data0 xrootd.export /data1 xrootd.export /data2
>>>> xrootd.export /home
>>>
>>>
>>> Hmm, you are probably right: perhaps this was something that Andy
>>> fixed at some point? I see Matt is using the xrootd version from
>>> ROOT 4.02-00 itself (i.e. 20041124-0752). What version are you
>>> running at BNL?
>>>
>>> Matt, could you try the latest "development" version
>>> 20050226-0852? This is a development version, but the one we are
>>> currently testing to become the next "production" version.
>>>
>>> (Unfortunately it looks like we got one of the intermediate
>>> development versions of the xrootd server itself into the
>>> production version of ROOT! It is no big deal to download and
>>> build the proper version of the server separately, but we'll need
>>> to be careful in the future to make sure only production versions
>>> of xrootd wind up in production versions of ROOT...)
>>>
>>>
>>>
>>>> I also enlose the log file from redirector where you can see,
>>>> that files (from /data1 and data2) are located and redirected
>>>> to right node without using cache file system.
>>>>
>>>> 050227 12:14:22 28868 odc_Locate: user=starlib.782:12@rcas6002
>>>> redirected to rcas6067.rcf.bnl.gov:1095 by xrdstar
>>>> path=/data2/starlib/reco/productionCentral/FullField/P02ge/2001/318/st_physics_2318037_raw_0012.MuDst.root
>>>> 050227 12:14:22 28868 odc_Receive: Server: Received from
>>>> xrdstar.rcf.bnl.gov: 481 !try rcas6067.rcf.bnl.gov:1095 050227
>>>> 12:14:22 28868 odc_Locate: user=starlib.782:12@rcas6002
>>>> redirected to rcas6067.rcf.bnl.gov:1095 by xrdstar
>>>> path=/data2/starlib/reco/productionCentral/FullField/P02ge/2001/318/st_physics_2318037_raw_0008.MuDst.root
>>>>
>>>
>>>
>>> I guess the "/data2", etc. is left from your previous method of
>>> finding the files? In general we try to hide that from the user
>>> (since it is an internal detail of the server-side) with some
>>> combination of the cache filesystem and the use of the
>>> "localroot" directive.
>>>
>>> Pete
>>>
>
>
>
> -------------------------------------------------------------------------
> Peter Elmer E-mail: [log in to unmask] Phone: +41 (22)
> 767-4644 Address: CERN Division PPE, Bat. 32 2C-14, CH-1211 Geneva
> 23, Switzerland
> -------------------------------------------------------------------------
>
--


Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
July 2009
June 2009
May 2009
April 2009
March 2009
January 2009
December 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004

ATOM RSS1 RSS2



LISTSERV.SLAC.STANFORD.EDU

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager

Privacy Notice, Security Notice and Terms of Use