All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan E Brassow <jbrassow@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: reboot problem
Date: Mon, 30 Oct 2006 10:45:33 -0600	[thread overview]
Message-ID: <f4eecfb9818a11ba9525b0a838628664@redhat.com> (raw)
In-Reply-To: <454567BF.04EDDA.27845>


[-- Attachment #1.1: Type: text/plain, Size: 1251 bytes --]

Device Mapper does not remember the tables you have created across 
reboots.  For persistent volume creation, I would use LVM2.

If you must use device mapper, you could create an init script that 
creates the devices you've mentioned and mounts "v2".  Be forewarned, 
Linux can reorder block devices, so hard-coding block device names in 
your init script may result in mapping the wrong device(s).  (LVM2 gets 
around this by writing labels to the devices, so that it can identify 
the proper devices and assemble them in the correct order.)

  brassow

On Oct 29, 2006, at 8:01 PM, ~{KNUq;*~} wrote:

> Hi all:
> 	I'm a beginner to Device Mapper, now I have a problem perhaps stupid.
> 	However, I have made a mapped device named "v1" with table "t1", then 
> I made a mapped device named "v2" with table "t2" using "v1" as the 
> targed device, and mount "/dev/mapper/v2" at "/mnt/vd".
> 	Now I hope that after reboot there are still "v1","v2" and "v2" will 
> be still mounted at "/mnt/vd". How should I do for these? Thanks!
>
> ~{!!!!!!!!!!!!!!!!~}Song Zhenhua
> ~{!!!!!!!!!!!!!!!!~}songzhh81@163.com
> ~{!!!!!!!!!!!!!!!!!!!!~}2006-10-30
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
>

[-- Attachment #1.2: Type: text/enriched, Size: 1502 bytes --]

Device Mapper does not remember the tables you have created across
reboots.  For persistent volume creation, I would use LVM2.


If you must use device mapper, you could create an init script that
creates the devices you've mentioned and mounts "v2".  Be forewarned,
Linux can reorder block devices, so hard-coding block device names in
your init script may result in mapping the wrong device(s).  (LVM2
gets around this by writing labels to the devices, so that it can
identify the proper devices and assemble them in the correct order.)


 brassow


On Oct 29, 2006, at 8:01 PM,
<fontfamily><param>Hiragino Kaku Gothic Pro</param>~{KNUq~}</fontfamily><fontfamily><param>STHeiti</param>~{;*~}</fontfamily>
wrote:


<excerpt>Hi all:

	I'm a beginner to Device Mapper, now I have a problem perhaps stupid. 

	However, I have made a mapped device named "v1" with table "t1", then
I made a mapped device named "v2" with table "t2" using "v1" as the
targed device, and mount "/dev/mapper/v2" at "/mnt/vd". 

	Now I hope that after reboot there are still "v1","v2" and "v2" will
be still mounted at "/mnt/vd". How should I do for these? Thanks!


<fontfamily><param>STHeiti</param>~{!!!!!!!!!!!!!!!!~}</fontfamily>Song Zhenhua

<fontfamily><param>STHeiti</param>~{!!!!!!!!!!!!!!!!~}</fontfamily>songzhh81@163.com

<fontfamily><param>STHeiti</param>~{!!!!!!!!!!!!!!!!!!!!~}</fontfamily>2006-10-30


--

dm-devel mailing list

dm-devel@redhat.com

https://www.redhat.com/mailman/listinfo/dm-devel


</excerpt>

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



       reply	other threads:[~2006-10-30 16:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <454567BF.04EDDA.27845>
2006-10-30 16:45 ` Jonathan E Brassow [this message]
2010-06-07  2:59 Reboot Problem Chaitra Gorantla
2010-06-07  3:19 ` Sterling Windmill
2010-06-07  3:44   ` Chaitra Gorantla
  -- strict thread matches above, loose matches on Subject: below --
2006-10-30  2:01 reboot problem 宋振华
2006-08-25 18:55 Ming Li
2005-11-04  0:33 Reboot problem JaniD++
2005-11-04  5:30 ` Willy Tarreau
2004-08-12  2:42 Aleksey Gorelov
1999-04-09 18:15 reboot problem Edward Brookhouse

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=f4eecfb9818a11ba9525b0a838628664@redhat.com \
    --to=jbrassow@redhat.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.