LISTSERV mailing list manager LISTSERV 16.5

Help for ATLAS-SCCS-PLANNING-L Archives


ATLAS-SCCS-PLANNING-L Archives

ATLAS-SCCS-PLANNING-L Archives


ATLAS-SCCS-PLANNING-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

ATLAS-SCCS-PLANNING-L Home

ATLAS-SCCS-PLANNING-L Home

ATLAS-SCCS-PLANNING-L  May 2007

ATLAS-SCCS-PLANNING-L May 2007

Subject:

RE: Minutes of ATLAS/SCCS Planning Meeting 2nd May 2007

From:

"Young, Charles C." <[log in to unmask]>

Date:

4 May 2007 02:41:59 -0700Fri, 4 May 2007 02:41:59 -0700

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (40 lines)

Sorry I was not able to attend. Have some questions about this parity business.

> 2. Tier-2 Hardware
> 
>     One storage machine has the OS. Should get two of the machines up
>     and running, allow Len to do some testing with the third
>     machine. There is some question about how many parity disks we
>     want, one or two. There is some discussion at HEPiX about how long

When one disk fails, how many TB's of data are affected? 

>     it takes to reconstruct an array after loosing a disk, we would be
>     at risk during the reconstruction. Len will try to 

You mean a second disk failing before everything on the array has been reconstructed? Hope the components are not that unreliable. What is the advertised MTBF for a drive? 

> measure how long
>     it takes and try to get information from other labs. With double
>     parity it is more reliable but there is a write-time and space
>     parity. An element of the discussion would be the type of data on
>     it, if it was really just a cache of data stored 
> elsewhere or if it
>     was the primary storage. Even if we believe it is just a cache an

Tier 2 is not supposed to be primary storage for anything. True it may be the only storage for production before it is transferred to Tier 1 for archival. However, that is recoverable by regenerating so we actually have infinite number of "backups". On the scale of things, regenerating is cheap. 

>     worry would be how long it would take to reimport all the data
>     again from BNL (probably around a week). Could setup different

I assume we would not do this if reconstructing takes less than a week. So this is an upper bound, right? 

>     areas for production with double parity.

Production could be more tolerant. One, data is swept to Tier 1 for archival, so we should not lose more than a day or two's worth. Two, production data is, almost by definition, something with a fairly long lead time and regenerating them would be acceptable. Active analysis data disappearing is likely to have greater impact on users. Can we use our tape system to back these up -- assuming it is much faster getting things back from our tapes than from across the country? 

> 



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 2016
July 2016
June 2016
May 2016
April 2016
March 2016
November 2015
September 2015
July 2015
June 2015
May 2015
April 2015
February 2015
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
September 2013
August 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
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 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

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