I've got Solaris Express Community Edition build 75
(75a) installed on an Asus P5K-E/WiFI-AP (ip35/ICH9R
based) board. CPU=Q6700, RAM=8Gb, disk=Samsung
HD501LJ and (older) Maxtor 6H500F0.
When the O/S is running on bare metal, ie no xVM/Xen
hypervisor, then everything is fine.
When
On 11/2/07, MC [EMAIL PROTECTED] wrote:
I consider myself an early adopter of ZFS and pushed
it hard on this
list and in real life with regards to iSCSI
integration, zfs
performance issues with latency there of, and how
best to use it with
NFS. Well, I finally get to talk more about
I'm confused by this and NexentaStor... wouldn't it be better
to use b77? with:
Heads Up: File system framework changes (supplement to CIFS' head's up)
Heads Up: Flag Day (Addendum) (CIFS Service)
Heads Up: Flag Day (CIFS Service)
caller_context_t in all VOPs - PSARC/2007/218
VFS Feature
On 11/1/07, Nathan Kroenert [EMAIL PROTECTED] wrote:
Tell me - If you watch with an iostat -x 1, do you see bursts of I/O
then periods of nothing, or just a slow stream of data?
I was seeing intermittent stoppages in I/O, with bursts of data on
occasion...
I have seen this with ZFS
I consider myself an early adopter of ZFS and pushed
it hard on this
list and in real life with regards to iSCSI
integration, zfs
performance issues with latency there of, and how
best to use it with
NFS. Well, I finally get to talk more about the
ZFS-based product I've
been beta testing
I've removed half the memory, leaving 4Gb, and rebooted into Solaris xVM, and
re-tried under Dom0. Sadly, I still get a similar problem. With dd
if=/dev/zero of=myfile bs=16k count=15 I get command returning in 15
seconds, and zpool iostat 1 1000 shows 22 records with an IO rate of around
I have a supermicro AOC-SAT2-MV8 and am having some issues getting drives to
work. From what I can tell, my cables are to long to use with SATA2. I got some
drives to work by jumpering them down to sata1, but other drives I can't jumper
without opening the case and voiding the drive warranty.
I have a 9-bay JBOD configured as a raidz2. One of the disks, which is on-line
and fine, needs to be swapped out and replaced. I have been looking though the
zfs admin guide and am confused on how I should go about swapping out. I
though I could put the disk off-line, remove it, put a new
Joe Little wrote:
On 11/2/07, MC [EMAIL PROTECTED] wrote:
I consider myself an early adopter of ZFS and pushed
it hard on this
list and in real life with regards to iSCSI
integration, zfs
performance issues with latency there of, and how
best to use it with
NFS. Well, I finally get to
Hmm, I just repeated this test on my system:
bash-3.2# uname -a
SunOS soe-x4200m2-6 5.11 onnv-gate:2007-11-02 i86pc i386 i86xpv
bash-3.2# prtconf | more
System Configuration: Sun Microsystems i86pc
Memory size: 7945 Megabytes
bash-3.2# prtdiag | more
System Configuration: Sun Microsystems Sun
Chris,
You need to use the zpool replace command.
I recently enhanced this section of the admin guide with more explicit
instructions on page 68, here:
http://opensolaris.org/os/community/zfs/docs/zfsadmin.pdf
If these are hot-swappable disks, for example, c0t1d0, then use this syntax:
#
On Fri, 2007-11-02 at 11:20 -0700, Chris Williams wrote:
I have a 9-bay JBOD configured as a raidz2. One of the disks, which
is on-line and fine, needs to be swapped out and replaced. I have
been looking though the zfs admin guide and am confused on how I
should go about swapping out. I
I've been wrestling with implementing some ZFS mounts for /var and
/usr into a jumpstart setup. I know that jumpstart does know anything
about zfs as in your can't define ZFS volumes or pools in the profile.
I've gone ahead and let the JS do a base install into a single ufs slice
and then
On 11/2/07, Rob Logan [EMAIL PROTECTED] wrote:
I'm confused by this and NexentaStor... wouldn't it be better
to use b77? with:
Heads Up: File system framework changes (supplement to CIFS' head's up)
Heads Up: Flag Day (Addendum) (CIFS Service)
Heads Up: Flag Day (CIFS Service)
Jumpering drives by removing the cover? Do you mean opening the chassis
because they aren't removable from the outside?
Your cable is longer than 1 meter inside of a chasis??
I think sataI is 2 meters and sataII is 1 meter.
As far as a system setting for demoting these to sataI I don't know,
On Fri, 2 Nov 2007, Eric Haycraft wrote:
reformatted
I have a supermicro AOC-SAT2-MV8 and am having some issues getting
drives to work. From what I can tell, my cables are to long to use
with SATA2. I got some drives to work by jumpering them down to
sata1, but other drives I
On Fri, 2 Nov 2007, Peter Schuller wrote:
snip
Does anyone have suggestions on what to choose, that will actually work the
way you want it for JBOD use with ZFS? Or avenus of investigation? Is there
any chance of a lowly consumer getting any information out of LSI? Is there
17 matches
Mail list logo