Red Hat Bugzilla – Bug 77477
raid 5 reconstruction "freze" if device is in use
Last modified: 2008-08-01 12:22:53 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)
Description of problem:
When I set a device as failed on a raid 5 that is curently in use (mounted fs)
using the command :
# mdadm /dev/md0 -f /dev/hdb1
the command freeze and any mdadm or access to the mounted fs fail
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. mdadm -C -l5 -n3 -x1 /dev/md0 /dev/sdb
2. mke2fs -j /dev/md0 ; mount /dev/md0 /mnt
3. while sleep 1 ; do date >> /mnt/log ; done &
4. tail -f /mnt/log
5. mdadm /dev/md0 -f /dev/sdb1
Actual Results: the mdamd command never finish and any access to /mnt or mdadm
command fail !
If /dev/md0 is not in use (no access to the mounted fs) this works
I have to restart the machine and restart/repair/reconstruct the raid device
If the root in on an raid device too, the machine will refuse to restart !
I was making some test/exercise on an rh8.0 to learn mdadm and know what to do
to replace a failed disk.
I was first making test using /dev/loop? then tried real device /dev/hdb* to
know if the probleme was about /dev/loop.
The same probleme append with a RH7.3 too: Both (rh73 and rh80) use kernel
I tried an an RH72 kernel 2.4.7 and it was working fine.
Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem
The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases,
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/