On 07/11/2012 08:21 PM, Reginald Beardsley wrote:
>
> Newegg sent me a 10% coupon that will result in a 3 TB drive at my door for
> $135. They track what you look at and if you don't buy right away will offer
> enticements a few days later.
>
I bought 4 of these a couple of weeks ago. :) Oh we
On Wed, Jul 11, 2012 at 07:26:45AM -0400, James Carlson wrote:
> Weird. That looks a whole lot like this bug:
>
> http://wesunsolve.net/bugid/id/6646104
>
> which was fixed long ago.
I quite recently upgraded to oi_151a5, perhaps they missed this in the
regression testing?
--
Richard Jones
I had things configured originally via ifconfig and then unplumbed the
interface and recreated it using ipadm but after a reboot, things went
weird on me. I figure that it's some remnant left over from my original
manual configuration after disabling nwam years ago.
I created two persistent i
After rebooting to oi_151a4, and scrub, clear, scrub, the pool says
that it is completely healthy, no data errors, no device errors, no
repaired bytes (on the second scrub that is, on the first scrub there
were enough checksum errors for it to report all of the devices in one
vdev as degraded). Ad
On Thu, Jul 12, 2012 at 5:41 PM, Timothy Coalson wrote:
> After rebooting to oi_151a4, and scrub, clear, scrub, the pool says
> that it is completely healthy, no data errors, no device errors, no
> repaired bytes (on the second scrub that is, on the first scrub there
> were enough checksum errors
> The DMA alloc failure appears to be caused by improperly constrained
> kernel memory usage. Probably unrelated to the driver in question, but
> could be related to recent ZFS changes. Perhaps ::memstat prior to the
> import and scrub of the pool in question may show something
> significant.
Prio
