Sophie

Sophie

distrib > Mandriva > 2010.1 > x86_64 > by-pkgid > 965e33040dd61030a94f0eb89877aee8 > files > 3035

howto-html-en-20080722-2mdv2010.1.noarch.rpm

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML
><HEAD
><TITLE
>Reporting Errors and Bugs</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
REL="HOME"
TITLE="LVM HOWTO"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Sharing LVM volumes"
HREF="sharinglvm1.html"><LINK
REL="NEXT"
TITLE="Contact and Links"
HREF="contactsandlinks.html"></HEAD
><BODY
CLASS="appendix"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>LVM HOWTO</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="sharinglvm1.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="contactsandlinks.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="appendix"
><H1
><A
NAME="ReportBug"
></A
>Appendix B. Reporting Errors and Bugs</H1
><P
>&#13;      Just telling us that LVM did not work does not provide us with enough
      information to help you.  We need to know about your setup and the
      various components of your configuration.  The first thing you should
      do is check the
      <A
HREF="http://lists.sistina.com/pipermail/linux-lvm/"
TARGET="_top"
>linux-lvm mailing list archives</A
>
      to see if someone else has already reported the same bug.  If you do
      not find a bug report for a problem similar to yours you should
      collect as much of the following information as possible.  The list is
      grouped into three categories of errors.
    </P
><P
></P
><UL
><LI
><P
>&#13;          For compilation errors:
        </P
><P
></P
><OL
TYPE="1"
><LI
><P
>&#13;              Detail the specific version of LVM you have.  If you
              extracted LVM from a tarball give the name of the tar file
              and list any patches you applied.  If you acquired LVM
              from the Public CVS server, give the date and time you
              checked it out.
            </P
></LI
><LI
><P
>&#13;              Provide the exact error message. Copy the lines
              of output before the actual error message as well
              as the lines after.  These lines occasionally
              give hints as to why the error occurred.
            </P
></LI
><LI
><P
>&#13;              List the steps, in order, that produced the error.  Is the
              error reproducible?  If you start from a clean state does
              the same sequence of steps reproduce the error?
            </P
></LI
></OL
></LI
><LI
><P
>&#13;          For LVM errors:
        </P
><P
></P
><OL
TYPE="1"
><LI
><P
>&#13;              Include all of the information requested in the
              compilation section.
            </P
></LI
><LI
><P
>&#13;              Attach a short description of your hardware: types of
              machines and disks,  disks interface (SCSI, FC, NBD).  Any
              other tidbits about your hardware you feel is important.
            </P
></LI
><LI
><P
>&#13;              The command lines used with LVM to produce the error.
            </P
></LI
><LI
><P
>&#13;              A log file produced when running the offending commands.
              Make sure you have the following in your
              <TT
CLASS="filename"
>/etc/lvm/lvm.conf</TT
> file:
              <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="screen"
>&#13;log {
        file="/tmp/lvm2.log"
        level=7
        activation=1
}
              </PRE
></FONT
></TD
></TR
></TABLE
>
            </P
></LI
></OL
></LI
><LI
><P
>&#13;          When LVM trips a panic trap:
        </P
><P
></P
><OL
TYPE="1"
><LI
><P
>&#13;              Include all of the information requested in two sections
              above.
            </P
></LI
><LI
><P
>&#13;              Provide the debug dump for the machine.  This is best
              accomplished if you are watching the console output of the
              computer over a serial link, since you can't very well
              copy and paste from a panic'd machine, and it is very easy
              to mistype something if you try to copy the output by
              hand. 
            </P
></LI
></OL
></LI
></UL
><P
>&#13;      This can be a lot of information.  If you end up with more
      than a couple of files, tar and gzip them into a single
      archive.  Submit a link to where this file can be found to
      the appropriate mailing list (see <A
HREF="maillists.html"
>Section C.1</A
>) along with a short description of the
      error.  If you do not have a public web or ftp site that you
      can post the information to, you can try to submit the file
      to the list.
    </P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="sharinglvm1.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="contactsandlinks.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Sharing LVM volumes</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Contact and Links</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>