Maybe to create snapshots "after the fact" as a part of some larger disaster
recovery effort.
(What did my pool/file-system look like at 10am?... Say 30-minutes before the
database barffed on itself...)
With some enhancements might this functionality be extendable into a "poor
man's CDP" offeri
Would adding a dedicated ZIL/SLOG (what is the difference between those 2
exactly? Is there one?) help meet your requirement?
The idea would be to use some sort of relatively large SSD drive of some
variety to absorb the initial write-hit. After hours when things quieit down
(or perhaps during
Bob Says:
"But a better solution is to assign a processor set to run only
the application -- a good idea any time you need a predictable
response."
Bob's suggestion above along with "no interrupts on that pset", and a
fixed scheduling class for the application/processes in question could
Does this all go away when BP-rewrite gets fully resolved/implemented?
Short of the pool being 100% full, it should allow a rebalancing
operation and possible LUN/device-size-shrink to match the new device
that is being inserted?
Thanks,
-- MikeE
-Original Message-
From: zfs-discuss-bo
Wow... that's seriously cool!
Throw in some of this... http://www.nexenta.com/demos/auto-cdp.html and
now we're really getting somewhere...
Nice to see this level of innovation here. Anyone try to employ these
types of techniques on s10? I haven't used nexenta in the past, and I'm
not clear in
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
Try a: zfs get -pH -o value creation
-- MikeE
-Original Message-
From: zfs-discuss-boun...@opensolaris.org
[mailto:zfs-discuss-boun...@opensolaris.org] On Behalf Of Chris Baker
Sent: Friday, August 28, 2009 10:52 AM
To: zfs-discuss@opensolaris.org
Subject: [zfs-discuss] Snapshot creati
While the snapshot isn't RW, the clone is and would certainly be helpful
in this case
Isn't the whole idea to:
0) boot into single-user/boot-archive if you're paranoid (or just quiess
and clone if you feel lucky)
1) "clone" the primary OS instance+relevant-slices & boot into the
primary OS
2)
This is probably a good place to start.
http://blogs.sun.com/realneel/entry/zfs_and_databases
Please post back to the group with your results, I'm sure many of us are
interested.
Thanks,
-- MikeE
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of homeru
Also the "unmirrored memory" for the rest of the system has ECC and
ChipKill, which provides at least SOME protection against random
bit-flips.
--
Question: It appears that CF and friends would make a descent live-boot
(but don't run on me like I'm a disk) type of boot-media due to the
limited wr
ght try to
use a CF-boot-option in their environment.
Good thread, lets bat this around some more.
-- MikeE
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 29, 2007 9:48 PM
To: Ellis, Mike
Cc: Carson Gaspar; zfs-discuss@opensolaris.or
ght try to
use a CF-boot-option in their environment.
Good thread, lets bat this around some more.
-- MikeE
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 29, 2007 9:48 PM
To: Ellis, Mike
Cc: Carson Gaspar; zfs-discuss@opensolaris.or
At what Solaris10 level (patch/update) was the "single-threaded
compression" situation resolved?
Could you be hitting that one?
-- MikeE
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Roch - PAE
Sent: Tuesday, June 26, 2007 12:26 PM
To: Roshan Perera
Yup...
With Leadville/MPXIO targets in the 32-digit range, identifying the "new
storage/LUNs" is not a trivial operatrion.
-- MikeE
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Russ
Petruzzelli
Sent: Monday, September 17, 2007 1:51 PM
To: zfs-discus
Use zpool replace to swap one side of the mirror with the iscsi lun.
-- mikee
- Original Message -
From: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
To: zfs-discuss@opensolaris.org
Sent: Tue Jan 15 08:46:40 2008
Subject: Re: [zfs-discuss] Moving zfs to an iscsci equallogic LUN
What would be
Could someone kindly provide some details on using a zvol in sparse-mode?
Wouldn't the COW nature of zfs (assuming COW still applies on ZVOLS) quickly
erode the sparse nature of the zvol?
Would sparse data-presentation only work by delegating a part of a zpool to a
zone, but that's at the file-
I like the link you sent along... They did a nice job with that.
(but it does show that mixing and matching vastly different drive-sizes
is not exactly optimal...)
http://www.drobo.com/drobolator/index.html
Doing something like this for ZFS allowing people to create pools by
mixing/match
The FAQ document (
http://opensolaris.org/os/community/zfs/boot/zfsbootFAQ/ ) has a
jumpstart profile example:
install_type initial_install
pool newpool auto auto auto mirror c0t0d0 c0t1d0
bootenv installbe bename sxce_xx
The B90 jumpstart "check" program (SPARC) flags th
In addition to the standard "containing the carnage" arguments used to
justify splitting /var/tmp, /var/mail, /var/adm (process accounting
etc), is there an interesting use-case where would one split out /var
for "compression reasons" (as in, turn on compression for /var so that
process accounting,
Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 05, 2008 1:56 PM
To: Ellis, Mike
Cc: ZFS discuss
Subject: Re: [zfs-discuss] ZFS root finally here in SNV90
Mike,
As we discussed, you can't currently break out other datasets besides
/var. I'll add thi
It's a valid use case in the high-end enterprise space.
While it probably makes good sense to use ZFS for snapshot creation,
there are still cases where array-based snapshots/clones/BCVs make
sense. (DR/Array-based replication, data-verification, separate
spindle-pool, legacy/migration reasons, an
Hey Tony...
When (properly) doing Array-based snapshots/BCVs with
EMC/Hitachi/what-have you arrays, you create "lun groups" out of the
luns you're interested in snappin'. You then perform snapshot/clone
operations on that "lun group" which will make it atomic across all
members of that group.
Wh
22 matches
Mail list logo
