Thank you very much, Alexander!
The bug is fixed. Binaries and manual are updated.
2012/1/10 Alexander Eremin
> To get working procfs, you must change vfsdef_t vfw's "0" to "VSW_ZMOUNT"
> in /usr/src/uts/common/brand/lx/**procfs/lx_prvfsops.c
>
>
> On Jan 9, 2012, at 11:26 AM, Andrey Sokolov w
Hat to go with h700. Works flawlessly. Had to make single drive raid 0 then
create pool. I tried lsi and dell IT firmware to no avail so I assume it's the
drives also since hooking any sata drive up did indeed work, just something
about the sas drives (not really sas but they are called that).
How did you make out with this? i just recieved the same configuration, except
it is using 2tb western digital drives. I have the same exact errors though.
Did the h710 resolve your issues?
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@open
how did you make out with this? i have the same configuration but my system
came with 2tb WD drives. Otherwise our configuration and symptoms were the
same. Did the h700 resolve this? Woudl an LSI 8 port I card be prefered so
that we can skip the raid 0 setup?
_
Hi!
My manual is written about linux 2.4 support.
2012/1/10 Mads Worsøe Duun
> Hi Andrey
>
> >> http://os-solaris.ru/en/lx-brand-dlya-openindiana-151a/
>>
>> This looks great, is it lx or lx26 brandz?
>
> Mads Worsøe Duun
>
___
OpenIndiana-discuss mail
btw as of november there is likely new firmware for your lsi card. you might
want to take this opportunity to upgrade.
j
Sent from Jasons' hand held
On Jan 10, 2012, at 7:13 AM, Maurilio Longo wrote:
> Geoff,
>
> I've hit this problem several times in the past, with OpenSolaris and then
>
> From: Jason Matthews
> Date: Tue, 10 Jan 2012 08:26:08 -0800
>
>
> you can adjust the disk timeouts in solaris.
Here's an article on how to do that, although it ends with the author
adding this comment "However in testing with failing harddrives (on
mpt_sas anyway), we see that the sd t
you can adjust the disk timeouts in solaris. there are two schools of thought
here:
1) accomodate the extremely long timeouts of cinsumer drives and let the drive
decide whether to report an error back (fail itself out)
2) set the time outs very narrowly and be aggressive in letting zfs fail o
Geoff,
I've hit this problem several times in the past, with OpenSolaris and then
with OpenIndiana.
There are, to my knowledge, no available solutions, it is so by design!
If a disk stops responding the pool waits until after it responds again
(sometimes pulling it out of its slot and then reins
Hi,
I have an OI machine I used for testing, with a zpool shared through CIFS
joined to an AD.
Then I destroyed the zpool to start from scratch, and now I have many logs
complaining
about the AD domain.
How do I let the system forget about that domain?
Thanx,
Gabriele.
___
Hi,
don't know if this is a stupid question.
Is there any way to connect two OI machines through a scsi / sas cable and
execute some
kind of zfs send/recv through it?
Gabriele.
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http
To get working procfs, you must change vfsdef_t vfw's "0" to
"VSW_ZMOUNT"
in /usr/src/uts/common/brand/lx/procfs/lx_prvfsops.c
On Jan 9, 2012, at 11:26 AM, Andrey Sokolov wrote:
http://os-solaris.ru/en/lx-brand-dlya-openindiana-151a/
There are binaries and manual on the site. This fisrt ve
Hi Andrey
>> http://os-solaris.ru/en/lx-brand-dlya-openindiana-151a/
>
> This looks great, is it lx or lx26 brandz?
Mads Worsøe Duun
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openind
13 matches
Mail list logo
