|
DFCT
ID:
|
|
LSID100031919
|
|
Headline:
|
|
SPY
crashing
|
|
Version
Reported:
|
|
7.24.24
|
|
Description:
|
|
"Spy
issue (RHEL 4 32-bit) At certain configuration, do plug-out and plug-in
action will cause spy stop the service."
|
|
Steps
To Reproduce:
|
|
Slot 0
and Slot 1: Raid 1
Slot 2: raid 0
1. Install RHEL 4 32-bit on Slot 0.
2. After OS install finish, install Spy rpm package and startup the spy
service.
3. Use command "pidof Spy" to confirm the
service is running.
4. Plug-out slot 2 HDD and wait 20 seconds.
5. Plug-in slot2 the same HDD and wait 20 seconds.
6. Use command "pidof Spy" to confirm the
service. But the service is stop.
|
|
Resolution
Description:
|
|
The root
cause for this problem is same as for DFCT # LSID100031921 which is below:
On removing Physical Drive,
Spy recreates its own repository. While Recreating Spy
repository, Spy was removing the drive from internal structures, and then
recreating
an arry repository to reflect which all drives
belong to which array.
Here Spy is now getting the null pointer for the removed drive (which is
correct),
and because of that Spy was adding a new array into existing ones for that
drive.
That means we now have an extra array and while traversing the array later,
Spy was
crashing.
Another problem here was when the Physical drive is removed, it is removed
from part of Logical drive list but was not removed from the array list .
Both of the above problems are fixed now.
|
|
Version
Fixed:
|
|
7.24.26
|
|
Resolution:
|
|
FIXED
|
|
Suggested
Testing:
|
|
1>
Please verify insertion/removal for other RAID combinations also. 2>
Please verify insertion/removal by inserting removing drives, couple of
times.
|
|
Task
References:
|
|
LSID100032381
|
|
DFCT
ID:
|
|
LSID100031920
|
|
Headline:
|
|
SPY
Crashing
|
|
Version
Reported:
|
|
7.24.24
|
|
Description:
|
|
SPy crashing on a bad drive
|
|
Steps
To Reproduce:
|
|
on linux system
slot0 -- system,
slot1 -- bad disk
slot2 -- raid1 member
slot3 -- raid1 member
1. I plugged out the bad disk serval times and
plugged the slot3 disk and plugged in, whether I have plugged
out slot3 disk serval times.
2. At a certain time, all the LIGHT went to RED, and I can see BAD disk
record in /var/log/messages to
which our hotplug driver put information, at this
time I run my tool which call our hotplug interface
and
find the function [bad disk is plugged out, and two RAID1 member disks is
plugged in and with a
system volume disk in slot 0]
3. spy__get_DriveStatusNum
return 2, and a member of the raid did not shows information, that is to say
with normal method I can not get information of it [get disk information
method can be seen in the
following].
so the LIGHT goes to RED then.
In the said log file, it printed some lines like following:
... (Slot: 0) error
... (Slot: 1) error
|
|
Resolution
Description:
|
|
The root
cause for this problem is same as for DFCT # LSID100031921 which is below:
On removing Physical Drive,
Spy recreates its own repository. While Recreating Spy
repository, Spy was removing the drive from internal structures, and then
recreating
an arry repository to reflect which all drives
belong to which array.
Here Spy is now getting the null pointer for the removed drive (which is
correct),
and because of that Spy was adding a new array into existing ones for that
drive.
That means we now have an extra array and while traversing the array later,
Spy was
crashing.
Another problem here was when the Physical drive is removed, it is removed
from part of Logical drive list but was not removed from the array list .
Both of the above problems are fixed now.
|
|
Version
Fixed:
|
|
7.24.26
|
|
Resolution:
|
|
FIXED
|
|
Suggested
Testing:
|
|
1>
Please verify insertion/removal for other RAID combinations also. 2>
Please verify insertion/removal by inserting removing drives, couple of
times.
|
|
Task
References:
|
|
LSID100032379 LSID100032381
|
|
DFCT
ID:
|
|
LSID100031921
|
|
Headline:
|
|
Spy
Crashing
|
|
Version
Reported:
|
|
7.24.24
|
|
Description:
|
|
Spy icon
not reporting
|
|
Steps
To Reproduce:
|
|
1 RAID1
be the system harddisk(slot0 and slot1)
2 RAID0 (slot2 first RAID0 and slot3 second RAID0)
after ES4.0 32bit installed in RAID1, install spy in system
startup ES4.0->ok, spy icon ->green
hotplug out first RAID0, spy show plugout message window, spy icon->red, spy is alive
hotplug out second RAID0, spy dead, not show plugout message window, spy icon->green
|
|
Resolution
Description:
|
|
On
removing Physical Drive,
Spy recreates its own repository. While Recreating Spy
repository, Spy was removing the drive from internal structures, and then
recreating
an arry repository to reflect which all drives
belong to which array.
Here Spy is now getting the null pointer for the removed drive (which is
correct),
and because of that Spy was adding a new array into existing ones for that
drive.
That means we now have an extra array and while traversing the array later,
Spy was
crashing.
Another problem here was when the Physical drive is removed, it is removed
from part of Logical drive list but was not removed from the array list .
Both of the above problems are fixed now.
|
|
Version
Fixed:
|
|
7.24.26
|
|
Resolution:
|
|
FIXED
|
|
Suggested
Testing:
|
|
1>
Please verify insertion/removal for other RAID combinations also. 2>
Please verify insertion/removal by inserting removing drives, couple of
times.
|
|
Task
References:
|
|
LSID100032381
|