| 2006-09-04 16:41:38 |
Timothy Miller |
bug |
|
|
added bug |
| 2007-06-21 19:13:31 |
Micah Cowan |
None: status |
New |
Invalid |
|
| 2007-06-21 19:13:31 |
Micah Cowan |
None: statusexplanation |
|
Thanks for your report. Your idea might get more attention and have the possibility of being implemented if you submit a specification for it. First check whether the idea is already registered <https://launchpad.net/ubuntu/+specs>, and if so, contact the specification's drafter about your ideas. Otherwise, you can start writing a spec yourself. <https://wiki.ubuntu.com/FeatureSpecifications> |
|
| 2008-10-07 16:01:27 |
Dustin Kirkland |
None: status |
Invalid |
Confirmed |
|
| 2008-10-07 16:01:27 |
Dustin Kirkland |
None: statusexplanation |
Thanks for your report. Your idea might get more attention and have the possibility of being implemented if you submit a specification for it. First check whether the idea is already registered <https://launchpad.net/ubuntu/+specs>, and if so, contact the specification's drafter about your ideas. Otherwise, you can start writing a spec yourself. <https://wiki.ubuntu.com/FeatureSpecifications> |
I'm marking this bug as confirmed, although the behavior has improved to some degree in Intrepid.
Here are my observations...
1) Boot with diskA and diskB attached, the md is actively sync'd. (EXPECTED, OKAY)
2) Disconnect diskB, the md will (optionally) come up in a degraded mode, using only diskA (EXPECTED, OKAY)
3) Re-attach diskB. The md will come up in degraded mode, using only diskA. This is (EXPECTED, OKAY), because the state of diskB is unknown. You can manually add diskB back to the array, and once it has re-synced, it will be an active member of the array on subsequent boots.
4) Disconnect diskA, attach diskB. The md will (optionally) come up in degraded mode (as several other bugs have solved this for Ubuntu Intrepid). (EXPECTED, OKAY)
5) Now, we have booted each of diskA and diskB as the only member of the array. Each of them "think" that they are the only active member of a degraded array. What is the desired behavior now? Clearly the two disks are out of sync, and cannot be booted together in the same array. Currently, in Intrepid, the disk "last touched" is booted. I *think* this is the best behavior, but perhaps something more interactive from the system administrator's standpoint would be most desired.
Timothy-
Is there any way that you can test this behavior in Intrepid? I would be very curious to get your take on the new behavior.
:-Dustin
|
|
| 2008-10-08 16:54:51 |
Dustin Kirkland |
None: status |
Confirmed |
Fix Released |
|
| 2008-10-08 16:54:51 |
Dustin Kirkland |
None: statusexplanation |
I'm marking this bug as confirmed, although the behavior has improved to some degree in Intrepid.
Here are my observations...
1) Boot with diskA and diskB attached, the md is actively sync'd. (EXPECTED, OKAY)
2) Disconnect diskB, the md will (optionally) come up in a degraded mode, using only diskA (EXPECTED, OKAY)
3) Re-attach diskB. The md will come up in degraded mode, using only diskA. This is (EXPECTED, OKAY), because the state of diskB is unknown. You can manually add diskB back to the array, and once it has re-synced, it will be an active member of the array on subsequent boots.
4) Disconnect diskA, attach diskB. The md will (optionally) come up in degraded mode (as several other bugs have solved this for Ubuntu Intrepid). (EXPECTED, OKAY)
5) Now, we have booted each of diskA and diskB as the only member of the array. Each of them "think" that they are the only active member of a degraded array. What is the desired behavior now? Clearly the two disks are out of sync, and cannot be booted together in the same array. Currently, in Intrepid, the disk "last touched" is booted. I *think* this is the best behavior, but perhaps something more interactive from the system administrator's standpoint would be most desired.
Timothy-
Is there any way that you can test this behavior in Intrepid? I would be very curious to get your take on the new behavior.
:-Dustin
|
|
|
| 2012-02-23 21:35:08 |
Kai Kasurinen |
removed subscriber Kai Kasurinen |
|
|
|
