diff options
| author | madduck <madduck@3cfab66f-1918-0410-86b3-c06b76f9a464> | 2006-09-16 09:43:46 +0000 |
|---|---|---|
| committer | madduck <madduck@3cfab66f-1918-0410-86b3-c06b76f9a464> | 2006-09-16 09:43:46 +0000 |
| commit | 8c64af57be721910a39a740db4ecfc266129781e (patch) | |
| tree | e60ea13514c4462dae6688efa0fcd9f52b077d33 /debian/FAQ | |
| parent | 9459a36cf1f50444463811d2807fe3352b52e56d (diff) | |
FAQ updates
Diffstat (limited to 'debian/FAQ')
| -rw-r--r-- | debian/FAQ | 12 |
1 files changed, 7 insertions, 5 deletions
@@ -147,12 +147,14 @@ Also see /usr/share/doc/mdadm/README.recipes.gz If mdadm cannot stop other arrays on your system, check that these arrays aren't used anymore. Common causes for busy/locked arrays are: - * LVM - * dm-crypt - * EVMS + * The array contains a mounted filesystem (check the `mount' output) + * The array is used as a swap backend (check /proc/swaps) + * The array is used by the device-mapper (check with `dmsetup') + * LVM + * dm-crypt + * EVMS + * The array is used by a process (check with `lsof') - Check that none of these are using the md arrays before trying to stop them. - -- martin f. krafft <madduck@debian.org> Wed, 02 Aug 2006 16:38:29 +0100 $Id$ |