Follow up, and current status:
In the morning I cut power (before receiving the 4 replies). Turning it on
again, I got too impatient to get a text screen for diagnostics to show that I
overfilled the keyboard buffer. I forced it off again (to stop the beeps),
then waited longer before attempti
Why wouldn't they try a reboot -d? That would at least get some data in
the form of a crash dump if at all possible...
A power cycle seems a little medieval to me... At least in the first
instance.
The other thing I have noted is that sometimes things to get wedged, and
if you can find where
> From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
> boun...@opensolaris.org] On Behalf Of Yaverot
>
> I'm (still) running snv_134 on a home server. My main pool "tank" filled
up
> last night ( 1G free remaining ).
There is (or was) a bug that would sometimes cause the system to cr
> From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
> boun...@opensolaris.org] On Behalf Of Yaverot
>
> We're heading into the 3rd hour of the zpool destroy on "others".
> The system isn't locked up, as it responds to local keyboard input, and
I bet you, you're in a semi-crashed stat
sigbj...@nixtra.com said:
> I will do some testing on the loadbalance on/off. We have nearline SAS disks,
> which does have dual path from the disk, however it's still just 7200rpm
> drives.
>
> Are you using SATA , SAS or SAS-nearline in your array? Do you have multiple
> SAS connections to your
On Mar 5, 2011, at 9:14 PM, Yaverot wrote:
> I'm (still) running snv_134 on a home server. My main pool "tank" filled up
> last night ( 1G free remaining ).
> So today I bought new drives, adding them one at a time running format
> between each one to see what name they received.
> As I had a
