From: Fabian Herschel <fabian.herschel@novell.com>
To: suleyman.kutlu@gmail.com,
LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Device mapper problems..
Date: Thu, 15 Sep 2005 18:02:34 +0200 [thread overview]
Message-ID: <43299B1A.3090200@novell.com> (raw)
In-Reply-To: <432986DA.50107@gmail.com>
You have a look which device path is used when mounting your both file
systems (using mount).
Than you can have a look at the major and minor device number of these
devices (using ls -la).
If these devices are using the same major/minor combination the kernel
assumes these devices
the be the same. This would show the effects you mentioned.
ls -la /dev/mapper/*
brw------- 1 root root 253, 3 Jun 21 16:09 /dev/mapper/rootvg-homlv
brw------- 1 root root 253, 2 Jun 21 16:09 /dev/mapper/rootvg-optlv
in this case rootvg-homlv has major 253 and minor 3, while rootvg-optlv
has major 253 and minor 2.
best regards
Fabian Herschel
Suleyman Kutlu schrieb:
> Hello all,
>
>
> I have an AMD-64 machine running SuSE 9.2. I have one SATA 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 (say lv_a) I see
> the directory structure of another LV (say lv_b). If I issue a df -k,
> I see a wrong size for lv_a, it is the size of lv_b. But in lvdisplay
> output, the size for lv_a is correct.
>
> The file systems on lv_a and lv_b is JFS.
>
> /mnt is mounted as lv_b
> /mnt2 is mounted as lv_a but has contents of lv_b
>
>
> I thought that, filesystem structure is corrupted and started to work
> on some filesystem level utilities, but later 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 ?
> If the corruption is at filesystem level, do you have any experience
> on JFS-utils ? I just want to see what was stored in lv_a, what I lost
> in lv_a...
>
>
> 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 regards..
>
> * Suleyman Kutlu
> * mailto: suleyman.kutlu@gmail.com
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
next prev parent reply other threads:[~2005-09-15 16:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-15 14:36 [linux-lvm] Device mapper problems Suleyman Kutlu
2005-09-15 16:02 ` Fabian Herschel [this message]
2005-09-15 23:23 ` Suleyman Kutlu
2005-09-16 20:08 ` Lars Ellenberg
2005-09-17 11:49 ` Suleyman Kutlu
2005-09-17 19:10 ` Lars Ellenberg
2005-09-21 10:01 ` Suleyman Kutlu
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=43299B1A.3090200@novell.com \
--to=fabian.herschel@novell.com \
--cc=linux-lvm@redhat.com \
--cc=suleyman.kutlu@gmail.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.