On Jan 7, 2010, at 12:02 PM, Anil wrote:
I *am* talking about situations where physical RAM is used up. So
definitely the SSD could be touched quite a bit when used as a rpool
- for pages in/out.
In the cases where rpool does not serve user data (eg. home directories
and databases are not i
I *am* talking about situations where physical RAM is used up. So definitely
the SSD could be touched quite a bit when used as a rpool - for pages in/out.
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.o
On Thu, 2010-01-07 at 11:07 -0800, Anil wrote:
> There is talk about using those cheap disks for rpool. Isn't rpool
> also prone to a lot of writes, specifically when the /tmp is in a SSD?
Huh? By default, solaris uses tmpfs for /tmp, /var/run,
and /etc/svc/volatile; writes to those filesystems w
On Thu, 7 Jan 2010, Anil wrote:
After spending some time reading up on this whole deal with SSD with "caches"
and how they are prone to data losses during power failures, I need some clarifications...
When you guys say "write cache", do you just really mean the on
board cache (for both read A
Also...
There is talk about using those cheap disks for rpool. Isn't rpool also prone
to a lot of writes, specifically when the /tmp is in a SSD?
What's the real reason to making those cheap SSD as a rpool rather than a L2ARC?
Basically is everyone saying that SSD without NVRAM/capacitors/batt
