All of lore.kernel.org
 help / color / mirror / Atom feed
From: Suleyman Kutlu <suleyman.kutlu@gmail.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Device Mapper corruption
Date: Mon, 11 Jul 2005 15:32:24 +0300	[thread overview]
Message-ID: <42D266D8.6040001@gmail.com> (raw)
In-Reply-To: <00a501c57c92$c3041020$1f000064@polaris>

Hello all,

I have an AMD-64 machine running SuSE 9.2. I have one disk (for now,
will add another later on) and a VG on it. I have created some LVs.

Sometimes later, I realized that when I mount an LV (lets call it
lv_a) I see the directory structure of another LV (lets call it lv_b). If I issue a df -k, I see the size of lv_b for lv_a,
but in lvdisplay output, the size for lv_a is correct.

/mnt is mounted as lv_b
/mnt2 is mounted as lv_a but has contents as lv_b has.

I thought that, filesystem structure is corrupted and started to work
on some filesystem level utilities today, but today I see that,
another filesystem pair also got the same problem.

So I think it is a problem in device-mapper level, not the filesystem level. 

What can be the possible works to get what is wrong and how to fix ? 

I am new at device-mapper, I don't have enough experience on it and I
do not want to loose everything while there is something that can be
recovered...

Any help is appreciated. 

Thanks and best regards.. 

* 
* Suleyman Kutlu
*
* mailto: suleyman.kutlu@gmail.com
*

      parent reply	other threads:[~2005-07-11 12:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-29 10:10 bio's bi_size bug also be founded at dm-stripe.c and dm-snap.c (resend in correct charset) Zhao Qian
2005-06-29 11:30 ` Kevin Corry
2005-06-29 11:46   ` Kevin Corry
2005-06-29 14:42     ` Alasdair G Kergon
2005-06-30  2:02       ` Zhao Qian
2005-07-11 12:32 ` Suleyman Kutlu [this message]

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=42D266D8.6040001@gmail.com \
    --to=suleyman.kutlu@gmail.com \
    --cc=dm-devel@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.