Hi,
Please forgive me if my searching-fu has failed me in this case, but
I've been unable to find any information on how people are going about
monitoring and alerting regarding memory usage on Solaris hosts using
ZFS.
The problem is not that the ZFS ARC is using up the memory, but that the
scr
On Tue, May 5, 2009 at 6:09 PM, Ellis, Mike wrote:
> PS: At one point the old JumpStart code was encumbered, and the
> community wasn't able to assist. I haven't looked at the next-gen
> jumpstart framework that was delivered as part of the OpenSolaris SPARC
> preview. Can anyone provide any backg
> use a bunch of 15K SAS drives as L2ARC cache for several TBs of SATA disks?
perhaps... depends on the workload, and if the working set
can live on the L2ARC
> used mainly as astronomical images repository
hmm, perhaps two trays of 1T SATA drives all
mirrors rather than raidz sets of one tra
hey all,
so recently i wrote some zones code to manage zones on zfs datasets.
the code i wrote did things like rename snapshots and promote
filesystems. while doing this work, i found a few zfs behaviours that,
if changed, could greatly simplify my work.
the primary issue i hit was that when ren
Hello Roger,
Tuesday, May 5, 2009, 9:07:22 PM, you wrote:
>
Hello,
Does it make any sense to use a bunch of 15K SAS drives as L2ARC cache for several TBs of SATA disks?
For example:
A STK2540 storage array with this configuration:
Tray 1: Twelve (12) 146 GB @ 15K SAS HDDs.
Tray 2:
How about a generic "zfs options" field in the JumpStart profile?
(essentially an area where options can be specified that are all applied
to the boot-pool (with provisions to deal with a broken-out-var))
That should future proof things to some extent allowing for
compression=x, copies=x, blocksiz
Hello,
Does it make any sense to use a bunch of 15K SAS drives as L2ARC cache
for several TBs of SATA disks?
For example:
A STK2540 storage array with this configuration:
* Tray 1: Twelve (12) 146 GB @ 15K SAS HDDs.
* Tray 2: Twelve (12) 1 TB @ 7200 SATA HDDs.
I was thinking about us
Before I put one in ... anyone else seen one? Seems we support
compression on the root pool but there is no way to enable it at install
time outside of a custom script you run before the installer. I'm
thinking it should be a real install time option, have a jumpstart
keyword, etc. Same with c
On Tue, May 5, 2009 at 12:40 PM, Darren J Moffat wrote:
> Vladimir 'phcoder' Serbinenko wrote:
>
>>
>>
>> On Fri, May 1, 2009 at 10:57 AM, Darren J Moffat
>> > darr...@opensolaris.org>> wrote:
>>
>>Ulrich Graef wrote:
>>
>>According: ZFS encryption
>>
>>Will it be possible to
