<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> Thanks for your response. Effectively, I use the lv name : fsck.ext3 /dev/vg_home/lvol0 Result is a list of I/O errors, dma_intr, buffer I/O error, ... Nick Geovanis <a class="moz-txt-link-rfc2396E" href="mailto:n-geovanis@northwestern.edu"><n-geovanis@northwestern.edu></a> a écrit : <blockquote cite="midPine.SOL.4.10.10510051210230.12727-100000@merle.it.northwestern.edu" type="cite"> <blockquote type="cite"> <pre wrap="">From: Luc MAIGNAN <a class="moz-txt-link-rfc2396E" href="mailto:luc.maignan@winxpert.com"><luc.maignan@winxpert.com></a> Subject: Disk problem with LVM Message-ID: <a class="moz-txt-link-rfc2396E" href="mailto:4343F6C7.200@winxpert.com"><4343F6C7.200@winxpert.com></a> I used LVM partitions on a disk. This partition seems to have been crashed. I cannot do a fsck on it. Is there a LMV specific tool to repair the partition ? </pre> </blockquote> <pre wrap=""> Are you sure that you fsck'ed the correct device name? You want to use the device name for the logical volume (LV), not the name for the volume group (VG) or physical volume (PV). The LVM stuff works below the level of the filesystem, so there is no conceptual link between the two except when resizing a mounted filesystem after resizing the underlying LV. * Nick Geovanis | IT Computing Svcs | Northwestern Univ | n-geovanis@ | northwestern.edu +-------------------> </pre> </blockquote> </body> </html>