There is something more to consider with SSDs uses as a cache device.
why use SATA as the interface? perhaps
http://www.tgdaily.com/content/view/34065/135/
would be better? (no experience)
cards will start at 80 GB and will scale to 320 and 640 GB next year.
By the end of 2008, Fusion io also
Rob Logan wrote:
There is something more to consider with SSDs uses as a cache device.
why use SATA as the interface? perhaps
http://www.tgdaily.com/content/view/34065/135/
would be better? (no experience)
cards will start at 80 GB and will scale to 320 and 640 GB next year.
By the end of
This past weekend, but holiday was ruined due to a log device
replacement gone awry.
I posted all about it here:
http://jmlittle.blogspot.com/2008/05/problem-with-slogs-how-i-lost.html
In a nutshell, an resilver of a single log device with itself, due to
the fact one can't remove a log device
On Mon, May 26, 2008 at 6:10 AM, Gerard Henry [EMAIL PROTECTED] wrote:
hello all,
i have indiana freshly installed on a sun ultra 20 machine. It only does nfs
server. During one night, the kernel had crashed, and i got this messages:
May 22 02:18:57 ultra20 unix: [ID 836849 kern.notice]
Gerard Henry wrote:
hello all,
i have indiana freshly installed on a sun ultra 20 machine. It only does nfs
server. During one night, the kernel had crashed, and i got this messages:
May 22 02:18:57 ultra20 unix: [ID 836849 kern.notice]
May 22 02:18:57 ultra20
On Tue, May 27, 2008 at 12:44 PM, Rob Logan [EMAIL PROTECTED] wrote:
There is something more to consider with SSDs uses as a cache device.
why use SATA as the interface? perhaps
http://www.tgdaily.com/content/view/34065/135/
would be better? (no experience)
cards will start at 80 GB and
Yeah, I noticed this the other day while I was working on an unrelated
problem. The basic problem is that log devices are kept within the
normal vdev tree, and are only distinguished by a bit indicating that
they are log devices (and is the source for a number of other
inconsistencies that Pwel
On May 27, 2008, at 1:44 PM, Rob Logan wrote:
There is something more to consider with SSDs uses as a cache device.
why use SATA as the interface? perhaps
http://www.tgdaily.com/content/view/34065/135/
would be better? (no experience)
We are pretty happy with RAMSAN SSD's (ours is RAM
On May 23, 2008, at 22:21, Richard Elling wrote:
Consider a case where you might use large, slow SATA drives (1 TByte,
7,200 rpm)
for the main storage, and a single small, fast (36 GByte, 15krpm)
drive
for the
L2ARC. This might provide a reasonable cost/performance trade-off.
Ooh,
On Tue, May 27, 2008 at 1:50 PM, Eric Schrock [EMAIL PROTECTED] wrote:
Yeah, I noticed this the other day while I was working on an unrelated
problem. The basic problem is that log devices are kept within the
normal vdev tree, and are only distinguished by a bit indicating that
they are log
Joe -
We definitely don't do great accounting of the 'vdev_islog' state here,
and it's possible to create a situation where the parent replacing vdev
has the state set but the children do not, but I have been unable to
reproduce the behavior you saw. I have rebooted the system during
resilver,
On Tue, May 27, 2008 at 4:50 PM, Eric Schrock [EMAIL PROTECTED] wrote:
Joe -
We definitely don't do great accounting of the 'vdev_islog' state here,
and it's possible to create a situation where the parent replacing vdev
has the state set but the children do not, but I have been unable to
Joe Little wrote:
On Tue, May 27, 2008 at 4:50 PM, Eric Schrock [EMAIL PROTECTED] wrote:
Joe -
We definitely don't do great accounting of the 'vdev_islog' state here,
and it's possible to create a situation where the parent replacing vdev
has the state set but the children do not, but I have
I'm using a gigabyte I-RAM card with cheap memory for my slog device with great
results. Of course I don't have as much memory as you do in my project box. I
also want to use the left over space on the I-ram and dual purpose it for a
readzilla cache device and slog. Picked it up off ebay
14 matches
Mail list logo
