* On 02 Feb 2010, Richard Elling wrote:
>
> This behaviour has changed twice. Long ago, the pools would autoexpand.
> This is a bad thing, by default, so it was changed such that the expansion
> would only occur on pool import (around 3-4 years ago). The autoexpand
> property allows you to expa
* On 02 Feb 2010, Orvar Korvar wrote:
> Ok, I see that the chassi contains a mother board. So never mind that
> question.
>
> Another q: Is it possible to have large chassi with lots of drives,
> and the opensolaris in another chassi, how do you connect them both?
The J4500 and most other storage
* On 02 Feb 2010, Darren J Moffat wrote:
>
> zpool get autoexpand test
This seems to be a new property -- it's not in my Solaris 10 or
OpenSolaris 2009.06 systems, and they have always expanded immediately
upon replacement. In what build number or official release does
autoexpand appear, and do
> guess the upshot is that if one were to daily rsync data to an zfs
> filesystem, the changes wrought there by rsync would be reflected in
> zfs snapshots, maybe timed to happen right after the rsync runs, as
> these new blocks covering only the deltas... I don't really know what
> deltas are... b
* On 07 Apr 2009, Michael Shadle wrote:
>
> Now quick question - if I have a raidz2 named 'tank' already I can
> expand the pool by doing:
>
> zpool attach tank raidz2 device1 device2 device3 ... device7
>
> It will make 'tank' larger and each group of disks (vdev? or zdev?)
> will be dual pari
* On 28 Mar 2009, Peter Tribble wrote:
> The choice of raidz1 versus raidz2 is another matter. Given that
> you've already got raidz1, and you can't (yet) grow that or expand
> it to raidz2, then there doesn't seem to be much point to having the
> second half of your storage being more protected.
DE:
I think that a big part of the reason you're getting the responses you
do is not arrogance from Sun or us kool-aid drinkers, but your own tone
and attitude. You didn't ask for help in your initial message at all.
The entire post was a diatribe against Sun and ZFS which was based on
your exper
> too many words wasted, but not a single word, how to restore the data.
>
> I have read the man pages carefully. But again: there's nothing said,
> that on USB drives zfs umount pool is not allowed.
You misunderstand. This particular point has nothing to do with USB;
it's the same for any ZFS en
> > Would there be an advantage to using 4GB USB memory sticks on a home
> > system for zil and l2arc?
>
> Probably not. Most USB devices are slower than SATA disks.
Moreover, all USB devices are alower than most SATA disks.
--
-D.d...@uchicago.eduNSITUniversity of Chicago
> nevermind, i will just get a Promise array.
Don't. I don't normally like to badmouth vendors, but my experience
with Promise was one of the worst in my career, for reasons that should
be relevant other ZFS-oriented customers.
We ordered a Promise array because their tech sheet said Solaris was
I have a feeling I pushed people away with a long message. Let me
reduce my problem to one question.
> # zpool import -f z
> cannot import 'z': one or more devices is currently unavailable
>
>
> 'zdb -l' shows four valid labels for each of these disks except for the
> new one. Is this what "un
There are a lot of hits for this error in google, but I've had trouble
identifying any that resemble my situation. I apologize if you've
answered it before. If it's better for me to open a case with Sun
Support, I can do that, but I'm hoping to cheat my way around the system
so that I don't have
12 matches
Mail list logo
