Linux LVM users
 help / color / mirror / Atom feed
From: Emmanuel Varagnat <emmanuel.varagnat@free.fr>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Disk crash , LVM and ext2... (bis)
Date: Mon Sep 30 17:55:04 2002	[thread overview]
Message-ID: <3D98D656.2070904@free.fr> (raw)
In-Reply-To: 20020925075113.GK1291@tykepenguin.com

Patrick Caulfield wrote:
> Don't forget, you'll need the "device-mapper" kernel patches too. They work best
> with 2.4.19 kernels, there were VM problems with 2.4.18 ones.
> 

I played a bit with that, and it looks like when device-mapper can't 
access a zone it returns zeros.
What I did, is to create an LV over 4 or 5 partitions, format it, zeroed 
the first partition, do a 'vgscan -P' and try to read the block device 
(LV raw data).
I supposed that this is the device-mapper that hide the missing 
informations by returning zeros. Is there a way to know (via ioctl for 
example) that a data is not available ?
For my program, I need to know, what is readable and what is not readable.

I will also try evms, as E.Tews sugested.

Thanks

-=( manu )=-

PS: I do not have backup of my data because this is personal data (at 
home) and I thought it could be useful, as well as fun, to write this tool.
PPS: I first named this tool e2forensic, but my english isn't so good so 
could someone tell me if it make sense ?
PPPS: thank you for reading the message until there :o)

  reply	other threads:[~2002-09-30 17:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-24 17:51 [linux-lvm] Disk crash , LVM and ext2... (bis) Emmanuel Varagnat
2002-09-25  2:22 ` Patrick Caulfield
2002-09-25  2:43   ` Emmanuel Varagnat
2002-09-25  2:57     ` Patrick Caulfield
2002-09-30 17:55       ` Emmanuel Varagnat [this message]
2002-10-01  9:53         ` Emmanuel Varagnat
2002-10-04  5:40           ` Heinz J . Mauelshagen
2002-10-09 13:59             ` Emmanuel Varagnat

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3D98D656.2070904@free.fr \
    --to=emmanuel.varagnat@free.fr \
    --cc=linux-lvm@sistina.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox