Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
As I see, the "problem" is with devices mounted within initrd image.
No problem with these names at all. You should revise your boot image to fix names.
I am not sure that you will success, but you will learn a lot.
not sure that separate /usr is a problem with lvm but with systemd /usr is not being used but you have 2 options rebuild initrd or initramfs (not sure which) to support separate /usr or move it to root.
BTW Thanks for posting this thread the machine that I'm on is having problems & it's most likely due to separate /usr.
Anything that I want to use I have to execute from /usr/bin
I actually tried unpacking/decompressing the image last weekend. It looked succesfull, but where to go from there .... ?
"rebuild initrd to support separate /usr".
I am not familliar with this process. Can you point me in the right direction ? (I can google it myself, but about 10 million links show up).
What is the core functionality of systemd ?
Last edited by shadow-fmx; 06-30-2015 at 04:04 AM.
Everything is fine and mounted on my box. I just cut the relative info out for the post.
my var, usr, etc, etc. are all on that lv (/)
I can't find anything on this elsewhere, not sure what to search for either though.
Oh, and other than this 'visual' issue, the system is fine. Just my monitoring scripts and such that look for the dm mapped named had to all be revised to point to the dev name instead - it's just bothering because I can't figure it out
The LVM volume is mounted just fine. The /dev/mapper/LVNAME is a mapping to the long device name for ease of use. The dm-2 name is a very short name for the device itself, which isn't the proper method of displaying the LVM volume.
From what I understand the initial root volume is always mount RO at first then remounted with FSTAB options. So I believe that is functioning as designed.
More explanation on the /dev/mapper vs /dev/dm naming:
Well, from functional point of view they are same - they point to the
same device, of course. But dmsetup/lvm itself does not create the
/dev/dm-X nodes - the ones in /dev/mapper are the right and official
ones that should always be used.
The /dev/dm-X nodes are created by some general udev rules, dm-X is
only internal kernel name for that device and you can't rely on those
names (because the number X that is assigned is not stable and could
be changed - it depends on the sequence of device activation).