# lvremove /dev/cinder-volumes/volume-cf5565aa-291c-49ba-a75c-6842d4655d34
Can't remove open logical volume "volume-cf5565aa-291c-49ba-a75c-6842d4655d34"

# fuser /dev/cinder-volumes/volume-cf5565aa-291c-49ba-a75c-6842d4655d34
/dev/dm-14:           1749
# lsof | grep /dev/dm-14
tgtd       1749       root   19u      BLK             252,14         0t0       8546 /dev/dm-14
# service tgt stop
tgt stop/waiting
# lvremove /dev/cinder-volumes/volume-cf5565aa-291c-49ba-a75c-6842d4655d34 
Do you really want to remove active logical volume volume-cf5565aa-291c-49ba-a75c-6842d4655d34? [y/n]: y
  Logical volume "volume-cf5565aa-291c-49ba-a75c-6842d4655d34" successfully removed

cryptsetup luksFormat /dev/vgtest/lvm1
#回车后，会要求输入大写的YES，然后就输入密码

cryptsetup luksOpen /dev/vgtest/lvm1 encryptLVM
#回车后，要求输入刚才加密时设置的密码，正确则会创建一个Device-Mapper文件，/dev/mapper/encryptLVM，错误则无法生成，也就无法挂载使用。
	
#格式化系统，并挂载使用
mkfs.ext3 /dev/mapper/encryptLVM
mkdir /mnt/crypt
mount /dev/mapper/encryptLVM /mnt/crypt

umount /mnt/crypt
cryptsetup luksClose /dev/mapper/encryptLVM

#! /bin/sh
# File path: ~/Yeelink/rpi_sensors.sh
apikey=<your api key>
url_cpu=http://api.yeelink.net/v1.0/device/<device no.>/sensor/<sensor no.>/datapoints
url_mem=http://api.yeelink.net/v1.0/device/<device no.>/sensor/<sensor no.>/datapoints
url_disk=http://api.yeelink.net/v1.0/device/<device no.>/sensor/<sensor no.>/datapoints
mem_used=$(free -m | grep "Mem" | egrep "[[:digit:]]+" -o | head -n 2 | tail -n 1)
cpu_load=$(iostat -c | tail -n 2 | egrep "[[:digit:].]+" -o | head -n 1)
disk_avaliable=$(df -l | grep "/dev/sda5" | egrep "[[:digit:]]+" -o | tail -n 3 | head -n 1)
disk_ava=`echo "$disk_avaliable/1024"|bc`
echo $disk_ava
curl -d "{\"value\":$mem_used}" -H "U-ApiKey: $apikey" $url_mem
curl -d "{\"value\":$cpu_load}" -H "U-ApiKey: $apikey" $url_cpu
curl -d "{\"value\":$disk_ava}" -H "U-Apikey: $apikey" $url_disk
exit 0

crontab -e

# Edit this file to introduce tasks to be run by cron.
#
# Each task to run has to be defined through a single line
# indicating with different fields when the task will be run
# and what command to run for the task
#
# To define the time you can provide concrete values for
# minute (m), hour (h), day of month (dom), month (mon),
# and day of week (dow) or use '*' in these fields (for 'any').#
# Notice that tasks will be started based on the cron's system
# daemon's notion of time and timezones.
#
# Output of the crontab jobs (including errors) is sent through
# email to the user the crontab file belongs to (unless redirected).
#
# For example, you can run a backup of all your user accounts
# at 5 a.m every week with:
# 0 5 * * 1 tar -zcf /var/backups/home.tgz /home/
#
# For more information see the manual pages of crontab(5) and cron(8)
#
# m h  dom mon dow   command
*/1 * * * * ~/Yeelink/rpi_sensors.sh