[dm-devel] reboot problem

[Jonathan E Brassow]

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, 宋振华 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 at 163.com
> 　　　　　　　　　　2006-10-30
>
> --
> dm-devel mailing list
> dm-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/enriched
Size: 1502 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/dm-devel/attachments/20061030/245f992b/attachment.bin>