Hi Garrett,
Since my problem did turn out to be a debug kernel on my compilations,
I booted back into the Nexanta 3 RC2 CD and let a scrub run for about
half an hour to see if I just hadn't waited long enough the first time
around. It never made it past 159 MB/s. I finally rebooted into my
145
Hi,
My bits were originally debug because I didn't know any better. I thought I
had then
recompiled without debug to test again, but I didn't realize until just now the
packages
end up in a different directory (nightly vs nightly-nd) so I believe after
compiling
non-debug I just reinstalled
gave it in my
prior tests
for the scrub to reach it's normal speed, although I can't do that until this
evening
when I'm home again.
Chad
On Wed, Jul 21, 2010 at 09:44:42AM -0700, Chad Cantwell wrote:
Hi,
My bits were originally debug because I didn't know any better. I thought I
had
On Mon, Jul 19, 2010 at 07:01:54PM -0700, Chad Cantwell wrote:
On Tue, Jul 20, 2010 at 10:54:44AM +1000, James C. McPherson wrote:
On 20/07/10 10:40 AM, Chad Cantwell wrote:
fyi, everyone, I have some more info here. in short, rich lowe's 142 works
correctly (fast) on my hardware, while
.
Thanks,
Chad
On Tue, Jul 20, 2010 at 08:39:42AM +0100, Robert Milkowski wrote:
On 20/07/2010 07:59, Chad Cantwell wrote:
I've just compiled and booted into snv_142, and I experienced the same slow
dd and
scrubbing as I did with my 142 and 143 compilations and with the Nexanta 3
RC2 CD
No, this wasn't it. A non debug build with the same NIGHTLY_OPTIONS
at Rich Lowe's 142 build is still very slow...
On Tue, Jul 20, 2010 at 09:52:10AM -0700, Chad Cantwell wrote:
Yes, I think this might have been it. I missed the NIGHTLY_OPTIONS variable
in
opensolaris and I think
On Tue, Jul 20, 2010 at 10:45:58AM -0700, Brent Jones wrote:
On Tue, Jul 20, 2010 at 10:29 AM, Chad Cantwell c...@iomail.org wrote:
No, this wasn't it. A non debug build with the same NIGHTLY_OPTIONS
at Rich Lowe's 142 build is still very slow...
On Tue, Jul 20, 2010 at 09:52:10AM -0700
with how I'm compiling the kernel that makes the hardware not
perform up to its specifications with a zpool, and possibly the Nexanta 3
RC2 ISO has the same problem as my own compilations.
Chad
On Tue, Jul 06, 2010 at 03:08:50PM -0700, Chad Cantwell wrote:
Hi all,
I've noticed something strange
On Tue, Jul 20, 2010 at 10:54:44AM +1000, James C. McPherson wrote:
On 20/07/10 10:40 AM, Chad Cantwell wrote:
fyi, everyone, I have some more info here. in short, rich lowe's 142 works
correctly (fast) on my hardware, while both my compilations (snv 143, snv
144)
and also the nexanta 3 rc2
On Mon, Jul 19, 2010 at 06:00:04PM -0700, Brent Jones wrote:
On Mon, Jul 19, 2010 at 5:40 PM, Chad Cantwell c...@iomail.org wrote:
fyi, everyone, I have some more info here. in short, rich lowe's 142 works
correctly (fast) on my hardware, while both my compilations (snv 143, snv
144
a configuration parameter.
I'm not sure offhand if installing source-compiled ON builds from a bfu'd
rpool is supported, although I suppose it's simple enough to try.
Thanks,
Chad Cantwell
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http
partly since it has PCI-X slots and I thought
those
might be useful for AOC-SAT2-MV8 cards if I couldn't shake the mpt issues, but
now
that the mpt issues are gone I can continue with that controller if I want.
Thanks everyone for your help,
Chad
On Sun, Dec 06, 2009 at 11:12:50PM -0800, Chad
Thanks for the info on the yukon driver. I realize too many variables makes
things impossible to determine, but I had made these hardware changes awhile
back, and they seemed to work fine at the time. Since they aren't now, even
in the older OpenSolaris (i've tried 2009.06 and 2008.11 now), the
to resort to motherboard
swapping again.
Chad
On Thu, Dec 03, 2009 at 10:44:53PM -0800, Chad Cantwell wrote:
I eventually performed a few more tests, adjusting some zfs tuning options
which had no effect, and trying the
itmpt driver which someone had said would work, and regardless my system
I was under the impression that the problem affecting most of us was introduced
much later than b104,
sometime between ~114 and ~118. When I first started using my LSI 3081 cards,
they had the IR firmware
on them, and it caused me all kinds of problems. The disks showed up but I
couldn't
better and wipe again in the event
of problems)
Chad
On Tue, Dec 01, 2009 at 03:06:31PM -0800, Chad Cantwell wrote:
To update everyone, I did a complete zfs scrub, and it it generated no errors
in iostat, and I have 4.8T of
data on the filesystem so it was a fairly lengthy test. The machine also
errors
fairly rapidly)
Thanks again for your help. Sorry for wasting your time if the previously
posted workaround fixes things.
I'll let you know tomorrow either way.
Chad
On Tue, Dec 01, 2009 at 05:57:28PM +1000, James C. McPherson wrote:
Chad Cantwell wrote:
After another crash I checked
, 2009 at 12:13:36AM -0800, Chad Cantwell wrote:
I don't think the hardware has any problems, it only started having errors
when I upgraded OpenSolaris.
It's still working fine again now after a reboot. Actually, I reread one of
your earlier messages,
and I didn't realize at first when you
upgrades it creates a second root environment, but my forte isn't
solaris so I
just reformatted the root device)
On Tue, Dec 01, 2009 at 08:09:32AM -0500, Mark Johnson wrote:
Chad Cantwell wrote:
Hi,
I was using for quite awhile OpenSolaris 2009.06
with the opensolaris-provided mpt driver
though, I'm sure it would
generate errors and crash again.
Chad
On Tue, Dec 01, 2009 at 12:29:16AM -0800, Chad Cantwell wrote:
Well, ok, the msi=0 thing didn't help after all. A few minutes after my last
message a few errors showed
up in iostat, and then in a few minutes more the machine
Hi,
Sorry for not replying to one of the already open threads on this topic;
I've just joined the list for the purposes of this discussion and have
nothing in my client to reply to yet.
I have an x86_64 opensolaris machine running on a Core 2 Quad Q9650
platform with two LSI SAS3081E-R PCI-E 8
Hi,
I just posted a summary of a similiar issue I'm having with non-Sun hardware.
For the record, it's in a Chenbro RM41416 chassis with 4 chenbro SAS backplanes
but no expanders (each backplane is 4 disks connected by SFF-8087 cable). Each
of my LSI brand SAS3081E PCI-E cards is connected to
:34PM +1000, James C. McPherson wrote:
Chad Cantwell wrote:
Hi,
Sorry for not replying to one of the already open threads on this topic;
I've just joined the list for the purposes of this discussion and have
nothing in my client to reply to yet.
I have an x86_64 opensolaris machine running
On Tue, Dec 01, 2009 at 01:43:06PM +1000, James C. McPherson wrote:
Chad Cantwell wrote:
Hi,
Replied to your previous general query already, but in summary, they are in
the
server chassis. It's a Chenbro 16 hotswap bay case. It has 4 mini
backplanes
that each connect via an SFF-8087
0 0
c2t10d0 ONLINE 0 0 0
errors: No known data errors
#
On Mon, Nov 30, 2009 at 06:46:13PM -0800, Chad Cantwell wrote:
Hi,
Sorry for not replying to one of the already open threads on this topic;
I've just joined the list for the purposes of this discussion
25 matches
Mail list logo
