From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <13426df10908031956t5cb01b8bl611ef09669ca5f19@mail.gmail.com> References: <1248914582.479.7837.camel@work.SFBay.Sun.COM> <140e7ec30907300931v3dbd8ebdl32a6b74792be144@mail.gmail.com> <28CF259C-21F4-4071-806E-6D5DA02C985D@sun.com> <13426df10907312241q409b9f9w412974485aec7fee@mail.gmail.com> <13426df10908010847v5f4f891fq9510ad4b671660ea@mail.gmail.com> <1249349522.479.15191.camel@work.SFBay.Sun.COM> <13426df10908031956t5cb01b8bl611ef09669ca5f19@mail.gmail.com> Date: Tue, 4 Aug 2009 06:07:04 +0100 Message-ID: From: roger peppe To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] ceph Topicbox-Message-UUID: 37870a0e-ead5-11e9-9d60-3106f5b1d025 2009/8/4 ron minnich : >> =C2=A02. do we have anybody successfully managing that much storage that= is >> =C2=A0 =C2=A0 also spread across the nodes? And if so, what's the best p= ractices >> =C2=A0 =C2=A0 out there to make the client not worry about where does th= e storage >> =C2=A0 =C2=A0 actually come from (IOW, any kind of proxying of I/O, etc) > > Google? the exception that proves the rule? they emphatically don't go for posix semantics...