From: Jack Norton <jack@0x6a.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Petabytes on a budget: JBODs + Linux + JFS
Date: Mon, 14 Sep 2009 10:50:23 -0500 [thread overview]
Message-ID: <4AAE663F.1080207@0x6a.com> (raw)
In-Reply-To: <a6dc96eb834906054ed328111976a6b5@quanstro.net>
erik quanstrom wrote:
>> So what about having venti on an AoE device, and fossil on a local drive
>> (say an ssd even)?
>>
>
> sure. we keep the cache on the coraid sr1521 as well.
>
>
>> How would you handle (or: how would venti handle), a
>> resize of the AoE device?
>>
>
> that would depend on the device structure of ken's fs.
> as long as you don't use the pseudo-worm device, it wouldn't
> care. the worm would simply grow. if you use the pseudo-worm
> device (f), changing the size of the device would fail since
> the written bitmap is at a fixed offset from the end of the
> device. and if you try to read an unwritten block, the f
> panics the file server. i stopped using the f device.
>
> - erik
>
>
I am going to try my hands at beating a dead horse:)
So when you create a Venti volume, it basically writes '0's' to all the
blocks of the underlying device right? If I put a venti volume on a AoE
device which is a linux raid5, using normal desktop sata drives, what
are my chances of a successful completion of the venti formating (let's
say 1TB raw size)? Have you ever encountered such problems, or are you
using more robust hardware?
I ask because I have in the past, failed a somewhat-used sata drive
while creating a venti volume (it subsequently created i/o errors on
every os I used on it, although it limped along). I must say it is
quite a brutal process, creating venti (at least I get that impression
from the times I have done it in the past).
If linux is my raid controller, I know that it is _very_ picky about how
long a drive takes to respond and will fail a drive if it has to wait
too long.
By the way I am currently buying a few pieces of cheap hardware to
implement my own diskless fileserver. Should be ready to go in about a
couple of weeks.
-Jack
next prev parent reply other threads:[~2009-09-14 15:50 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-04 0:53 Roman V Shaposhnik
2009-09-04 1:20 ` erik quanstrom
2009-09-04 9:37 ` matt
2009-09-04 14:30 ` erik quanstrom
2009-09-04 16:54 ` Roman Shaposhnik
2009-09-04 12:24 ` Eris Discordia
2009-09-04 12:41 ` erik quanstrom
2009-09-04 13:56 ` Eris Discordia
2009-09-04 14:10 ` erik quanstrom
2009-09-04 18:34 ` Eris Discordia
[not found] ` <48F03982350BA904DFFA266E@192.168.1.2>
2009-09-07 20:02 ` Uriel
2009-09-08 13:32 ` Eris Discordia
2009-09-04 16:52 ` Roman Shaposhnik
2009-09-04 17:27 ` erik quanstrom
2009-09-04 17:37 ` Jack Norton
2009-09-04 18:33 ` erik quanstrom
2009-09-08 16:53 ` Jack Norton
2009-09-08 17:16 ` erik quanstrom
2009-09-08 18:17 ` Jack Norton
2009-09-08 18:54 ` erik quanstrom
2009-09-14 15:50 ` Jack Norton [this message]
2009-09-14 17:05 ` Russ Cox
2009-09-14 17:48 ` Jack Norton
2009-09-04 23:25 ` James Tomaschke
2009-09-14 16:43 erik quanstrom
2009-09-20 20:13 ` Bakul Shah
2009-09-21 3:37 ` erik quanstrom
2009-09-21 17:43 ` Bakul Shah
2009-09-21 18:02 ` erik quanstrom
2009-09-21 18:49 ` Wes Kussmaul
2009-09-21 19:21 ` erik quanstrom
2009-09-21 20:57 ` Wes Kussmaul
2009-09-21 22:42 ` erik quanstrom
2009-09-22 10:59 ` matt
2009-09-21 19:10 ` Bakul Shah
2009-09-21 20:30 ` erik quanstrom
2009-09-21 20:57 ` Jack Norton
2009-09-21 23:38 ` erik quanstrom
2009-09-21 22:07 ` Bakul Shah
2009-09-21 23:35 ` Eris Discordia
2009-09-22 0:45 ` erik quanstrom
[not found] ` <6DC61E4A6EC613C81AC1688E@192.168.1.2>
2009-09-21 23:50 ` Eris Discordia
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AAE663F.1080207@0x6a.com \
--to=jack@0x6a.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).