Hi,
What sort of compression ratio do you get?
Sigbjorn
On Wed, August 18, 2010 12:59, Hans Foertsch wrote:
Hello,
we use ZFS on Solaris 10u8 as a backup to disk solution with EMC Networker.
We use the standard recordsize 128k and zfs compression.
Dedup we can't use, because of
Wow, not bad!
What is your CPU penalty for enabling compression?
Sigbjorn
On Wed, August 18, 2010 14:11, Paul Kraus wrote:
On Wed, Aug 18, 2010 at 7:51 AM, Peter Tribble peter.trib...@gmail.com
wrote:
I tried this with NetBackup, and decided against it pretty rapidly.
Basically, we
Hello list,
while following this list for more then 1 year, I feel that this list was a
great way to get insights into ZFS. Thank you all for contributing.
Over the last month's I was writing a little whitepaper trying to consolidate
the knowledge collected here. It has now reached a beta
On Wed, Aug 25, 2010 at 3:27 AM, Sigbjorn Lie sigbj...@nixtra.com wrote:
Wow, not bad!
What is your CPU penalty for enabling compression?
Not noticeable on the server side. The NBU servers are M4000 with 4
dual core CPUs, so we have (effectively) 16 CPUs and 16 GB of RAM. The
load does climb
Hi, I've been following these forums for a long time but this is my first post.
I'm looking for some advice on debugging an issue. I've been looking at all
the bug reports and updates though b146 but I can't find a good match. I tried
the fix for 6937998 but it didn't help.
Running Nexenta
What does ::zio_state show?
Dave
On 08/25/10 07:41, Bryan Leaman wrote:
Hi, I've been following these forums for a long time but this is my first post.
I'm looking for some advice on debugging an issue. I've been looking at all
the bug reports and updates though b146 but I can't find a
More info:
::zio_state
ADDRESS TYPE STAGEWAITER
ff02cf248c88 NULL OPEN -
ff02e3dec348 NULL OPEN -
ff02e3e6d6a0 NULL OPEN -
--
Sigbjorn
Stop! Don't do it... it's a waste of time. We tried exactly what
you're thinking of... we bought two Sun/Oracle 7000 series storage
units with 20TB of ZFS storage each planning to use them as a backup
target for Networker. We ran into several issues eventually gave up
the ZFS networker
This is slightly off topic, so I apologise in advance.
I'm investigating the option of offering private cloud storage. I've
found many things which offer features that I want, but nothing that seems
to glue them all together into a useful whole. Thus I would like to pick
your collective
IMHO, may be take look the ZFS appliance (7000 storage) from oracle
it provide GUI for Dtrace based Analytics and WGUI management.
It support 1/2 PB now and will be support much more in near future.
http://www.oracle.com/us/products/servers-storage/039224.pdf
it support local cluster and
not possible now
On 8/25/2010 2:34 PM, Mike DeMarco wrote:
Is it currently or near future possible to shrink a zpool remove a disk
attachment: laotsao.vcf___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
Ray
Supermicro does not support the use of SSDs behind an expander.
You must put the SSD in the head or use an interposer card see here:
http://www.lsi.com/storage_home/products_home/standard_product_ics/sas_sata_protocol_bridge/lsiss9252/index.html
Supermicro offers an interposer card too:
I'm trying to pick between an Intel X25-M or Intel X25-E for a slog
device.
At some point in the future, TRIM support will become available
http://mail.opensolaris.org/pipermail/onnv-notify/2010-July/012674.html.
The X25-M support TRIM while X25-E don't support trim.
Does TRIM support
IMHO, U want -E for ZIL and -M for L2ARC
On 8/25/2010 2:44 PM, Karl Rossing wrote:
I'm trying to pick between an Intel X25-M or Intel X25-E for a slog
device.
At some point in the future, TRIM support will become available
On Wed, Aug 25, 2010 at 11:47:38AM -0700, Andreas Grüninger wrote:
Ray
Supermicro does not support the use of SSDs behind an expander.
You must put the SSD in the head or use an interposer card see here:
Although it's bit much Nexenta oriented, command wise. It's a nice
introduction. I did found one thing, page 28 about the zil. There's no zil
device, the zil can be written to an optional slog device. And the last line
first paragraph, If you can, use memory based SSD devices. At least change
On Tue, Aug 24, 2010 at 9:45 PM, Peter Taps ptr...@yahoo.com wrote:
Essentially, on is just a pseudonym for sha256 and verify is just a
pseudonym for sha256,verify.
Can someone please confirm if this is true?
When dedup was initially announced, dedup=on was fletcher4. There was
a problem
Hi!
I'm running a OSOL box for quite a while and I think ZFS is an amazing
filesystem. As a computer I use a Apple MacMini with USB and FireWire devices
attached. Unfortunately the USB and sometimes the FW devices just die, causing
the whole system to stall, forcing me to do a hard reboot.
I
On Wed, Aug 25, 2010 at 12:29 PM, Dr. Martin Mundschenk
m.mundsch...@me.com wrote:
Well, I wonder what are the components to build a stable system without
having an enterprise solution: eSATA, USB, FireWire, FibreChannel?
I wouldn't consider anything except FC or SAS for a true enterprise
sas-2 with 7200 rpm sas 1tb ot 2tb hdd
--- Original message ---
From: Dr. Martin Mundschenk m.mundsch...@me.com
To: zfs-discuss@opensolaris.org
Sent: 25.8.'10, 15:29
Hi!
I'm running a OSOL box for quite a while and I think ZFS is an amazing
filesystem. As a computer I use a Apple
dtrace is DTrace
On 8/25/2010 3:27 PM, F. Wessels wrote:
Although it's bit much Nexenta oriented, command wise. It's a nice introduction. I did found one
thing, page 28 about the zil. There's no zil device, the zil can be written to an optional slog
device. And the last line first paragraph,
This was the information I got from the distributor but this faq is newer.
Anyway you have still the problems.
When we installed the Intel-X25 we had also problems with timeout.
We replaced the original SUN StorageTek SAS HBA (LSI based, 1068E, newest
firmware) with an original SUN StorageTek
Thank you all for your help.
It appears it is better to use on instead of sha256. This way, you are
letting zfs decide the best option.
Regards,
Peter
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
Update: version 3.2.5 out now, with changes to better support snv_134:
http://forums.halcyoninc.com/showthread.php?t=368
If you've downloaded v3.2.4 and are on 09/06, there is no reason to upgrade.
Regards,
mike.k...@halcyoninc.com
--
This message posted from opensolaris.org
So I don't know if I'm on the right track, but I've been looking at the
threadlist and findstack output from above, specifically this thread which
seems to be what zpool-syspool is stuck on:
0xff000fa05c60::findstack -v
stack pointer for thread ff000fa05c60: ff000fa05860
[
I'm currently using SXCE with eSATA (with an LSI controller) and SAS disks in
my home boxes and they run just fine. The only glitch I had after LU-upgrading
to the latest release is eSATA disk not spinning down any longer when idle.
I export file systems with NFS to my Macs: beware that Mac OS
On Wed, Aug 25, 2010 at 12:29 PM, Dr. Martin Mundschenk
m.mundsch...@me.com wrote:
I'm running a OSOL box for quite a while and I think ZFS is an amazing
filesystem. As a computer I use a Apple MacMini with USB and FireWire devices
attached. Unfortunately the USB and sometimes the FW devices
0n Wed, Aug 25, 2010 at 02:54:42PM -0400, LaoTsao ?? wrote:
IMHO, U want -E for ZIL and -M for L2ARC
Why ?
-Alex
IMPORTANT: This email remains the property of the Department of Defence and is
subject to the jurisdiction of section 70 of the Crimes Act 1914. If you have
-M has larger capacity and L2ARC is mostly for read and not much write
and U also need memory for ARC
L2ARC should be the sze of Ur working dataset
ZIL is mostly for write and U want SSD for better write and longer life
and ZIl may be =1/2 phy memory
regards
On 8/25/2010 9:18 PM,
From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
boun...@opensolaris.org] On Behalf Of Neil Perrin
This is a consequence of the design for performance of the ZIL code.
Intent log blocks are dynamically allocated and chained together.
When reading the intent log we read each
From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
boun...@opensolaris.org] On Behalf Of Dr. Martin Mundschenk
devices attached. Unfortunately the USB and sometimes the FW devices
just die, causing the whole system to stall, forcing me to do a hard
reboot.
Well, I wonder what
On 08/25/10 20:33, Edward Ned Harvey wrote:
From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
boun...@opensolaris.org] On Behalf Of Neil Perrin
This is a consequence of the design for performance of the ZIL code.
Intent log blocks are dynamically allocated and chained together.
Thanks for the feedback, the idea of it is to give people new to ZFS a
understanding of the terms and mode of operations to avoid common problems
(wide stripe pools etc.). Also agreed that it is a little NexentaStor tweaked
:)
I think I have to rework the zil section anyhow because of
33 matches
Mail list logo
