linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Lars Ellenberg <Lars.Ellenberg@linbit.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Device mapper problems..
Date: Fri, 16 Sep 2005 22:08:33 +0200	[thread overview]
Message-ID: <20050916200833.GA2453@barkeeper1.linbit> (raw)
In-Reply-To: <432A0282.5020905@gmail.com>

/ 2005-09-16 02:23:46 +0300
\ Suleyman Kutlu:

> Two VGs.
> 
> systemvg on /dev/sda4
> datavg on /dev/sdb1
> 

slightly moving the chunks around in your mail,
so it is more obvious...

> What I am trying to do is:
> 
> - At least get the directory contents of the filesystem
>   /dev/datavg/snk2lv inorder to know what I have lost.
>   Is it possible to get this with jfsutils ??  Any experience ?

hm...

> - If there is a way to fix-up the device-mapper tables and get my
>   filesystems back, it is ofcourse welcome.

well, comparing this:

> ls -la /dev/mapper
> total 124
> drwxr-xr-x   2 root root    4096 Sep 16  2005 .
> drwxr-xr-x  36 root root  118784 Sep 16 01:49 ..
> crw-------   1 root root  10, 63 Sep 16  2005 control

> brw-------   1 root root 253,  0 Jun  5 03:24 systemvg-optlv
> brw-------   1 root root 253,  1 Jun  5 03:25 systemvg-varlv
> brw-------   1 root root 253,  1 May 10 03:08 systemvg-rootlv
> brw-------   1 root root 253,  2 Jun  5 03:26 systemvg-tmplv
> brw-------   1 root root 253,  3 Jun  5 03:26 systemvg-usrlv
> brw-------   1 root root 253,  4 Jun  5 03:27 systemvg-temp

> brw-------   1 root root 253,  6 Jul 16 20:32 datavg-rootlv
> brw-------   1 root root 253,  7 Jul 16 22:40 datavg-snk2lv
> brw-------   1 root root 253,  8 Sep 16  2005 datavg-backup

> dmsetup ls output is:
> 
> systemvg-optlv (253, 0)
> systemvg-tmplv (253, 1)
> systemvg-usrlv (253, 2)
> systemvg-varlv (253, 3)
> systemvg-temp  (253, 4)
> systemvg-rootlv(253, 5)

> datavg-rootlv  (253, 6)
> datavg-snk2lv  (253, 7)
> datavg-backup  (253, 8)


for a start,
we see that the device nodes for -optlv and -temp are correct,
and the datavg seems correct.

but 253,1 apears two times in the listing, and 253,5 is missing...

recreate those nodes with
# dmsetup mknodes

or by hand with:
# cd /dev/mapper
# rm systemvg-{varlv,rootlv,tmplv,usrlv}
# mknod systemvg-tmplv   b 253 1
# mknod systemvg-usrlv   b 253 2
# mknod systemvg-varlv   b 253 3
# mknod systemvg-rootlv  b 253 5

now, how this could happen is an other question.

note that maybe the mapping of names to minors is still wrong.
but at least all of the devices should be there again;
(253,5) was missing completely before.

hope that gets you one step further.

-- 
: Lars Ellenberg                                  Tel +43-1-8178292-0  :
: LINBIT Information Technologies GmbH            Fax +43-1-8178292-82 :
: Schoenbrunner Str. 244, A-1120 Vienna/Europe   http://www.linbit.com :

  reply	other threads:[~2005-09-16 20:09 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
2005-09-15 23:23   ` Suleyman Kutlu
2005-09-16 20:08     ` Lars Ellenberg [this message]
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=20050916200833.GA2453@barkeeper1.linbit \
    --to=lars.ellenberg@linbit.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).