From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
boun...@opensolaris.org] On Behalf Of Eff Norwood
We tried all combinations of OCZ SSDs including their PCI based SSDs and
they do NOT work as a ZIL. After a very short time performance degrades
horribly and for the OCZ drives
From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
boun...@opensolaris.org] On Behalf Of Tristram Scott
When it comes to dumping and restoring filesystems, there is still no
official
replacement for the ufsdump and ufsrestore.
Let's go into that a little bit. If you're piping
Hi Edward,
Do you have a source for the 8KiB block size data? whilst we can't avoid the
SSD controller in theory we can change the smallest size we present to the
SSD to 8KiB fairly easily... I wonder if that would help the controller do a
better job (especially with TRIM)
I might have to do some
On 01/28/11 02:37 PM, Edward Ned Harvey wrote:
Let's go into that a little bit. If you're piping zfs send directly into
zfs receive, then it is an ideal backup method. But not everybody can
afford the disk necessary to do that, so people are tempted to zfs send
to
a file or tape. There are
On 28/01/2011 13:37, Edward Ned Harvey wrote:
From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
boun...@opensolaris.org] On Behalf Of Tristram Scott
When it comes to dumping and restoring filesystems, there is still no
official
replacement for the ufsdump and ufsrestore.
Let's
There's a lot of discussion of dedup performance issues (including problems
backing out of using it which concerns me), but many/most of those involve
relatively limited RAM and CPU configurations. I wanted to see if there is
experience that people could share using it on with higher RAM
Comments below.
On 29 January 2011 00:25, Edward Ned Harvey
opensolarisisdeadlongliveopensola...@nedharvey.com wrote:
This was something interesting I found recently. Apparently for flash
manufacturers, flash hard drives are like the pimple on the butt of the
elephant. A vast majority of
Hi Alex,
Disks that are part of the root pool must contain a valid
slice 0 (this is boot restriction) and the disk names that you
present to ZFS for the root pool must also specify the slice
identifier (s0). For example, instead of this syntax:
# zpool attach -f rpool c0t0d0 c0t2d0
try this
On Jan 27, 2011, at 4:34 AM, Tristram Scott wrote:
I don't disagree that zfs is the better choice, but...
Seriously though. UFS is dead. It has no advantage
over ZFS that I'm aware
of.
When it comes to dumping and restoring filesystems, there is still no official
replacement for the
comment below...
On Jan 28, 2011, at 7:13 AM, Ware Adams wrote:
There's a lot of discussion of dedup performance issues (including problems
backing out of using it which concerns me), but many/most of those involve
relatively limited RAM and CPU configurations. I wanted to see if there is
On Jan 28, 2011, at 12:21 PM, Richard Elling wrote:
On Jan 28, 2011, at 7:13 AM, Ware Adams wrote:
SuperMicro 36 bay case
48 GB RAM
2x 5620 CPU
Hitachi A7K2000 drives for storage
X25-M for l2arc (160 GB)
4x LSI SAS9211-8i
Solaris 11 Express
I apologize for the shortness, but since
On Fri, Jan 28 at 8:25, Edward Ned Harvey wrote:
From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
boun...@opensolaris.org] On Behalf Of Eff Norwood
We tried all combinations of OCZ SSDs including their PCI based SSDs and
they do NOT work as a ZIL. After a very short time
I created a zfs pool with dedup with the following settings:
zpool create data c8t1d0
zfs create data/shared
zfs set dedup=on data/shared
The thing I was wondering about was it seems like ZFS only dedup at the file
level and not the block. When I make multiple copies of a file to the store I
On Fri, Jan 28, 2011 at 01:38:11PM -0800, Igor P wrote:
I created a zfs pool with dedup with the following settings:
zpool create data c8t1d0
zfs create data/shared
zfs set dedup=on data/shared
The thing I was wondering about was it seems like ZFS only dedup at
the file level and not the
On 01/28/11 02:38 PM, Igor P wrote:
I created a zfs pool with dedup with the following settings:
zpool create data c8t1d0
zfs create data/shared
zfs set dedup=on data/shared
The thing I was wondering about was it seems like ZFS only dedup at the file
level and not the block. When I make
On Fri, Jan 28, 2011 at 1:38 PM, Igor P i...@godlike.org wrote:
I created a zfs pool with dedup with the following settings:
zpool create data c8t1d0
zfs create data/shared
zfs set dedup=on data/shared
The thing I was wondering about was it seems like ZFS only dedup at the file
level and
I created a zfs pool with dedup with the following settings:
zpool create data c8t1d0
zfs create data/shared
zfs set dedup=on data/shared
The thing I was wondering about was it seems like ZFS only dedup at
the file level and not the block. When I make multiple copies of a
file to the
Hi,
I am using FreeBSD 8.2 and went to add 4 new disks today to expand my
offsite storage. All was working fine for about 20min and then the new
drive cage started to fail. Silly me for assuming new hardware would be
fine :(
The new drive cage started to fail, it hung the server and the
Hey Cindy...
wanted to post up on here since you've been helping me in email (which I
greatly appreciate!).
I figured it out.. I've done the 'dd' thing before etc. I got it all the way
to where it was complaining that it cannot use a EFI labeled drive. When I did
a prtvtoc | fmthard on the
19 matches
Mail list logo
