Wan Optimization Support
Technical => Installation => : mcooper06 March 27, 2014, 02:30:17 PM
-
This post demonstrates my lack of Linux skill more than anything -
I wrote the base image to a 120GB SATA disk and it works fine, but I would like to use the remaining capacity for caching as well. So my disk had a single partition of 4~GB labeled /dev/sda1. I created a second primary partition, /dev/sda2 using the remaining space.
I used this command to create a path: "sudo mkdir /mnt/sda2"
I then mounted the partition using: mount "sudo /dev/sda2 /mnt/sda2/"
I then created a subdirectory on this newly mounted drive using this command: "sudo mkdir -p /mnt/sda2/wanos/ds0"
I then edited the bootlocal.sh script using the command: "sudo vi /opt/bootlocal.sh"
I have added the line: "mount /dev/sda2 /mnt/sda2"
I have added the line: "ln -s /mnt/sda2/wanos /wanos"
I have commented out the line: "ln -s /mnt/sda1/wanos /wanos"
I thought this would do the trick, and the system boots fine, but when I go into the interface, I am shown that the Datastore Disk is still /dev/sda1 and I was thinking it should be /dev/sda2.
Michael
-
Hi Michael,
Looks like you are doing everything 100% right. That sda1 in the GUI could be a cosmetic bug. You can verify where the datastore is actually at by running 'ls -la /wanos'
-
/wanos -> /mnt/sda2/wanos/
OK - So it seems like it's good then! Thank you so much.
Michael
-
Ok, thanks for the feedback, fixed in 0.1.8
-
Since v2.0.2
steps:
sudo su
/tce/etc/wanos/wanos-fdisk sda
reboot
mkfs.ext3 /dev/sda2
reboot
set the datastore to sda2 in the UI
This is based on the assumption that the only drive installed is sda and that is where the un-partitioned free space is located.