Hi Hannes,
I guess it was only a matter of time before you found this thread (-:
I've had a look at the source through git and I must admit I'm fairly
lost - I was a qualified (embedded) software engineer at one stage,
but I've dropped that in favor of systems / network administration.
First
Sparqz wrote:
On Feb 29, 9:41 am, Mike Christie [EMAIL PROTECTED] wrote:
Sparqz wrote:
On Feb 28, 12:09 pm, Sparqz [EMAIL PROTECTED] wrote:
I can repeat the problem with bonnie on SuSE 10 SP1
I can also repeat the problem with HP's open-
iscsi-2.0.707-0.25b.src.rpm (supplied from
Sparqz wrote:
The default run for bonnie++ on a server with 32GB of memory takes
forever...! But it looks like the performance is up on the production
server (Still SLES10 SP1) with the semi-stable release from the open-
iscsi website.
Version 1.03 --Sequential Output--
Mike Christie wrote:
Sparqz wrote:
On Feb 29, 9:41 am, Mike Christie [EMAIL PROTECTED] wrote:
Sparqz wrote:
On Feb 28, 12:09 pm, Sparqz [EMAIL PROTECTED] wrote:
I can repeat the problem with bonnie on SuSE 10 SP1
I can also repeat the problem with HP's open-
iscsi-2.0.707-0.25b.src.rpm
Hi Mike,
Could you try this tarball
http://kernel.org/pub/linux/kernel/people/mnc/open-iscsi/releases/ope...
And try it with different IO schedulers by doing
cat /sys/block/sdb/queue/scheduler
echo $ONE_OF_THE_VALUES_FROM_THE_CAT /sys/block/sdb/queue/scheduler
Please be carefull with
FYI: If anyone is keen to have a look at my bugzilla submission at
SuSE
https://bugzilla.novell.com/show_bug.cgi?id=366492
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
open-iscsi group.
To post to this group,
The default run for bonnie++ on a server with 32GB of memory takes
forever...! But it looks like the performance is up on the production
server (Still SLES10 SP1) with the semi-stable release from the open-
iscsi website.
Version 1.03 --Sequential Output-- --Sequential Input-
Here's some output from tcpdump, this is a bunch of duplicate acks, I
don't think these are normal... unless anyone can tell me different?
192.168.50.8 is the iSCSI target, 192.168.50.11 is the initiator
11:14:45.391670 IP 192.168.50.8.3260 192.168.50.11.58035: P
3143284:3144176(892) ack 193
On Wed, Feb 20, 2008 at 06:09:50PM -0800, Sparqz wrote:
Hi All,
I have a nasty problem with open-iscsi on SLES10 + an Infortrend iSCSI
array.
Basically it looks like everything goes wrong as soon as the read/
write load becomes heavy, although network dumps suggest the problem
is
Hi Pasi,
My setup:
1x HP DL585 - SLES10 x86_64
1x HP DL585 - RHEL4 x86_64
1x HP DL380 - SLES10 i586
SLES10 or SLES10SP1 ?
SLES10SP1
Have you tried installing and using the latest open-iscsi from open-iscsi.org
?
2x Cisco 2960G (gigabit) switches
2x Infortrend A16E-G2130-4
Hi All,
I have a nasty problem with open-iscsi on SLES10 + an Infortrend iSCSI
array.
Basically it looks like everything goes wrong as soon as the read/
write load becomes heavy, although network dumps suggest the problem
is always there, it just goes critical when the load is too heavy.
My
11 matches
Mail list logo
