Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
cancel
Showing results for 
Search instead for 
Did you mean: 
jmalla
Contributor
Hi Folks,

I am writing this BLOG about my experience trying to do XSA development on the SAP HANA Express edition on AWS and the space issues I ran into and how I addressed it.  If you are using the HANA Express Edition on AWS, and if you are running into strange behavior and space issues, this BLOG may be helpful.

I launched the SAP HANA, Express Edition on AWS through CAL.

Once it ran, I ran across many issues.

A few things to help out so that I could get start developing:

  • started nodejstools explicitly.

  • create a space and explicitly redeployed the builder using the di-space-enablement tool


I was encountering a lot of strange issues and then found out the they could be happening due to disk space issues.  The biggest issue I had was the the logical volume /dev/mapper/vga-sysfiles was getting filled up.  I started deleting log files and any files that were not necessary.  But this did not help.

I was having the issue of /dev/mapper/vga-sysfiles getting filled up to 100%.  I cleared the log files, and would start the system at 95% as shown here - but that would fill up to 100% relatively quickly.
sid-hxe:~ # df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/hda1 10189112 3035020 6613472 32% /
devtmpfs 15721704 8 15721696 1% /dev
tmpfs 40897116 0 40897116 0% /dev/shm
tmpfs 15730604 9900 15720704 1% /run
tmpfs 15730604 0 15730604 0% /sys/fs/cgroup
/dev/mapper/vgcal-sysfiles 42985920 40757896 2228024 95% /hana/shared/HXE
/dev/mapper/vgcal-dbdata 60819392 8848024 51971368 15% /hana/data/HXE
/dev/mapper/vgcal-dblog 33553344 2002172 31551172 6% /hana/log/HXE

 

So here are the steps.

Through the AWS EC2 console, click on Volumes under the ELASTIC BLOCK STORE option on the left sidebar window and then click on Create Volume:



 

I chose a 50 GB Magnetic volume type:



 

The volume is created.  Note the Volume ID.



Now attach this Volume to the instance (SAP HANA Express in my case)



 



Log into the SAP HANA system.

 

Extend the volume group vgcal (in my case) to include this new volume.  If you need the volume group, run vgdisplay and get the VG name
sid-hxe:~ # vgextend vgcal /dev/xvdt
Physical volume "/dev/xvdt" successfully created
Volume group "vgcal" successfully extended

 

Here is the file system:



 

Once the volume is attached, we need to extend the logical volume /dev/vgcal/sysfiles to use this volume - note the change from 41 GB to 91 GB:
sid-hxe:~ # lvextend -i 1 -r /dev/vgcal/sysfiles /dev/xvdt
Size of logical volume vgcal/sysfiles changed from 41.02 GiB (10500 extents) to 91.01 GiB (23299 extents).
Logical volume sysfiles successfully resized
meta-data=/dev/mapper/vgcal-sysfiles isize=256 agcount=16, agsize=671984 blks
= sectsz=512 attr=2, projid32bit=1
= crc=0 finobt=0
data = bsize=4096 blocks=10751744, imaxpct=25
= sunit=16 swidth=192 blks
naming =version 2 bsize=4096 ascii-ci=0 ftype=0
log =internal bsize=4096 blocks=5264, version=2
= sectsz=512 sunit=16 blks, lazy-count=1
realtime =none extsz=4096 blocks=0, rtextents=0
data blocks changed from 10751744 to 23858176

So the additional 50 GB is available now for /dev/mapper/vgcal-sysfiles
sid-hxe:~ # df -h
Filesystem Size Used Avail Use% Mounted on
/dev/hda1 9.8G 6.5G 2.8G 70% /
devtmpfs 15G 8.0K 15G 1% /dev
tmpfs 40G 0 40G 0% /dev/shm
tmpfs 16G 18M 15G 1% /run
tmpfs 16G 0 16G 0% /sys/fs/cgroup
/dev/mapper/vgcal-sysfiles 91G 41G 51G 45% /hana/shared/HXE
/dev/mapper/vgcal-dbdata 59G 8.5G 50G 15% /hana/data/HXE
/dev/mapper/vgcal-dblog 32G 2.0G 31G 6% /hana/log/HXE

 
sid-hxe:~ # lvdisplay
--- Logical volume ---
LV Path /dev/vgcal/dbdata
LV Name dbdata
VG Name vgcal
LV UUID trUgvA-oNiA-QHUM-HYMY-2URJ-bp4z-5YKYOQ
LV Write Access read/write
LV Creation host, time ip-10-0-22-11, 2017-09-01 11:26:20 +0000
LV Status available
# open 1
LV Size 58.03 GiB
Current LE 14856
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 3072
Block device 254:0

--- Logical volume ---
LV Path /dev/vgcal/dblog
LV Name dblog
VG Name vgcal
LV UUID 7TzNYT-bRRX-wbpA-L5xx-xAEO-RO5R-GpB2aN
LV Write Access read/write
LV Creation host, time ip-10-0-22-11, 2017-09-01 11:26:26 +0000
LV Status available
# open 1
LV Size 32.02 GiB
Current LE 8196
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 3072
Block device 254:1

--- Logical volume ---
LV Path /dev/vgcal/sysfiles
LV Name sysfiles
VG Name vgcal
LV UUID zCjmzn-yjgf-VENQ-HCW1-Af5J-TPAx-fOkEm0
LV Write Access read/write
LV Creation host, time ip-10-0-22-11, 2017-09-01 11:26:27 +0000
LV Status available
# open 1
LV Size 91.01 GiB
Current LE 23299
Segments 2
Allocation inherit
Read ahead sectors auto
- currently set to 3072
Block device 254:2

 

After I did this, the system was behaving much better and I could work on the XSA development.  More BLOGs to follow on the SAP HANA XSA development.  I did refer to the following  article: Increase disk space on AWS for SAP CAL system -
https://archive.sap.com/discussions/thread/3739935

But i added the additional steps to get this working for the instance.

 

Enjoy,

Jay

 

You can connect with me at - Jay Malla on LinkedIn

 
24 Comments
Labels in this area