diff options
author | Radek Vykydal <rvykydal@redhat.com> | 2009-05-13 15:30:27 +0200 |
---|---|---|
committer | Radek Vykydal <rvykydal@redhat.com> | 2009-05-15 09:53:43 +0200 |
commit | c8f1322b336e434b380219a4935d1cc2e31d2ebf (patch) | |
tree | fa48a84a8261a0929a8a0386b79d4bf4ea0646a3 /po | |
parent | 7316b263561cf6e40e733aea3482ef319baa52c6 (diff) | |
download | anaconda-c8f1322b336e434b380219a4935d1cc2e31d2ebf.tar.gz anaconda-c8f1322b336e434b380219a4935d1cc2e31d2ebf.tar.xz anaconda-c8f1322b336e434b380219a4935d1cc2e31d2ebf.zip |
Consider active-idle state of md device as accepatable status of device (#497407)
This should fix traceback met when we were updating sysfs path attribute of md
device in active-idle state (empty string was returned as the device was not in
state clean or active). I think it is a state very rarely met in our tests.
According to md.txt, it is "like active, but no writes have been seen for a
while". I prepared updates.img for testing, but we can't reproduce the bug.
Diffstat (limited to 'po')
0 files changed, 0 insertions, 0 deletions