<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://homeostasis.scs.carleton.ca/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Simcoe</id>
	<title>Soma-notes - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://homeostasis.scs.carleton.ca/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Simcoe"/>
	<link rel="alternate" type="text/html" href="https://homeostasis.scs.carleton.ca/wiki/index.php/Special:Contributions/Simcoe"/>
	<updated>2026-05-12T20:51:45Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.42.1</generator>
	<entry>
		<id>https://homeostasis.scs.carleton.ca/wiki/index.php?title=NASD,_GoogleFS,_Farsite&amp;diff=1789</id>
		<title>NASD, GoogleFS, Farsite</title>
		<link rel="alternate" type="text/html" href="https://homeostasis.scs.carleton.ca/wiki/index.php?title=NASD,_GoogleFS,_Farsite&amp;diff=1789"/>
		<updated>2008-03-10T20:11:42Z</updated>

		<summary type="html">&lt;p&gt;Simcoe: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Readings==&lt;br /&gt;
&lt;br /&gt;
[http://homeostasis.scs.carleton.ca/~soma/distos/2008-03-10/gibson-nasd.pdf Garth A. Gibson et al., &amp;quot;A Cost-Effective, High-Bandwidth Storage Architecture&amp;quot; (1998)]&lt;br /&gt;
&lt;br /&gt;
[http://homeostasis.scs.carleton.ca/~soma/distos/2008-03-10/gfs-sosp2003.pdf Sanjay Ghemawat et al., &amp;quot;The Google File System&amp;quot; (2003)]&lt;br /&gt;
&lt;br /&gt;
[http://homeostasis.scs.carleton.ca/~soma/distos/2008-03-10/adya-farsite-intro.pdf Atul Adya et al.,&amp;quot;FARSITE: Federated, Available, and Reliable Storage for an Incompletely Trusted Environment&amp;quot; (2002)]&lt;br /&gt;
&lt;br /&gt;
[http://homeostasis.scs.carleton.ca/~soma/distos/2008-03-10/bolosky-farsite-retro.pdf William J. Bolosky et al., &amp;quot;The Farsite Project: A Retrospective&amp;quot; (2007)]&lt;br /&gt;
&lt;br /&gt;
==Questions==&lt;br /&gt;
&lt;br /&gt;
# What were the target environments for these filesystems?  How did these environments shape their assumptions?&lt;br /&gt;
# What are the key ideas behind each filesystem?&lt;br /&gt;
# What are the strengths and weaknesses of each design?&lt;br /&gt;
# What are the strengths and weaknesses of each implementation?&lt;br /&gt;
# Which system is best suited for today&#039;s Internet?  How about tomorrow&#039;s?&lt;br /&gt;
&lt;br /&gt;
==Questions for NASD==&lt;br /&gt;
# Is giving direct access between client and drive a good idea? &lt;br /&gt;
# Are there substantial advantages in storing variable-length objects over fixed-sized blocks?&lt;br /&gt;
# Is putting the filesystem on the drive a good idea? Should more control and awareness be given to hardware devices?&lt;br /&gt;
# What are the strengths and weaknesses of the capability-based cryptography which NASD makes use of?&lt;br /&gt;
&lt;br /&gt;
==Questions for GoogleFS==&lt;br /&gt;
# How does the Google file system implement security?&lt;br /&gt;
# Is using a central server (point of access) a good design decision?&lt;br /&gt;
# Is removing random writes a good idea?&lt;br /&gt;
# Is the speedup attained by GFS&#039;s record-append method worth the sacrifice of Application overhead?&lt;br /&gt;
&lt;br /&gt;
==Questions for Farsite==&lt;br /&gt;
# Byzantine fault tolerance?&lt;br /&gt;
# How similar and different compared to OceanStore?&lt;br /&gt;
&lt;br /&gt;
==Questions for Farsite retrospective==&lt;br /&gt;
# If using different programming methods... how does this file-system work given different programming models&lt;br /&gt;
# Details of buyzantine fault tolerance&lt;/div&gt;</summary>
		<author><name>Simcoe</name></author>
	</entry>
</feed>