mastermind's weblog - Comments

GreyCat: LSIlogic MegaRAID SAS and the self explaining CLI

nospam@example.com (GreyCat) — Wed, 23 Sep 2009 13:07:51 +0200

You might be interested in Einarc - a much more straightforward wrapper solution for LSI MegaCli and many other crappy proprietary utiliies. You can check it out at http://www.inquisitor.ru/doc/einarc

For example, monitoring RAID with einarc boils down to:

einarc logical list | grep -v 'normal$'

And it's the same for *every* RAID, not only for LSI.

Frank Bergmann: LSIlogic MegaRAID SAS and the self explaining CLI

nospam@example.com (Frank Bergmann) — Wed, 02 Sep 2009 19:05:15 +0200

Hi,

There is great documentation available, but it's kind of hidden:

- Cheat Sheet:
http://tools.rapidsoft.de/perc/

- LSI MegaRAID SAS User's Guide:
http://www.lsi.com/DistributionSystem/AssetDocument/files/docs/techdocs/storage_stand_prod/sas/mr_sas_sw_ug.pdf

Enjoy!
Frank

Stefan Kaltenbrunner: factory defaulting an IBM Remote Supervisor II Slimline (RSAII) card

nospam@example.com (Stefan Kaltenbrunner) — Tue, 25 Aug 2009 18:32:53 +0200

as said in my post you need to compile and install the USB daemon before you can change the password. If you did that already it would be interesting to see what exact error you are getting

Bostjan: factory defaulting an IBM Remote Supervisor II Slimline (RSAII) card

nospam@example.com (Bostjan) — Tue, 18 Aug 2009 18:31:20 +0200

Do you maybe remember how you configure that connection to RSA was successful?

I'm trying to reset RSA2 Slimline password with ASU, but i can't make it to connect.

I'm having Debian Lenny (Amd64)

If you can help me, it will really appreciate it.

dim: Benchmarking 8.4 - Chapter 1/Read-Only workloads

nospam@example.com (dim) — Sun, 14 Jun 2009 13:18:24 +0200

To overcome pgbench scalability limit, I'd advice using tsung. Bug me when you see me there on IRC if you want me to help through setting up the client etc.

With modern Erlang version (stable and all), you can have 50 000 concurrent TCP connected clients without a problem, you typically run out of TCP ports before erlang scalability level is reached, I've been told by tsung author.

Stefan Kaltenbrunner: Benchmarking 8.4 - Chapter 1/Read-Only workloads

nospam@example.com (Stefan Kaltenbrunner) — Sat, 13 Jun 2009 10:00:30 +0200

at this transaction rates (ie up to 140000 queries/s) the additional latency involved in going over tcp/ip from another box is significant and seems to hide some of the pgbench issues. However I will see if I can get some numbers as well.

Stefan Kaltenbrunner: Benchmarking 8.4 - Chapter 1/Read-Only workloads

nospam@example.com (Stefan Kaltenbrunner) — Sat, 13 Jun 2009 09:56:42 +0200

the first chart actually contains numbers at scale=1000 which I actually did to see if shared_buffers less than the size of the database would have a noticable effect in this scenario.

Greg Smith: Benchmarking 8.4 - Chapter 1/Read-Only workloads

nospam@example.com (Greg Smith) — Sat, 13 Jun 2009 07:19:47 +0200

The largest database test set used here (scale=100, about 1.6GB) is smaller than the 2GB shared_buffers already allocated. Giving it more RAM will just slow things down unless the working set of data is also increased.

slava: Benchmarking 8.4 - Chapter 1/Read-Only workloads

nospam@example.com (slava) — Sat, 13 Jun 2009 01:57:52 +0200

given that the server has 34GB of RAM would you consider allocating more memory to shared buffers? I would try 5-7GB.
This setting most likely wouldn't change the test results and I know that it's very often advised to keep shared buffers small, but given the amount of RAM available nowadays and efficiency of nehalem architecture (i.e. built-in memory controller and fasr QPI bus) I would be interested to see if more memory dedicated to shared buffers is appropriate. thanks.

Euler Taveira de Oliveira: Benchmarking 8.4 - Chapter 1/Read-Only workloads

nospam@example.com (Euler Taveira de Oliveira) — Sat, 13 Jun 2009 00:31:53 +0200

Hi Stefan,

Could you retest it with pgbench in another machine? As you said, the scaling problems is a known issue in pgbench. IIRC you posted this same analysis for 8.3; is it the same machine? Could you show us the comparison?

Thanks for testing.

Prashant: LSIlogic MegaRAID SAS and the self explaining CLI

nospam@example.com (Prashant) — Thu, 12 Feb 2009 16:50:37 +0100

Hi,
Thanks for all the info you've added for the MegaCli, can you please send me tha link to the nagios plugins.
Thanks
Prashant

Anon: LSIlogic MegaRAID SAS and the self explaining CLI

nospam@example.com (Anon) — Fri, 14 Nov 2008 19:23:37 +0100

Oh help! I've been blindsided by this nonsese. I have a server that's just started acting odd, and I'd like to verify that the @#$$% drives are alive, thank you very much. @#$%$^% you LSI!

Martin: LSIlogic MegaRAID SAS and the self explaining CLI

nospam@example.com (Martin) — Thu, 16 Oct 2008 16:25:08 +0200

Yes, you don't need the '-' option symbol. What's even more confusing, is that some commands do not work if you add the dash. Let's say I want to get some information about the 4th drive, first adapter, first enclosure: megacli -pdInfo -PhysDrv[0:3] -a0, this doesn't work, no matter what. But specifying this: megacli -pdInfo PhysDrv[0:3] -a0 works. Actually I just noticed that this must be a bug, since ver. 1.01.39 has this bug, but it doesn't matter with version 2.0.0.15

Andreas 'ads' Scherbaum: Nagios conference 2008

nospam@example.com (Andreas 'ads' Scherbaum) — Sat, 13 Sep 2008 16:48:49 +0200

Well done ;-)
Thanks for taking this over.

Andreas

Stephen Dowdy: LSIlogic MegaRAID SAS and the self explaining CLI

nospam@example.com (Stephen Dowdy) — Mon, 16 Jun 2008 18:28:03 +0200

FWIW,

While the megarc & megacli tools are documented in mixed case, they are actually case-insensitive (yay! that helps make a completely unusable tool only *very* unusable). Also, megacli doesn't even need the '-' option symbol.

And, megarc has DIFFERENT help output if you use '?' versus '-?' (megacli has the same output)
[root MegaRAID]# ./megarc ? | wc -l
103
[root MegaRAID]# ./megarc -? | wc -l
58

These are the only tools that i HAVE to run the help before i type EVERY command because they commands are SOOOO twisted. Also, going from megarc to megacli the standard equivalent command options completely change.

For the log files, "-NoLog" can be used to NOT create/append log files. (in a sane world, log files would be created if you ASKED for them)

One final hint. On many systems, you can use "/dev/stdout" (or /dev/fd/1) as an arg to the "-f" option to get the output to the screen instead of creating a log file.