What are you running there? snv or OpenSolaris?
Could you try an OpenSolaris 2009.06 live disc and boot directly from that.
Once I was running that build every single hot plug I tried worked flawlessly.
I tried for several hours to replicate the problems that caused me to log that
bug report
Well, I upgraded to b124, disabling ACPI because of [1], and I get exactly the
same behaviour. I've removed the device from the zpool, and tried dd-ing from
the device while I remove it; it still hangs all IO on the system until the
disk is re-inserted.
I'm running the kernel with -v (from diag
On Tue, Oct 13, 2009 at 9:42 AM, Aaron Brady wrote:
> I did, but as tcook suggests running a later build, I'll try an
> image-update (though, 111 > 2008.11, right?)
>
It should be, yes. b111 was released in April of 2009.
--Tim
___
zfs-discuss maili
I did, but as tcook suggests running a later build, I'll try an image-update
(though, 111 > 2008.11, right?)
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinf
Hi Tim, that doesn't help in this case - it's a complete lockup apparently
caused by driver issues.
However, the good news ofr Insom is that the bug is closed because the problem
now appears fixed. I tested it and found that it's no longer occuring in
OpenSolaris 2008.11 or 2009.06.
If you mo
On Tue, Oct 13, 2009 at 8:54 AM, Aaron Brady wrote:
> All's gone quiet on this issue, and the bug is closed, but I'm having
> exactly the same problem; pulling a disk on this card, under OpenSolaris
> 111, is pausing all IO (including, weirdly, network IO), and using the ZFS
> utilities (zfs list
All's gone quiet on this issue, and the bug is closed, but I'm having exactly
the same problem; pulling a disk on this card, under OpenSolaris 111, is
pausing all IO (including, weirdly, network IO), and using the ZFS utilities
(zfs list, zpool list, zpool status) causes a hang until I replace t
On Thu, Feb 12, 2009 at 5:16 PM, Bob Friesenhahn <
bfrie...@simple.dallas.tx.us> wrote:
> On Thu, 12 Feb 2009, Ross Smith wrote:
>
>>
>> As far as I'm concerned, the 7000 series is a new hardware platform,
>>
>
> You are joking right? Have you ever looked at the photos of these "new"
> systems or
On Thu, 12 Feb 2009, Ross Smith wrote:
As far as I'm concerned, the 7000 series is a new hardware platform,
You are joking right? Have you ever looked at the photos of these
"new" systems or compared them to other Sun systems? They are just
re-purposed existing systems with a bit of extra
Heh, yeah, I've thought the same kind of thing in the past. The
problem is that the argument doesn't really work for system admins.
As far as I'm concerned, the 7000 series is a new hardware platform,
with relatively untested drivers, running a software solution that I
know is prone to locking up
On Thu, Feb 12, 2009 at 9:25 AM, Ross wrote:
> This sounds like exactly the kind of problem I've been shouting about for 6
> months or more. I posted a huge thread on availability on these forums
> because I had concerns over exactly this kind of hanging.
>
> ZFS doesn't trust hardware or driver
This sounds like exactly the kind of problem I've been shouting about for 6
months or more. I posted a huge thread on availability on these forums because
I had concerns over exactly this kind of hanging.
ZFS doesn't trust hardware or drivers when it comes to your data - everything
is checksum
> Yup, was an absolute nightmare to diagnose on top of everything else.
> Definitely doesn't
> happen in windows too. I really want somebody to try snv_94 on a Thumper to
> see if you
> get the same behaviour there, or whether it's unique to Supermicro's Marvell
> card.
On a Thumper under S1
I don't think its just b94, I recall this behavior for as long as I've
had the card. I'd also be interested to know if the sun driver team
has ever even tested with this card. I realize its probably not a top
priority, but it sure would be nice to have it working properly.
On 8/20/08, Ross
Ross Smith wrote:
> > > Without fail, cfgadm changes the status from "disk" to "sata-port"
> when I
> > > unplug a device attached to port 6 or 7, but most of the time
> unplugging
> > > disks 0-5 results in no change in cfgadm, until I also attach disk
> 6 or 7.
> >
> > That does seem inco
> > Without fail, cfgadm changes the status from "disk" to "sata-port" when I
> > unplug a device attached to port 6 or 7, but most of the time unplugging
> > disks 0-5 results in no change in cfgadm, until I also attach disk 6 or 7.
>
> That does seem inconsistent, or at least, it's not what I'd
Ross wrote:
> lol, I got bored after 13 pages and a whole day of going back through my
> notes to pick out the relevant information.
>
> Besides, I did mention that I was using cfgadm to see what was connected
> :-p. If you're really interested, most of my troubleshooting notes have
> been posted
lol, I got bored after 13 pages and a whole day of going back through my notes
to pick out the relevant information.
Besides, I did mention that I was using cfgadm to see what was connected :-p.
If you're really interested, most of my troubleshooting notes have been posted
to the forum, but un
Well, when you leave out a bunch of relevant information you also leave
people guessing! :-)
Regardless, is it possibly that all of your testing was done with ZFS and not
just the "raw" disk? If so, it is possible that ZFS isn't noticing the hot
unplugging
of the disk until it tries to access th
On Fri, Aug 15, 2008 at 10:07:31AM -0500, Tim wrote:
> You could always try FreeBSD :)
>
> > Unfortunately for me, Windows doesn't support ZFS... right now it's
> > looking a whole load more stable.
Nope: FreeBSD doesn't have proper power management either.
florin
--
Bruce Schneier expects the
Oh god no, I'm already learning three new operating systems, now is not a good
time to add a fourth.
Ross<-- Windows admin now working with Ubuntu, OpenSolaris and ESX
Date: Fri, 15 Aug 2008 10:07:31 -0500From: [EMAIL PROTECTED]: [EMAIL
PROTECTED]: Re: [zfs-discuss] FW: Supermicro AOC-S
You could always try FreeBSD :)
--Tim
On Fri, Aug 15, 2008 at 9:44 AM, Ross <[EMAIL PROTECTED]> wrote:
> Haven't a clue, but I've just gotten around to installing windows on this
> box to test and I can confirm that hot plug works just fine in windows.
>
> Drives appear and dissappear in device
Haven't a clue, but I've just gotten around to installing windows on this box
to test and I can confirm that hot plug works just fine in windows.
Drives appear and dissappear in device manager the second I unplug the
hardware. Any drive, either controller. So far I've done a couple of dozen
r
I don't have any extra cards lying around and can't really take my server
down, so my immediate question would be:
Is there any sort of PCI bridge chip on the card? I know in my experience
I've seen all sorts of headaches with less than stellar bridge chips.
Specifically some of the IBM bridge chi
This is the problem when you try to write up a good summary of what you found.
I've got pages and pages of notes of all the tests I did here, far more than I
could include in that PDF.
What makes me think it's driver is that I've done much of what you suggested.
I've replicated the exact same
Looking at what you wrote, you claim that hot plug events on ports 6 and 7
generally work, but other ports are not immediately discovered. Since
there is no special code for ports 6 & 7 and no one else has reported this
sort of behavior, it would make me think that you have a hardware issue.
Possi
Ok, I've now reported most of the problems I found, but have additional
information to add to bugs 6667199 and 667208. Can anybody tell me how I go
about reporting that to Sun?
thanks,
Ross
This message posted from opensolaris.org
___
zfs-discuss
27 matches
Mail list logo
