Joost Roeleveld wrote:
On Friday 08 April 2011 16:30:03 Dale wrote:
The naming I was talking about was sort of like a label. I wanted to
use test, where I might use say data in real use, but ended up with this:
root@fireball / # df
Filesystem 1K-blocks Used Available Use% Mounted on
<< SNIP>>
/dev/mapper/sdb--vg-test
51606140 184268 48800432 1% /mnt/temp
root@fireball / #
I don't mind the sdb--vg part tho. I guess that sort of points to what
all is needed to get to that point. Might come in handy if I needed to
remove something tho. Sort of tells me what is what.
True :)
I tend to start my VGs with "vg_<something>". That way I know what they're
for.
Also, it's a good idea to not name them "vg" as then you can get naming
conflicts if you ever put the drive into another machine that also has a VG
called that.
As example for the way I name them:
vg_<hostname>.
On my server, I actually have 2 Volume Groups. One for the OS-parts (including
VMs) and the other for the data.
I wish it was like file system labels but I guess any clues is better
than nothing.
I did try to mount it before putting a file system on it. I sort of
missed that part somewhere. I knew it needed it, just forgot to do it.
Mount sort of puked on my keyboard to remind me. lol
Hehe :)
I forget as well sometimes.
Whew !! Progress. Oh, someone posted a link to a site that had
pictures. That helped a good bit. It needed more detail tho. I'm
going to do some google image searches and see what I can find.
I think I posted more then 1 link, actually :)
Thanks much.
You're welcome
--
Joost
You did. I think a couple of them had some pictures to but google image
search found some more that helped. Of course, reading the commands to
see how they work helped too. I just needed a picture to see how this
was built up.
I learned a lot in the past couple days. Still don't want my OS on it
tho. ;-)
Dale
:-) :-)
