From: <bowmailtmp-lvm@yahoo.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] LVM2/DM Mapping Tables Documentation
Date: Tue, 13 Jul 2004 14:23:12 -0700 (PDT) [thread overview]
Message-ID: <20040713212312.81503.qmail@web11803.mail.yahoo.com> (raw)
I have been having a very difficult time correlating
physical addresses to LVM2/DM addresses.
for instance, if i do:
dmsetup table /dev/mapper/avtest-vdisk2g
the result is:
0 4194304 linear 22:65 384
from what i currently understand, this means logical
extent 0 (which is composed of 8192 512 byte sectors
in the default config) of this LV should start at
physical sector 384 of device 22:65 (/dev/hdd1 on my
machine)
after i've written to the logical device a couple
times, it appears this correlation doesn't hold when i
access the physical sectors on hdd1 using dd.
however, if i use dd to access the sectors through the
LV, all the data appears as it should. i was under
the impression that the logical to physical mappings
was quite straightforward and intuitive, but i feel
that i am missing some key information. Can someone
help me out of is there decent developer documentation
somewhere that explains the mappings?
As a more complete example of my problem, if i do the
following:
dd if=/dev/zero of=/dev/avtest/vdisk2g count=1
then do:
dd if=/dev/avtest/vdisk2g of=tmpfile.out count=1
then tmpfile.out contains 512 bytes of zeros.
however, if I do:
dd if=/dev/hdd1 of=tmpfile.out skip=384 count=1
then tmpfile.out contains other data, not the zero's i
would expect from the output of the dmsetup table
command above. I feel i'm missing something fairly
basic here, but I haven't had any luck tracking this
relationship down. I suppose there is always the
sourc code :)
Thanks a lot.
next reply other threads:[~2004-07-13 21:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-13 21:23 bowmailtmp-lvm [this message]
2004-07-13 23:38 ` [linux-lvm] LVM2/DM Mapping Tables Documentation bowmailtmp-lvm
2004-07-19 6:29 ` Dave B
2004-07-22 17:00 ` Angelo DiNardi
2004-07-22 21:36 ` Dave B
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=20040713212312.81503.qmail@web11803.mail.yahoo.com \
--to=bowmailtmp-lvm@yahoo.com \
--cc=linux-lvm@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.