I cannot reproduce this bug. On a DL 380G5 running Hardy Heron:
# array-info -l
array-info v0.13.0 by Benoit Gaussen (b...@trez42.net)
Usage:
array-info -d array_device_path [-a|-l|-A|-c|-s|-L|-h]
Options:
--device=PATH -d path to array device
--all-drives -a show
The kernel I'm using is 2.6.24-25-server.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/374928
Title:
Array-info crash which used with -l option
To manage notifications about this bug go to:
# /usr/sbin/array-info -ld /dev/cciss/c0d0
Unknown Controller id 0x3234103c
Firmware revision : 5.20
Rom revision : 5.20
1 logical drive configured.
Logical drive 0 :
Fault tolerance : RAID 1 (Mirroring)
Size: 136.70 GiB
Platform: x86_64
Kernel: 2.6.24-22-server
System: HP ProLiant DL380 G5
--
Array-info crash which used with -l option
https://bugs.launchpad.net/bugs/374928
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Valgrind output (logfile will be uploaded):
# G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck
--leak-check=full --num-callers=40 --log-file=/tmp/valgrind.log
/usr/sbin/array-info -ld /dev/cciss/c0d1
Unknown Controller id 0x3234103c
Firmware revision : 2.08
# ls -l /dev/cciss/
total 0
brw-rw 1 root disk 104, 0 Feb 3 14:20 c0d0
brw-rw 1 root disk 104, 1 Feb 3 14:20 c0d0p1
brw-rw 1 root disk 104, 2 Feb 3 14:20 c0d0p2
brw-rw 1 root disk 104, 3 Feb 3 14:20 c0d0p3
brw-rw 1 root disk 104, 5 Feb 3 14:20 c0d0p5
brw-rw 1 root
** Attachment added: Valgrind log
http://launchpadlibrarian.net/26589273/valgrind.log
--
Array-info crash which used with -l option
https://bugs.launchpad.net/bugs/374928
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
