From: Lyndon Nerenberg <lyndon@orthanc.ca>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] anyone put their venti on an SSD?
Date: Fri, 3 May 2013 18:16:49 -0700 [thread overview]
Message-ID: <2F31A92B-4011-42DB-9043-D04F6B81A504@orthanc.ca> (raw)
In-Reply-To: <69b6245860f4a50b378f2458153fabd6@plan9.bell-labs.com>
On 2013-05-03, at 1:59 PM, geoff@plan9.bell-labs.com wrote:
> I tried putting our index on a single OCZ SSD and it died during buildindex.
> The SSD was completely unresponsive thereafter, which is pretty
> appalling behaviour for a storage device. Having since sworn off
> OCZ, I would try again with a pair of Intel 330s in a RAID.
A couple of months ago I tried cloning my existing fossil+venti to an OCZ Vertex 3. I did the partitioning and setup by hand and everything seemed to go just fine: the arenas copied and verified, fossil initialized, and I could run and mount the fossil from the SSD, but whenever I tried to boot from it it failed very early on with "I/O error" and that was that. I didn't have any spare time to mess around with it so I just stuck with the existing disk.
I was running a really bastardized mix of old and new boot software, so it's quite possible I screwed up installing the correct MBR and boot loader. But it might also have been a problem with the BIOS or SATA controller on the motherboard -- it's a slightly ancient Supermicro Atom 1U, and it doesn't like SATA hard disks, either (it's currently talking to an IDE disk). I didn't have time to try 9atom.
That said, the limited testing I did with the secondary fossil+venti showed it to be quite zippy, within the limitations of the surrounding motherboard hardware. Certainly it was noticeably faster than the hard disk for, e.g., mk all.
--lyndon
next prev parent reply other threads:[~2013-05-04 1:16 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-03 14:19 Steve Simon
2013-05-03 14:28 ` a
2013-05-03 20:59 ` geoff
2013-05-03 21:51 ` Matthew Veety
2013-05-03 21:58 ` cinap_lenrek
2013-05-04 1:59 ` erik quanstrom
2013-05-04 4:17 ` cinap_lenrek
2013-05-04 6:17 ` erik quanstrom
2013-05-03 23:59 ` Charles Forsyth
2013-05-04 1:31 ` cinap_lenrek
2013-05-04 1:41 ` Devon H. O'Dell
2013-05-04 1:47 ` Lyndon Nerenberg
2013-05-04 1:51 ` erik quanstrom
2013-05-04 1:57 ` Lyndon Nerenberg
2013-05-04 2:00 ` erik quanstrom
2013-05-04 2:03 ` Lyndon Nerenberg
2013-05-04 2:13 ` Kurt H Maier
2013-05-04 2:17 ` erik quanstrom
2013-05-04 5:50 ` Charles Forsyth
2013-05-04 6:22 ` Bakul Shah
2013-05-04 1:16 ` Lyndon Nerenberg [this message]
2013-05-04 1:43 ` erik quanstrom
2013-05-04 1:50 ` Lyndon Nerenberg
2013-05-04 3:41 ` Steven Stallion
2013-05-04 4:19 ` cinap_lenrek
2013-05-04 4:46 ` Lyndon Nerenberg
2013-05-04 3:26 ` Steven Stallion
2013-05-04 6:44 ` erik quanstrom
2013-05-04 18:09 ` Steven Stallion
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=2F31A92B-4011-42DB-9043-D04F6B81A504@orthanc.ca \
--to=lyndon@orthanc.ca \
--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).