martin f. krafft: add note about rootdelay to FAQ and presubj

[Martin F. Krafft]

Module: mdadm
Branch: master
Commit: 7e7414760afa42a10eac8f77e3f6f79c207849ec
URL:    http://git.debian.org/?p=pkg-mdadm/mdadm.git;a=commit;h=7e7414760afa42a10eac8f77e3f6f79c207849ec

Author: martin f. krafft <madduck at debian.org>
Date:   Mon Jul 20 15:06:52 2009 +0200

add note about rootdelay to FAQ and presubj

---

 debian/FAQ     |   13 ++++++++++++-
 debian/presubj |   23 +++++++++++++++++++----
 2 files changed, 31 insertions(+), 5 deletions(-)

diff --git a/debian/FAQ b/debian/FAQ
index c7cdd8d..649e689 100644
--- a/debian/FAQ
+++ b/debian/FAQ
@@ -581,4 +581,15 @@ The latest version of this FAQ is available here:
   http://wiki.debian.org/InitramfsDebug. Please append rootdelay=10 to the
   kernel command line and try if the boot now works.
 
- -- martin f. krafft <madduck at debian.org>  Wed, 13 May 2009 09:59:53 +0200
+27. Can mdadm please wait for the kernel to initialise all devices?
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+  By the time mdadm runs in the initramfs, the kernel should have readied all
+  block devices. If it fails to do that, then there is nothing mdadm can do.
+  In such cases, you should consider filing bugs against the driver(s)
+  involved, such that they do not pretend to be ready when they aren't yet.
+
+  A workaround is to append rootdelay=10 to the kernel command line, which
+  will cause the initramfs scripts to wait for 10 seconds for devices to get
+  ready and nodes to appear.
+
+ -- martin f. krafft <madduck at debian.org>  Mon, 20 Jul 2009 14:59:19 +0200
diff --git a/debian/presubj b/debian/presubj
index 9eb304f..987c520 100644
--- a/debian/presubj
+++ b/debian/presubj
@@ -1,17 +1,32 @@
+Reporting bugs against mdadm
+============================
+Before reporting bugs against mdadm, please read the README documents, as well
+as the FAQ in /usr/share/doc/mdadm . Most issues that are reported against the
+mdadm package are adequately answered therein.
+
+In particular, please do not file bugs about mdadm assembling arrays too
+early, e.g. when the driver is not yet ready and device nodes do not exist.
+Check FAQ item 27 about use of the rootdelay parameter instead.
+
+Also, please check out http://bugs.debian.org/mdadm/ and make sure that the
+issue you are facing has not already been reported.
+
+If you are not sure that the answer you are seeking is in those files, or you
+are not sure that you are facing a genuine bug, please approach
+debian-user at lists.debian.org or linux-raid at vger.kernel.org with your
+question(s).
+
 Gathering information relevant to mdadm as root
 ===============================================
-
 If you are not reporting bugs as root (which you should not), you will be
 prompted to give permission to run a script to collect relevant information
 from your system as the root user. Only the root user has access to some
 information that might be relevant to the bug report you are about to file.
 
-
 ** Please give permission to run the script as root when asked momentarily.
 
-
 If you would rather obtain the same information manually, you can run
   /usr/share/bug/mdadm/script 3>&1
 as root and include or attach the output.
 
- -- martin f. krafft <madduck at debian.org>  Tue, 05 May 2009 11:26:32 +0200
+ -- martin f. krafft <madduck at debian.org>  Mon, 20 Jul 2009 15:02:48 +0200