outsource from india chennai india programmers freelance php coder freelance outsource scripts programming complicated perl patterns php module installation
outsource from india perl installation and configuration php installation linux system administration US$15,US$19,US$11,US$10 cheap programmer
india outsource outsource india chennai india programmers php perl mysql freelance freelance programmer
SHOWCASE of php and perl scripts CONTACT US for php custom perl scripts
HOME
 

Chapter 13. Reporting Errors and Bugs

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 linux-lvm mailing list archives 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.

  • For compilation errors:

    1. 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.

    2. Provide the exact error message. Copy a couple of lines of output before the actual error message, as well as, a couple of lines after. These lines occasionally give hints as to why the error occurred.

    3. 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?

  • For LVM errors:

    1. Include all of the information requested in the compilation section.

    2. 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.

    3. Include the output from pinfo -s

    4. The command line used to make LVM and the file system on top of it.

    5. The command line used to mount the file system.

  • When LVM trips a panic trap:

    1. Include all of the information requested in two sections above.

    2. 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.

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 this compressed archive file to lvm-devel along with a short description of the error.


Linux HOWTO full list
   This document, LDP HOWTO-INDEX, is copyrighted (c) 1995 - 2002 by Tim Bynum, Guylhem Aznar, Joshua Drake and Greg Ferguson. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover Texts, and with no Back-Cover Texts. A copy of the license is available at http://www.gnu.org/copyleft/fdl.html. If you have questions, please contact the LDP.
Web Design Copyright © 1999-2003. Chrisranjana Software Solutions Pvt Ltd. syndicate rss feed