![]() ![]() Add the old volume into LVM and make it part of the existing LVM volume.Unmount file systems for the old volume and the new volume.Copy the file system from your existing Volume into the new file system.Format it with LVM, and create a LVM volume on it and format the volume.Attach your new Volume to the Instance.and decide if you can deal with the extra complexity. You probably need to do something like this: However, it is not possible to do an in-place conversion of an existing ordinary device into an LVM see. This is possible if you use Linux LVM (see ). What you want here is a single file system that spans multiple Volumes i.e. It is not normal practice to do that with an Volume.) (For a real physical disk, you normally partition the disk as well, and put the file systems into some of the partitions. You then (typically) format it to contain a file system and mount the file system on top of a directory in the root file system. When an Openstack Volume is attached to an Instance, it is viewed by the guest OS as a virtual disk device. That's not how UNIX / Linux filesystems work. Now when I mount this new volume I guess I can mount it to an existing directory on vda? Hence growing the overall size of the existing directory? This is mostly an operating systems question, and it would be better to ask on another site like ServerFault or Unix or AskUbuntu.īut since you are here, and since you asked in the context of Openstack, I'll answer here. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |