![\"driveicons\"](\"https:\/\/i0.wp.com\/www.cyberward.net\/blog\/wp-content\/uploads\/driveicons.png?resize=430%2C112\" "\\"driveicons\\"")
<\/p>\n<\/p>\n
Now that we have a raid array created, we are going to create some virtual drives. Why virtual drives? Well, we have one large terabyte drive right now, and if we just put folders in there, it can quickly get cumbersome. You have no control on size of those folders, and permissions can be more difficult. And if you try to share this drive, you can’t assign different drive letters in windows to different folders, just one to the drive. One other issue is file system. I am going to use just a basic file system here, but in the past I have created different file systems based on the type of use ie. large video files, small text files, etc. Making those decisions is beyond the scope of this tutorial, and I have decided that for my purposes now, it doesn’t matter that much. You can decided differently.<\/p>\n
What we will discuss is using LVM. This enables you to set up virtual drives that can contain different file systems, and that can be grown and shrunk (usually) to fit the space needs of the system. We will look at maintenance of these file systems at a later tutorial. Here we will create a backup, and a pictures virtual drive. We will not use the full terabyte of space, so that we can grow these as needed, or add another for say music at another time.<\/p>\n
I will once again be doing this on an ubuntu system, but the use of these tools is fairly standard across linux distributions.
\n
\nFirst we will need to make sure that you have LVM installed.<\/p>\n
sudo apt-get install lvm2<\/pre>\nWe need to create what is called a physical volume. We need to tell LVM what actual physical drives are involved. Lets check what drives we have again.<\/p>\n
$ sudo fdisk -l\r\n\r\nDisk \/dev\/sda: 1000.2 GB, 1000204886016 bytes\r\n255 heads, 63 sectors\/track, 121601 cylinders\r\nUnits = cylinders of 16065 * 512 = 8225280 bytes\r\nDisk identifier: 0x00000000\r\n\r\n Device Boot Start End Blocks Id System\r\n\/dev\/sda1 1 121601 976760001 fd Linux raid autodetect\r\n\r\nDisk \/dev\/sdb: 1000.2 GB, 1000204886016 bytes\r\n255 heads, 63 sectors\/track, 121601 cylinders\r\nUnits = cylinders of 16065 * 512 = 8225280 bytes\r\nDisk identifier: 0xfe76bc93\r\n\r\n Device Boot Start End Blocks Id System\r\n\/dev\/sdb1 1 121601 976760001 fd Linux raid autodetect<\/pre>\nThis is just a partial list of the drives. See that the \/dev\/sda1 and \/dev\/sdb1 drives have a system type of fd. In the last part of teh tutorial we set up software raid. If you are NOT using raid, you will need to add these devices to your physical volume. For us, we are going to add \/dev\/md0 that we created last time. Lets just verify that the array is there.<\/p>\n
$ sudo mdadm --detail --scan\r\nARRAY \/dev\/md0 level=raid1 num-devices=2 metadata=00.90 UUID=****<\/pre>\nNote: all UUID’s will be replaced with **** in this doc. They will be different on every machine anyway.<\/em><\/p>\n
As you can see, array \/dev\/md0 is ready to go. Lets create that physical volume finally.<\/p>\n
sudo pvcreate \/dev\/md0<\/pre>\nYou can verify that it is created with the pvdisplay command.<\/p>\n
$ sudo pvdisplay\r\n \"\/dev\/md0\" is a new physical volume of \"931.51 GB\"\r\n --- NEW Physical volume ---\r\n PV Name \/dev\/md0\r\n VG Name\r\n PV Size 931.51 GB\r\n Allocatable NO\r\n PE Size (KByte) 0\r\n Total PE 0\r\n Free PE 0\r\n Allocated PE 0\r\n PV UUID ****<\/pre>\nNow we need to create our volume group. That last step identified what hardware LVM has available. This next step groups that hardware into volume groups. I will call my “nas”.<\/p>\n
sudo vgcreate nas \/dev\/md0<\/pre>\nWe can then verify our volume group.<\/p>\n
$ sudo vgdisplay\r\n --- Volume group ---\r\n VG Name nas\r\n System ID\r\n Format lvm2\r\n Metadata Areas 1\r\n Metadata Sequence No 1\r\n VG Access read\/write\r\n VG Status resizable\r\n MAX LV 0\r\n Cur LV 0\r\n Open LV 0\r\n Max PV 0\r\n Cur PV 1\r\n Act PV 1\r\n VG Size 931.51 GB\r\n PE Size 4.00 MB\r\n Total PE 238466\r\n Alloc PE \/ Size 0 \/ 0\r\n Free PE \/ Size 238466 \/ 931.51 GB\r\n VG UUID ****<\/pre>\nNext, we can finally create our virtual drives. I am going to create a backup drive of 100 gig, and a pictures drive of 400 gig, both which are added to the “nas” volume group. You can create drives of what ever size you would like.<\/p>\n
sudo lvcreate --name backup --size 100G nas\r\nsudo lvcreate --name pictures --size 400G nas<\/pre>\nYou can see information about these virtual drives with another display command. Guess what it is.<\/p>\n
$ sudo lvdisplay\r\n --- Logical volume ---\r\n LV Name \/dev\/nas\/backup\r\n VG Name nas\r\n LV UUID gqrIVE-YtS4-cBne-QyPK-oMO1-7V7V-UaBoUL\r\n LV Write Access read\/write\r\n LV Status available\r\n # open 0\r\n LV Size 100.00 GB\r\n Current LE 25600\r\n Segments 1\r\n Allocation inherit\r\n Read ahead sectors auto\r\n - currently set to 256\r\n Block device 254:0\r\n\r\n --- Logical volume ---\r\n LV Name \/dev\/nas\/pictures\r\n VG Name nas\r\n LV UUID oDxJJi-lxsG-9RHw-RBME-oJah-jOJJ-J8I4p3\r\n LV Write Access read\/write\r\n LV Status available\r\n # open 0\r\n LV Size 400.00 GB\r\n Current LE 102400\r\n Segments 1\r\n Allocation inherit\r\n Read ahead sectors auto\r\n - currently set to 256\r\n Block device 254:1<\/pre>\nNow that we have our virtual drives, can we start filling them up? Not quite. We need partitions on them. These drives are just like a bare drive from the factory. We can put whatever file system we want on them. I am just going to use ext3. This may not be the best file system out there, but it is proven, and works good enough for me.<\/p>\n
sudo mkfs.ext3 \/dev\/nas\/backup\r\nsudo mkfs.ext3 \/dev\/nas\/pictures<\/pre>\nThat takes a little bit of time, just as would without LVM. As far as your programs, and bash, and Gnome are concerned, \/dev\/nas\/backup is just another drive. It does not care, and does no know that underneath all this is a raid array and virtual drives.<\/p>\n
Now we need to get them mounted so that they are useable. First off, I create a couple of mount points. I like to keep them organized.<\/p>\n
sudo mkdir \/var\/nas\r\nsudo mkdir \/var\/nas\/backup \/var\/nas\/pictures\r\n\r\nsudo mount \/dev\/nas\/backup \/var\/nas\/backup\r\nsudo mount \/dev\/nas\/pictures \/var\/nas\/pictures<\/pre>\nNow, do a “df” to see the drives on the system and the space used.<\/p>\n
$ df\r\nFilesystem 1K-blocks Used Available Use% Mounted on\r\n\/dev\/sdd1 186693520 2469660 174740292 2% \/\r\n\/dev\/mapper\/nas-backup\r\n 103212320 192248 97777192 1% \/var\/nas\/backup\r\n\/dev\/mapper\/nas-pictures\r\n 412849328 203156 391674652 1% \/var\/nas\/pictures<\/pre>\nNote: I removed other system file systems that we are not talking about here.<\/em><\/p>\n
You can see that our two drives are there. They are listed at \/var\/mapper\/nas-backup and \/var\/mapper\/nas-pictures, but they are the \/dev\/nas\/backup and \/dev\/nas\/pictures we have been setting up.<\/p>\n
Now you can copy your data into these drives.<\/p>\n
I am not the only one that uses these drives, and they will be shared on samba (later tutorial) so I like to change the permissions on these folders. I will create a “nas” group, add myself (insert your user id for *user*), and change the permissions.<\/p>\n
sudo groupadd nas\r\nsudo adduser *user* nas\r\nsudo chown -R *user*:nas \/var\/nas\/backup\r\nsudo chown -R *user*:nas \/var\/nas\/pictures<\/pre>\nThe file permissions are set up as writable by owner and readable by group and other. I will leave them this way for now.<\/p>\n
Things look good to go, and they would for awhile, until you reboot. Then your drives would disappear. We need to make them a little more permanent. We do this by putting some entries in the \/etc\/fstab file. This is the list of all mountable file systems that the OS uses to connect things up when booting.<\/p>\n
This file in Ubuntu is using UUID’s, so we will to. First thing you need to do is find out what yours are. So…<\/p>\n
\r\n$ sudo blkid\r\n\/dev\/sdc1: UUID=\"****1\" SEC_TYPE=\"ext2\" TYPE=\"ext3\" \r\n\/dev\/sdd1: UUID=\"****2\" TYPE=\"ext3\" \r\n\/dev\/sdd5: TYPE=\"swap\" UUID=\"****3\" \r\n\/dev\/sda1: UUID=\"****4\" TYPE=\"mdraid\" \r\n\/dev\/sdb1: UUID=\"****5\" TYPE=\"mdraid\" \r\n\/dev\/md0: UUID=\"****6\" TYPE=\"lvm2pv\" \r\n\/dev\/mapper\/nas-backup: UUID=\"****7\" TYPE=\"ext3\" \r\n\/dev\/mapper\/nas-pictures: UUID=\"****8\" TYPE=\"ext3\" \r\n<\/pre>\nYou can see the unique ID’s that are assigned to the drives in the array, the raid array its self, the LVM physical volume, and finally, the two logical volumes. Use these UUID’s that you get when you execute blkid. Now lets edit \/etc\/fstab<\/p>\n
\r\n$ sudo nano -w \/etc\/fstab\r\n# \/etc\/fstab: static file system information.\r\n#\r\n#\r\nproc \/proc proc defaults 0 0\r\n# \/dev\/sdd1\r\nUUID=****2 \/ ext3 relatime,errors=remount-ro 0 $\r\n# \/dev\/sdd5\r\nUUID=****3 none swap sw 0 0\r\n\/dev\/scd0 \/media\/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0\r\n\r\n#\/dev\/nas\/backup\r\nUUID=****7 \/var\/nas\/backup ext3 relatime,noexec 0 2\r\n\r\n#\/dev\/nas\/pictures\r\nUUID=****8 \/var\/nas\/pictures ext3 relatime,noexec 0 2\r\n<\/pre>\n You shouldn’t have to change anything except add the lines at the bottom for the backup and pictures drives (or whatever you created) . Please use the UUID’s you found from blkid.<\/p>\n
Press ctrl-x to exit nano and save the file. <\/p>\n
Try a reboot and see how it works. Once you bring the system back up, open a terminal and type df. This will show you all mounted drives, and your new drives should be there.<\/p>\n","protected":false},"excerpt":{"rendered":"
Now that we have a raid array created, we are going to create some virtual drives. Why virtual drives? Well, we have one large terabyte drive right now, and if we just put folders in there, it can quickly get … Continue reading