Andrea Righi a écrit :
Roger Chevalier wrote:
As far as I have looked to the source, it seems that function sub
collect_disks in si_prepareclient is not compliant to what happen on our
servers:
sistest4:~# cat /proc/partitions
major minor #blocks name rio rmerge rsect ruse wio wmerge wsect
wuse running use aveq
104 0 71126640 cciss/disc0/disc 6816 118816 312026 11080 2571
2713 42258 36660 0 16140 47740
104 1 174804 cciss/disc0/part1 24 556 1160 70 8 1 18 130 0 190 200
104 2 5325195 cciss/disc0/part2 4 3 32 30 0 0 0 0 0 30 30
104 3 65626639 cciss/disc0/part3 6783 118242 310794 10970 2563
2712 42240 36530 0 16020 47500
104 16 71126640 cciss/disc1/disc 5 11 32 0 0 0 0 0 0 0 0
104 32 71126640 cciss/disc2/disc 5 11 32 20 0 0 0 0 0 20 20
There is no match in ths function, so may the issue be here ?? Find the
other answer below inline.
The problem here is that your 2.4 kernel is using the old devfs naming
schema. You could try with the following patch that should resolve, but
you're forced to use UYOK, since the standard BOEL doens't support this
naming schema (probably the installation would work if you re-create the
autoinstall script with si_mkautoinstallscript --autodetect-disks ...,
but the 2.4 kernel in your distro should support both naming schema:
devfs and standard /dev/cciss/c0d*p*).
-Andrea
---
Index: sbin/si_prepareclient
===================================================================
--- sbin/si_prepareclient (revision 4289)
+++ sbin/si_prepareclient (working copy)
@@ -784,7 +784,8 @@
open(IN,"</proc/partitions") or croak("Couldn't open /proc/partitions for reading.");
while(<IN>) {
- if(/(\S*c[0-9]+d[0-9]+)p[0-9]+/) { # hardware raid devices (/dev/rd/c?d?, /dev/ida/c?d?, /dev/cciss/c?d?)
+ if ((/(\S*c[0-9]+d[0-9]+)p[0-9]+/) or (/(\S*\/disc[0-9]+\/disc)/)) {
+ # hardware raid devices (/dev/rd/c?d?, /dev/ida/c?d?, /dev/cciss/c?d?)
my $disk = $1;
unless(defined $excluded_disks{$disk}) {
$disks->{HWRAID}->{$disk}++;
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
sisuite-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-users
Thanks Andrea for the patch, some improvement, but still not really
working, got this error:
/dev/cciss/disc0/disc: No such file or directory
sfdisk: cannot open /dev/cciss/disc0/disc for reading
Using "sfdisk" to gather information about disk:
/dev/cciss/disc0/disc
Looking at devices is /dev , hardware device for first disk is
/dev/cciss/c0d0p0
(I don't know if this is sarge behaviour or cciss on 2.4 behaviour?)
|
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
sisuite-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-users
