PAPERS ON THE FIFTH 6360 QUIZ

1
PAPERS ON THE FIFTH 6360 QUIZ

• Jehan-François Pâris
• jfparis_at_sbcglobal.net
• Spring 2010

2
Distributed File Systems

• A, Muthitacharoen, B. Chen, and D. Mazieres, A
  Low-bandwidth network file system, Proc. 18th
  SOSP Symp., pp. 174187, 2001.
• We discussed the objective of LBFS and its use of
  chunking to reduce file transfer and file storage
  costs. We did not discuss any implementation
  details.

3
Distributed File Systems

• E. B. Nightingale and J. Flinn. Energy-efficiency
  and storage flexibility in the Blue file system.
  Proc. 6th USENIX OSDI Conf., pp. 363378, Dec.
  2004.
• We discussed the main objectives of BlueFS, its
  Write to All policy (including e-nodes), how and
  why aggregating writes can save energy and how
  BlueFS selects from which device to read data.
  You should read the paper

4
Distributed File Systems

• A. Adya, W. J. Bolosky, M. Castro, G. Cermak, R.
  Chaiken, J. R. Douceur, J. Howell, J. R. Lorch,
  M. Theimer and R.P. Wattenhofer, FARSITE
  Federated, Available, and Reliable Storage for an
  Incompletely Trusted Environment, Proc. 5th
  USENIX OSDI Symp., Dec. 2002.
• We covered the paper in some detail. You are
  responsible for all the topics discussed in the
  PowerPoint slides.

5
Distributed File Systems

• M. W. Storer, K.. Greenan, E. L. Miller, K.
  Voruganti, Pergamum Replacing Tape with Energy
  Efficient, Reliable, Disk-Based Archival Storage,
  Proc. 6th USENIX FAST Conf., pp. 1-16, Feb.
  2008.
• Focus on tome organization and the choice of tome
  components, how Pergamum uses two-level
  redundancy and how it uses algebraic signatures.
  You should read the paper.

6
Byzantine Agreement

• R. Kotla, L. Alvisi, M. Dahlin, A. Clement and E.
  Wong, Zyzzyva Speculative Byzantine fault
  tolerance, Proc. 21st ACM SOSP Symp., Oct. 2007.
• We discussed how Zyzzyva uses speculative
  execution to speed up Byzantine fault-tolerant
  agreements and the special role it assigns to the
  client . We did not discuss the protocol in
  detail. and skipped the view change sub-protocol.