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:

Proportional Font

LISTSERV Archives

LISTSERV Archives

XROOTD-L Home

XROOTD-L Home

XROOTD-L  March 2017

XROOTD-L March 2017

Subject:

Re: audit with frm_admin

From:

Patrick McGuigan <[log in to unmask]>

Reply-To:

Support use of xrootd by HEP experiments <[log in to unmask]>

Date:

Fri, 10 Mar 2017 16:52:24 -0600

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (197 lines)

On 03/10/2017 04:43 PM, Andrew Hanushevsky wrote:
> Hi Patrick,
>
> On Fri, 10 Mar 2017, Patrick McGuigan wrote:
>
>> We normally mount four partitions as /xrd_cache_[1-4].  This dataserver was
>> incorrectly setup and /xrd_cache_1 and /xrd_cache_4 are mounting the same device!
> OK, that just means the partition for cache_1 and cache_4 were used twice as
> often than would be expected.
>
>> I think I need to turn off xrootd, unmount the disks, clean up /etc/fstab,
>> remount the disks, modify the links under /xrd to replace references to
>> /xrd_cache_4 with /xrd_cache_1 and then restart xrootd.
> Indeed the symlink needs to change all 4's need to become 1's.
>
>> Is the naming structure guaranteed to be the same under different partitions
>> to the name of the file?:
>>
>> for instance:
>> /xrd/datadisk/some/path is a link to /xrd_cache_4/ATLASDATADISK/xx/HASH%
>>
>>
>> If the file should be on /xrd_cache_1, would xx and HASH% be same regardless
>> of partition?
> Well, you are in luck here because the cache file paths were identical in
> length. So, you should be able to simply change the symlink and not bother with
> anything in the cache.
>>

Good enough.  I am glad that this is the case.


>>
>> I am debating about allowing some access (read, maybe delete) to xrootd while
>> I am renaming links since this would allow the correct two partitions to operate.
> I don't immediately see how. Once you separate the caches, any reference to a
> cache_4 file will fail because cache_4 is now empty, right? As I see it, all
> files in cache_4 also exist in cache_1. So, you should be able to rename the
> links to point to their Cache_1 image. Then fix up the mount point after that's
> done. You can allow read access during this. If you also want to have write
> access then remove cache_4 from the list of available spaces (i.e. specify
> cache_1, 2, and 3 explicitly -- don't use an asterisk.
>

I was planning on using a read only (or read +delete, but no write) so that 
normal access will available for cache_2 and cache_3.  The cache_1 space should 
also be in good shape from the perspective of the exported path.  I need to make 
some backup listings of things so that I have good picture of where everything 
is right now.


> Make sense?
>

So far.

> Andy
>
>>
>>
>> Patrick
>>
>> On 03/10/2017 02:48 PM, Andrew Hanushevsky wrote:
>>> Hi Patrick,
>>>
>>> Hmm, well audit space does check that the files are actually linked via the name
>>> space. So, if it tells you all of tehm are reachable then they should be. On the
>>> other hand it also said, if I am not mistaken, that
>>> the space had no files in it (which I find hard to beleive). So, something else
>>> must be going on. You can rerrun audit space but specify -d (debug) on the
>>> command line to see what it actually is doing.
>>>
>>> Andy
>>>
>>>
>>> On Fri, 10 Mar 2017, Yang, Wei wrote:
>>>
>>>> HI Patrick,
>>>>
>>>> I think the best way is to rebuild the symlinks in name space (/xrd). For each
>>>> file in /xrd_cache_*, you can find what its symlinks should be by doing
>>>> something like this:
>>>>
>>>> $ getfattr -d
>>>> //atlas/xrdcache/sdb/ATLASDATADISK/22/CB0C6157C00C00000000ac172c8922E9010014D%
>>>> getfattr: Removing leading '/' from absolute path names
>>>> # file:
>>>> atlas/xrdcache/sdb/ATLASDATADISK/22/CB0C6157C00C00000000ac172c8922E9010014D%
>>>> user.XrdCks.adler32=0sYWRsZXIzMgAAAAAAAAAAAAAAAABXRH7/ADNKMQAAAATRL9rKAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
>>>>
>>>>
>>>> user.XrdFrm.Pfn="/atlas/xrootd/atlasdatadisk/rucio/mc15_5TeV/97/7d/log.08435138._004167.job.log.tgz.1"
>>>>
>>>>
>>>>
>>>> After you rebuild the symlinks in name space, you can then decide which files
>>>> are not needed (or rely on the RUCIO team to delete for you).
>>>>
>>>> regards,
>>>> --
>>>> Wei Yang  |  [log in to unmask]  |  650-926-3338
>>>>
>>>> ________________________________________
>>>> From: [log in to unmask] <[log in to unmask]> on behalf of
>>>> Patrick McGuigan <[log in to unmask]>
>>>> Sent: Friday, March 10, 2017 12:06 PM
>>>> To: xrootd-l
>>>> Subject: audit with frm_admin
>>>>
>>>> Hi,
>>>>
>>>> I have an odd situation with a dataserver that uses XA space names and how
>>>> space
>>>> usage is being reported.
>>>>
>>>> I export an area named /xrd
>>>>
>>>> We are not using mig or stage options on the export.
>>>>
>>>>
>>>> I have a named space:
>>>>         oss.space ATLASDATADISK /xrd_cache_*
>>>>
>>>>
>>>>
>>>> At the system level, only files written to /xrd/datadisk should be in the
>>>> ATLASDATADISK space.
>>>>
>>>> I have a script that walks the exported directory to discover the files being
>>>> stored on the server and record date and size information:
>>>>
>>>> find -L /xrd -type f -fprintf  /tmp/xrd_files '%p %T@ %s\n'
>>>>
>>>>
>>>> If I run 'frm_admin -c /etc/xrootd/xrootd-clustered.cfg audit usage' I get
>>>> amounts for claimed and actual bytes used by the various named spaces including
>>>> ATLASDATADISK.
>>>>
>>>> The problem is that the amount claimed in the audit output is 20TB (33%) larger
>>>> than what I expect by walking the path /xrd/datadisk.
>>>>
>>>> It looks like there are files in /xrd_cache_x/ATLASDATDISK/... that do not have
>>>> links in /xrd/datadisk.
>>>>
>>>> What is the correct way to rectify this issue?
>>>>
>>>> I tried to run
>>>>
>>>> frm_admin -c /etc/xrootd/xrootd-clustered.cfg audit space ATLASDATADISK
>>>>
>>>> 0 problems found; 0 fixed.
>>>> Space ATLASDATADISK has 0 files with 0 bytes in use (0 unreachable).
>>>>
>>>>
>>>>
>>>> Should I run an audit names?
>>>>
>>>> Should the audit invocation look like:
>>>> ... audit name /xrd/datadisk
>>>> ?
>>>>
>>>>
>>>> Thanks for any insights,
>>>>
>>>> Patrick
>>>>
>>>> ########################################################################
>>>> Use REPLY-ALL to reply to list
>>>>
>>>> To unsubscribe from the XROOTD-L list, click the following link:
>>>> https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-L&A=1
>>>> ########################################################################
>>>> Use REPLY-ALL to reply to list
>>>>
>>>> To unsubscribe from the XROOTD-L list, click the following link:
>>>> https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-L&A=1
>>>>
>>>
>>> ########################################################################
>>> Use REPLY-ALL to reply to list
>>>
>>> To unsubscribe from the XROOTD-L list, click the following link:
>>> https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-L&A=1
>>
>
> ########################################################################
> Use REPLY-ALL to reply to list
>
> To unsubscribe from the XROOTD-L list, click the following link:
> https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-L&A=1

########################################################################
Use REPLY-ALL to reply to list

To unsubscribe from the XROOTD-L list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-L&A=1

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

March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
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