深海游弋的鱼 – 第 111 页 – 智障儿童欢乐多

Ubuntu 16.04.3系统上OpenPTrack V1版本安装配置(Kinect V2)

对于Ubuntu 14.04.5系统上的安装操作，请参考Ubuntu 14.04.5系统上OpenPTrack V1版本安装配置(Kinect V2)

下面是我自己fork出来修改后的代码在Ubuntu 16.04.3系统上的安装操作

要求机器上必须有CUDA 8.0/9.0支持的显卡才可以。

1.从GitHub上获取项目代码

$ sudo apt-get install git -y
$ cd ~
$ git clone https://github.com/wangqiang1588/open_ptrack_org.git open_ptrack

$ sudo apt-get install git -y

$ cd ~

$ git clone https://github.com/wangqiang1588/open_ptrack_org.git open_ptrack

2.安装ROS

$ cd open_ptrack/scripts
$ chmod +x *.sh
$ ./ros_install.sh

$ source /opt/ros/kinetic/setup.bash
$ ./ros_configure.sh

$ cd open_ptrack/scripts

$ chmod +x *.sh

$ ./ros_install.sh

$ source /opt/ros/kinetic/setup.bash

$ ./ros_configure.sh

3.安装`OpenPTrack`

$ sudo apt-get install libdrm-dev

$ ./openptrack_install.sh

$ sudo apt-get install libdrm-dev

$ ./openptrack_install.sh

4.链接`OpenPTrack`目录

$ ln -s  ~/workspace/ros/catkin/src/open_ptrack ~/open_ptrack

1	$ ln -s ~/workspace/ros/catkin/src/open_ptrack ~/open_ptrack

5.`Kinect V2`驱动程序安装

检查当前用户目录下的.bashrc文件，注释掉如下内容：

export KINECT_DRIVER=openni

1	export KINECT_DRIVER=openni

然后执行如下命令：

# Nvidia Jetson TX1/TX2 不要安装这个
$ sudo apt-get install nvidia-375-dev

# Nvidia Jetson TX1/TX2不支持OpenCL,因此编译的时候，不要安装ocl-icd-opencl-dev
$ sudo apt-get install ocl-icd-opencl-dev

$ sudo apt-get install m4
$ sudo apt-get install automake
$ sudo apt-get install libjpeg-dev
$ sudo ln -s -f /usr/lib/`uname -m`-linux-gnu/libturbojpeg.so.0 /usr/lib/`uname -m`-linux-gnu/libturbojpeg.so
$ sudo apt-get install libglewmx-dev
$ sudo apt-get install libudev-dev
$ sudo ln -s -f /lib/`uname -m`-linux-gnu/libudev.so.1 /lib/`uname -m`-linux-gnu/libudev.so

$ cd ~/workspace/ros/catkin/src
$ source ~/.profile 
$ roscd open_ptrack/../scripts
$ chmod +x kinect2_install.sh
$ ./kinect2_install.sh

# Nvidia Jetson TX1/TX2 不要安装这个

$ sudo apt-get install nvidia-375-dev

# Nvidia Jetson TX1/TX2不支持OpenCL,因此编译的时候，不要安装ocl-icd-opencl-dev

$ sudo apt-get install ocl-icd-opencl-dev

$ sudo apt-get install m4

$ sudo apt-get install automake

$ sudo apt-get install libjpeg-dev

$ sudo ln -s -f /usr/lib/`uname -m`-linux-gnu/libturbojpeg.so.0 /usr/lib/`uname -m`-linux-gnu/libturbojpeg.so

$ sudo apt-get install libglewmx-dev

$ sudo apt-get install libudev-dev

$ sudo ln -s -f /lib/`uname -m`-linux-gnu/libudev.so.1 /lib/`uname -m`-linux-gnu/libudev.so

$ cd ~/workspace/ros/catkin/src

$ source ~/.profile

$ roscd open_ptrack/../scripts

$ chmod +x kinect2_install.sh

$ ./kinect2_install.sh

6.重新编译代码

UBUNTU_VERSION=`lsb_release -c -s`
ROS_DISTRO=hydro

if [ $UBUNTU_VERSION = trusty ] || [ $UBUNTU_VERSION = saucy ] ; then
  ROS_DISTRO=indigo
elif [ $UBUNTU_VERSION = xenial ] ; then
  ROS_DISTRO=kinetic
fi

GCC_VERSION=`gcc -dumpversion | cut -f1 -d.`
source /opt/ros/$ROS_DISTRO/setup.bash 
cd ~/workspace/ros/catkin
catkin_make --pkg calibration_msgs
catkin_make --pkg opt_msgs
#GCC 5 bug out of memory
if [ $GCC_VERSION > 4 ] ; then
  catkin_make --force-cmake -j 1
else
  catkin_make --force-cmake
fi

UBUNTU_VERSION=`lsb_release -c -s`

ROS_DISTRO=hydro

if [ $UBUNTU_VERSION = trusty ] || [ $UBUNTU_VERSION = saucy ] ; then

ROS_DISTRO=indigo

elif [ $UBUNTU_VERSION = xenial ] ; then

ROS_DISTRO=kinetic

GCC_VERSION=`gcc -dumpversion | cut -f1 -d.`

source /opt/ros/$ROS_DISTRO/setup.bash

cd ~/workspace/ros/catkin

catkin_make --pkg calibration_msgs

catkin_make --pkg opt_msgs

#GCC 5 bug out of memory

if [ $GCC_VERSION > 4 ] ; then

catkin_make --force-cmake -j 1

else

catkin_make --force-cmake

执行如下命令：

$ roscore

$ roscore

检查当前用户目录下的.bashrc文件，然后注释掉如下内容：

export KINECT_DRIVER=openni

1	export KINECT_DRIVER=openni

上面语句如不注释，会导致程序启动时候的崩溃。

新建一个Shell,执行如下命令

$ cd ~/workspace/ros/catkin/devel/lib/kinect2_bridge
$ sudo ./kinect2_bridge

1 2	$ cd ~/workspace/ros/catkin/devel/lib/kinect2_bridge $ sudo ./kinect2_bridge

执行此步的时候如果提示找不到Kinect设备，请重启一下系统再试试。

7.测试系统

可能需要重新插拔一下Kinect的USB数据线，然后执行如下命令

$ roslaunch kinect2_bridge kinect2_bridge.launch

1	$ roslaunch kinect2_bridge kinect2_bridge.launch

执行之后，等待十几秒，然后Ctrl+C中断执行。
执行完成后，执行

$ roslaunch tracking detection_and_tracking_kinect2.launch

1	$ roslaunch tracking detection_and_tracking_kinect2.launch

之后，会弹出三个界面出来。

参考链接

Kinect V2 深度图与彩色图融合(Ubuntu 14.04)

参考Kinect V2在Ubuntu 14.04系统上的驱动配置与安装在一个全新安装的Ubuntu 14.04系统中配置完成相关的驱动及其依赖。

Kinect V2深度图与彩色图融合的方式，简单粗暴，由于深度图像是512*424大小，因此，直接把彩色图像缩放成对应的512*424，然后像素点一一对应。至于原始大小的彩色图像，那么就是一片像素对应同一个深度即可。

注意，这个方式只适合Kinect V2，可以理解成Kinect V2的设计就是这样的，两个设备出厂的时候就校准为这样的输出。

具体的转换代码参考registration.cpp,Registration.cpp，建议直接调用驱动层提供的功能来实现，这样的话，一系列的参数设置可以同步，否则上层每次修改了分辨率等参数的时候，要自己手工修改这些数据。

Python深度图与彩色图融合的例子如下：

参考连接

Debian：如何从Jessie升级为Stretch(Debian 8.0 升级到Debian 9.0）

Debian 9（代号为Stretch）已经正式发布，可以开始尝鲜Debian 9了。

1. 更新Debian Jessie到最新版

$ su

$ apt-get update

$ apt-get upgrade

$ apt-get dist-upgrade

$ su

$ apt-get update

$ apt-get upgrade

$ apt-get dist-upgrade

2. 将软件源改为Stretch安装源

$ su

$ sed -i 's/jessie/stretch/g' /etc/apt/sources.list

# 替换成国内镜像源(清华大学)
$ sed -i 's/deb.debian.org/mirrors.tuna.tsinghua.edu.cn/g' /etc/apt/sources.list

$ sed -i 's/security.debian.org/mirrors.tuna.tsinghua.edu.cn\/debian-security/g' /etc/apt/sources.list

$ su

$ sed -i 's/jessie/stretch/g' /etc/apt/sources.list

# 替换成国内镜像源(清华大学)

$ sed -i 's/deb.debian.org/mirrors.tuna.tsinghua.edu.cn/g' /etc/apt/sources.list

$ sed -i 's/security.debian.org/mirrors.tuna.tsinghua.edu.cn\/debian-security/g' /etc/apt/sources.list

3. 升级系统版本

$ su

$ apt-get update

$ apt-get dist-upgrade

$ su

$ apt-get update

$ apt-get dist-upgrade

4. 重启

$ su

$ reboot

$ su

$ reboot

参考链接

Debian：如何从 Jessie 升级为 Stretch

Kinect V2在Ubuntu 14.04系统上的驱动配置与安装

以下的操作是在一个全新安装的Ubuntu 14.04系统上进行的，目前已知在安装了ROS的系统上并且已经安装过ROS版本的Kinect V2驱动的,可能需要先移除以前安装的面向ROS编译的Kinect V2驱动才行。

首先是安装配置驱动程序以及运行依赖库

$ sudo apt-get update

$ sudo apt-get upgrade

$ sudo apt-get dist-upgrade

$ sudo apt-get install python-opencv

$ sudo apt-get install python-dev

$ sudo apt-get install python-pip

$ sudo pip install openni

$ sudo apt-get install git

$ sudo apt-get update

$ sudo apt-get upgrade

$ sudo apt-get dist-upgrade

$ sudo apt-get install python-opencv

$ sudo apt-get install python-dev

$ sudo apt-get install python-pip

$ sudo pip install openni

$ sudo apt-get install git

参照libfreenect2 install linux的说明安装驱动

$ cd ~ 

$ git clone https://github.com/OpenKinect/libfreenect2.git

$ cd libfreenect2

$ cd depends; ./download_debs_trusty.sh

$ sudo dpkg -i debs/libusb*deb

$ sudo apt-get install build-essential cmake pkg-config

#如果没有配置ROS源，则使用这个源，否则不需要此步骤
$ sudo apt-add-repository ppa:deb-rob/ros-trusty && sudo apt-get update

$ sudo apt-get install libopenni2-dev

$ sudo apt-get install libjpeg-dev

$ sudo apt-get install libturbojpeg

$ sudo apt-get install libgl1-mesa-dev

$ sudo apt-get install ocl-icd-opencl-dev

#如果要启用CUDA的支持，只能是从nvidia官网下载安装最新版本才行，apt安装的版本会缺少 “ helper_math.h ”
# $ wget https://developer.nvidia.com/compute/cuda/8.0/Prod2/local_installers/cuda-repo-ubuntu1404-8-0-local-ga2_8.0.61-1_amd64-deb
# $ sudo apt-get update
# $ sudo apt-get install cuda

$ cd ..

$ git clean -xfd 

$ mkdir build && cd build

##如果在安装过ROS的系统上执行，并且已经通过ROS安装过libfreenect2驱动，可能下面的要调整成“cmake .. -DCMAKE_INSTALL_PREFIX=/usr/” 才能成功覆盖已经安装过的文件
$ cmake .. -DCMAKE_INSTALL_PREFIX=/usr/local/

$ make

$ sudo make install

$ cd ~

$ git clone https://github.com/OpenKinect/libfreenect2.git

$ cd libfreenect2

$ cd depends; ./download_debs_trusty.sh

$ sudo dpkg -i debs/libusb*deb

$ sudo apt-get install build-essential cmake pkg-config

#如果没有配置ROS源，则使用这个源，否则不需要此步骤

$ sudo apt-add-repository ppa:deb-rob/ros-trusty && sudo apt-get update

$ sudo apt-get install libopenni2-dev

$ sudo apt-get install libjpeg-dev

$ sudo apt-get install libturbojpeg

$ sudo apt-get install libgl1-mesa-dev

$ sudo apt-get install ocl-icd-opencl-dev

#如果要启用CUDA的支持，只能是从nvidia官网下载安装最新版本才行，apt安装的版本会缺少 “ helper_math.h ”

# $ wget https://developer.nvidia.com/compute/cuda/8.0/Prod2/local_installers/cuda-repo-ubuntu1404-8-0-local-ga2_8.0.61-1_amd64-deb

# $ sudo apt-get update

# $ sudo apt-get install cuda

$ cd ..

$ git clean -xfd

$ mkdir build && cd build

##如果在安装过ROS的系统上执行，并且已经通过ROS安装过libfreenect2驱动，可能下面的要调整成“cmake .. -DCMAKE_INSTALL_PREFIX=/usr/” 才能成功覆盖已经安装过的文件

$ cmake .. -DCMAKE_INSTALL_PREFIX=/usr/local/

$ make

$ sudo make install

安装Python扩展

$ cd ~

$ sudo pip install cython

$ sudo pip install numpy

$ git clone https://github.com/remexre/pyfreenect2.git

$ cd pyfreenect2 

$ sudo python setup.py install

$ sudo apt-get install gfortran

$ sudo apt-get install libopenblas-dev

$ sudo apt-get install liblapack-dev

$ sudo pip install scipy

$ cd ~

$ sudo pip install cython

$ sudo pip install numpy

$ git clone https://github.com/remexre/pyfreenect2.git

$ cd pyfreenect2

$ sudo python setup.py install

$ sudo apt-get install gfortran

$ sudo apt-get install libopenblas-dev

$ sudo apt-get install liblapack-dev

$ sudo pip install scipy

Python例子如下：

$ cd ~/pyfreenect2

$ python test.py

$ cd ~/pyfreenect2

$ python test.py

注意，如果编译的时候出现如下错误：

[  5%] Building NVCC (Device) object CMakeFiles/cuda_compile.dir/src/./cuda_compile_generated_cuda_kde_depth_packet_processor.cu.o
nvcc warning : The 'compute_20', 'sm_20', and 'sm_21' architectures are deprecated, and may be removed in a future release (Use -Wno-deprecated-gpu-targets to suppress warning).
nvcc warning : The 'compute_20', 'sm_20', and 'sm_21' architectures are deprecated, and may be removed in a future release (Use -Wno-deprecated-gpu-targets to suppress warning).
~/libfreenect2/src/cuda_kde_depth_packet_processor.cu(1346): error: name followed by "::" must be a class or namespace name

~/libfreenect2/src/cuda_kde_depth_packet_processor.cu(1346): error: explicit type is missing ("int" assumed)

/home/libfreenect2/src/cuda_kde_depth_packet_processor.cu(1346): error: expected a "{"

~/libfreenect2/src/cuda_kde_depth_packet_processor.cu(1349): warning: missing return statement at end of non-void function "libfreenect2::CudaKdeDepthPacketProcessor"

~/libfreenect2/src/cuda_kde_depth_packet_processor.cu(1351): error: name followed by "::" must be a class or namespace name

~/libfreenect2/src/cuda_kde_depth_packet_processor.cu(1353): error: identifier "impl_" is undefined

/home/libfreenect2/src/cuda_kde_depth_packet_processor.cu(1356): error: name followed by "::" must be a class or namespace name

~/libfreenect2/src/cuda_kde_depth_packet_processor.cu(1358): error: a nonstatic member reference must be relative to a specific object

~/libfreenect2/src/cuda_kde_depth_packet_processor.cu(1360): error: identifier "impl_" is undefined

~/libfreenect2/src/cuda_kde_depth_packet_processor.cu(1363): error: name followed by "::" must be a class or namespace name

~/libfreenect2/src/cuda_kde_depth_packet_processor.cu(1365): error: identifier "impl_" is undefined

~/libfreenect2/src/cuda_kde_depth_packet_processor.cu(1369): error: name followed by "::" must be a class or namespace name

~/libfreenect2/src/cuda_kde_depth_packet_processor.cu(1371): error: identifier "impl_" is undefined

~/libfreenect2/src/cuda_kde_depth_packet_processor.cu(1378): error: name followed by "::" must be a class or namespace name

~/libfreenect2/src/cuda_kde_depth_packet_processor.cu(1380): error: identifier "impl_" is undefined

~/libfreenect2/src/cuda_kde_depth_packet_processor.cu(1383): error: name followed by "::" must be a class or namespace name

~/libfreenect2/src/cuda_kde_depth_packet_processor.cu(1385): error: identifier "impl_" is undefined

~/libfreenect2/src/cuda_kde_depth_packet_processor.cu(1388): error: name followed by "::" must be a class or namespace name

~/libfreenect2/src/cuda_kde_depth_packet_processor.cu(1390): error: identifier "listener_" is undefined

~/libfreenect2/src/cuda_kde_depth_packet_processor.cu(1393): error: identifier "impl_" is undefined

~/libfreenect2/src/cuda_kde_depth_packet_processor.cu(1415): error: name followed by "::" must be a class or namespace name

~/libfreenect2/src/cuda_kde_depth_packet_processor.cu(1417): error: identifier "impl_" is undefined

~/longsky/libfreenect2/src/cuda_kde_depth_packet_processor.cu(413): warning: function "calculatePhaseUnwrappingVarDirect" was declared but never referenced

21 errors detected in the compilation of "/tmp/tmpxft_00004ae7_00000000-7_cuda_kde_depth_packet_processor.cpp1.ii".
CMake Error at cuda_compile_generated_cuda_kde_depth_packet_processor.cu.o.cmake:264 (message):
  Error generating file
  ~/libfreenect2/build/CMakeFiles/cuda_compile.dir/src/./cuda_compile_generated_cuda_kde_depth_packet_processor.cu.o


make[2]: *** [CMakeFiles/cuda_compile.dir/src/./cuda_compile_generated_cuda_kde_depth_packet_processor.cu.o] Error 1
make[1]: *** [CMakeFiles/freenect2.dir/all] Error 2
make: *** [all] Error 2

[ 5%] Building NVCC (Device) object CMakeFiles/cuda_compile.dir/src/./cuda_compile_generated_cuda_kde_depth_packet_processor.cu.o

nvcc warning : The 'compute_20', 'sm_20', and 'sm_21' architectures are deprecated, and may be removed in a future release (Use -Wno-deprecated-gpu-targets to suppress warning).

~/libfreenect2/src/cuda_kde_depth_packet_processor.cu(1346): error: name followed by "::" must be a class or namespace name

~/libfreenect2/src/cuda_kde_depth_packet_processor.cu(1346): error: explicit type is missing ("int" assumed)

/home/libfreenect2/src/cuda_kde_depth_packet_processor.cu(1346): error: expected a "{"

~/libfreenect2/src/cuda_kde_depth_packet_processor.cu(1349): warning: missing return statement at end of non-void function "libfreenect2::CudaKdeDepthPacketProcessor"

~/libfreenect2/src/cuda_kde_depth_packet_processor.cu(1351): error: name followed by "::" must be a class or namespace name

~/libfreenect2/src/cuda_kde_depth_packet_processor.cu(1353): error: identifier "impl_" is undefined

/home/libfreenect2/src/cuda_kde_depth_packet_processor.cu(1356): error: name followed by "::" must be a class or namespace name

~/libfreenect2/src/cuda_kde_depth_packet_processor.cu(1358): error: a nonstatic member reference must be relative to a specific object

~/libfreenect2/src/cuda_kde_depth_packet_processor.cu(1360): error: identifier "impl_" is undefined

~/libfreenect2/src/cuda_kde_depth_packet_processor.cu(1363): error: name followed by "::" must be a class or namespace name

~/libfreenect2/src/cuda_kde_depth_packet_processor.cu(1365): error: identifier "impl_" is undefined

~/libfreenect2/src/cuda_kde_depth_packet_processor.cu(1369): error: name followed by "::" must be a class or namespace name

~/libfreenect2/src/cuda_kde_depth_packet_processor.cu(1371): error: identifier "impl_" is undefined

~/libfreenect2/src/cuda_kde_depth_packet_processor.cu(1378): error: name followed by "::" must be a class or namespace name

~/libfreenect2/src/cuda_kde_depth_packet_processor.cu(1380): error: identifier "impl_" is undefined

~/libfreenect2/src/cuda_kde_depth_packet_processor.cu(1383): error: name followed by "::" must be a class or namespace name

~/libfreenect2/src/cuda_kde_depth_packet_processor.cu(1385): error: identifier "impl_" is undefined

~/libfreenect2/src/cuda_kde_depth_packet_processor.cu(1388): error: name followed by "::" must be a class or namespace name

~/libfreenect2/src/cuda_kde_depth_packet_processor.cu(1390): error: identifier "listener_" is undefined

~/libfreenect2/src/cuda_kde_depth_packet_processor.cu(1393): error: identifier "impl_" is undefined

~/libfreenect2/src/cuda_kde_depth_packet_processor.cu(1415): error: name followed by "::" must be a class or namespace name

~/libfreenect2/src/cuda_kde_depth_packet_processor.cu(1417): error: identifier "impl_" is undefined

~/longsky/libfreenect2/src/cuda_kde_depth_packet_processor.cu(413): warning: function "calculatePhaseUnwrappingVarDirect" was declared but never referenced

21 errors detected in the compilation of "/tmp/tmpxft_00004ae7_00000000-7_cuda_kde_depth_packet_processor.cpp1.ii".

CMake Error at cuda_compile_generated_cuda_kde_depth_packet_processor.cu.o.cmake:264 (message):

Error generating file

~/libfreenect2/build/CMakeFiles/cuda_compile.dir/src/./cuda_compile_generated_cuda_kde_depth_packet_processor.cu.o

make[2]: *** [CMakeFiles/cuda_compile.dir/src/./cuda_compile_generated_cuda_kde_depth_packet_processor.cu.o] Error 1

make[1]: *** [CMakeFiles/freenect2.dir/all] Error 2

make: *** [all] Error 2

则该现象出现的原因是首先参照

cmake .. -DCMAKE_INSTALL_PREFIX=$HOME/freenect2

1	cmake .. -DCMAKE_INSTALL_PREFIX=$HOME/freenect2

进行了编译，并且编译的时候是没有开启CUDA支持的。

然后执行了

$ make install

1	$ make install

因此在~/libfreenect2/include/libfreenect2/下面已经生成了config.h，export.h这两个文件。
然后又按照我们这里的

cmake .. -DCMAKE_INSTALL_PREFIX=/usr/local/

1	cmake .. -DCMAKE_INSTALL_PREFIX=/usr/local/

重新编译，并且这次开启了CUDA支持，导致GCC在编译的时候使用了我们在~/libfreenect2/build/libfreenect2/下面生成的config.h，export.h这两个文件，而NVCC却使用了~/libfreenect2/include/libfreenect2/下面的config.h，export.h进行编译，导致上面的错误发生。

因此删除全部的临时文件,然后再次重新编译即可。

参考连接

Ubuntu 14.04.5系统上OpenPTrack V1版本双Kinect V2简单校准

参照Ubuntu 14.04.5系统上OpenPTrack V1版本安装配置(Kinect V2)配置安装完成后，是单台机器的方式。

如果场地比较大，则需要部署多个Kinect V2。由于每台Kinect V2看到同一个人的视角不同，因此需要校准，才能进行合并。

下面，我们用两台PC+两个Kinect V2(每台机器上连接一个Kinect V2）来演示一下如何校准的操作。

继续阅读Ubuntu 14.04.5系统上OpenPTrack V1版本双Kinect V2简单校准

OpenMdeiaValut 3.0.86上编译Linux Kernel 4.13-rc6/Linux Kernel 4.13-rc7/Linux Kernel 4.13 Mainline

也可以使用下面的方式正常编译Linux Kernel 4.13-rc7/Linux Kernel 4.13 Mainline。

建议使用VirtualBox上建立虚拟机，保证磁盘空间不小于32GB，给root用户设置密码，远程通过shell登录到虚拟机。

查询虚拟机的IP地址的时候，使用

$ /sbin/ifconfig

1	$ /sbin/ifconfig

命令查询。虚拟机网卡设置的时候，设置为桥接模式，默认的NAT模式无法通过SSH登录。

然后执行如下命令：

$ cd ~

$ wget https://git.kernel.org/torvalds/t/linux-4.13-rc6.tar.gz -O linux-4.13-rc6.tar.gz

$ tar -zxvf linux-4.13-rc6.tar.gz

$ cd linux-4.13-rc6/

# 升级系统工具，如果不更新，有时候会出现无法编译的情况
$ sudo apt-get update

$ sudo apt-get upgrade

$ sudo apt-get install make

$ sudo apt-get install build-essential

$ sudo apt-get install kernel-package

$ sudo apt-get install ncurses-dev

#一路回车到底
$ make oldconfig

$ make-kpkg --initrd kernel-image kernel_headers

$ cd ~

$ wget https://git.kernel.org/torvalds/t/linux-4.13-rc6.tar.gz -O linux-4.13-rc6.tar.gz

$ tar -zxvf linux-4.13-rc6.tar.gz

$ cd linux-4.13-rc6/

# 升级系统工具，如果不更新，有时候会出现无法编译的情况

$ sudo apt-get update

$ sudo apt-get upgrade

$ sudo apt-get install make

$ sudo apt-get install build-essential

$ sudo apt-get install kernel-package

$ sudo apt-get install ncurses-dev

#一路回车到底

$ make oldconfig

$ make-kpkg --initrd kernel-image kernel_headers

完成后，在当前用户目录下生成linux-image-4.13.0-rc6_4.13.0-rc6-10.00.Custom_amd64.deb安装包,执行如下命令安装：

$ cd ~

$ sudo dpkg -i linux-image-4.13.0-rc6_4.13.0-rc6-10.00.Custom_amd64.deb

$ cd ~

$ sudo dpkg -i linux-image-4.13.0-rc6_4.13.0-rc6-10.00.Custom_amd64.deb

参考链接

Ubuntu 14.04系统上Python使用"subprocess.Popen"执行"source"命令报告错误“/bin/sh: source: not found”

使用如下的例子中的代码

import subprocess
def execShellCommand(cmd):
    print cmd
    p = subprocess.Popen(cmd, shell=True, stdout=subprocess.PIPE, stderr=subprocess.STDOUT)
    while True:  
        buff = p.stdout.readline()  
        if buff == '' and p.poll() != None:  
            break
        print buff
    p.wait()


def main():
    execShellCommand("source ~/.profile")

if __name__ == "__main__":
    main()

import subprocess

def execShellCommand(cmd):

print cmd

p = subprocess.Popen(cmd, shell=True, stdout=subprocess.PIPE, stderr=subprocess.STDOUT)

while True:

buff = p.stdout.readline()

if buff == '' and p.poll() != None:

break

print buff

p.wait()

def main():

execShellCommand("source ~/.profile")

if __name__ == "__main__":

main()

运行的时候报告错误

source ~/.profile
/bin/sh: 1: source: not found

1 2	source ~/.profile /bin/sh: 1: source: not found

这个错误发生的原因是subprocess.Popen执行Shell命令的时候默认调用/bin/sh，而source命令/bin/bash才支持的，因此导致错误发生，修改后的脚本如下：

import subprocess
def execShellCommand(cmd):
    print cmd
    p = subprocess.Popen(cmd, shell=True, stdout=subprocess.PIPE, stderr=subprocess.STDOUT,executable="/bin/bash")
    while True:  
        buff = p.stdout.readline()  
        if buff == '' and p.poll() != None:  
            break
        print buff
    p.wait()


def main():
    execShellCommand("source ~/.profile")

if __name__ == "__main__":
    main()

import subprocess

def execShellCommand(cmd):

print cmd

p = subprocess.Popen(cmd, shell=True, stdout=subprocess.PIPE, stderr=subprocess.STDOUT,executable="/bin/bash")

while True:

buff = p.stdout.readline()

if buff == '' and p.poll() != None:

break

print buff

p.wait()

def main():

execShellCommand("source ~/.profile")

if __name__ == "__main__":

main()

注意添加的executable="/bin/bash"，指明了执行脚本的执行程序是/bin/bash。

参考链接

Calling the “source” command from subprocess.Popen

OpenMediaVault 3.0.87数据分区文件系统从EXT4升级到BTRFS并启用压缩特性

自己搭建的NAS使用的是OpenMediaVault 3.0.87,默认的磁盘系统分区是EXT4数据分区格式，并且没有搭建RAID阵列，暂时不建议RAID阵列执行升级操作。

某些磁盘已经空间非常紧张了，希望能使用像微软的NTFS格式相同的磁盘数据压缩功能，但是遗憾的是EXT4数据分区格式是不支持数据压缩的。因此有必要升级到BTRFS数据分区格式。

另外，OpenMediaVault 3.0.87的Linux内核已经更新到Linux Kernel 4.9.0能够非常好的支持BTRFS数据分区格式了，因此尝试升级到BTRFS数据分区格式。

在执行如下操作之前，请确定已经启用了OpenMediaVault的SSH远程登录功能。

首先，确定数据分区的挂载位置

root@openmediavault:~# df
文件系统            1K-块       已用       可用 已用% 挂载点
udev                10240          0      10240    0% /dev
tmpfs              788476       9204     779272    2% /run
/dev/sdc1         3589076    1795968    1591076   54% /
tmpfs             1971180          0    1971180    0% /dev/shm
tmpfs                5120          0       5120    0% /run/lock
tmpfs             1971180          0    1971180    0% /sys/fs/cgroup
tmpfs             1971180          0    1971180    0% /tmp
/dev/sda1      2884137588 1282636316 1601484888   45% /media/7948f871-78ff-4448-a0e7-ad508359238e
/dev/sdb1      3845558068 2094208152 1751333532   55% /media/9b5fcef5-6c5a-4478-80a8-41ae6cb9dce3
/dev/sdd1      2884137588 2865971516   18149688  100% /media/7909fba8-cc50-430f-986f-9db4ba7caa3c

root@openmediavault:~# df

文件系统 1K-块已用可用已用% 挂载点

udev 10240 0 10240 0% /dev

tmpfs 788476 9204 779272 2% /run

/dev/sdc1 3589076 1795968 1591076 54% /

tmpfs 1971180 0 1971180 0% /dev/shm

tmpfs 5120 0 5120 0% /run/lock

tmpfs 1971180 0 1971180 0% /sys/fs/cgroup

tmpfs 1971180 0 1971180 0% /tmp

/dev/sda1 2884137588 1282636316 1601484888 45% /media/7948f871-78ff-4448-a0e7-ad508359238e

/dev/sdb1 3845558068 2094208152 1751333532 55% /media/9b5fcef5-6c5a-4478-80a8-41ae6cb9dce3

/dev/sdd1 2884137588 2865971516 18149688 100% /media/7909fba8-cc50-430f-986f-9db4ba7caa3c

如上所示，我们看到有三个磁盘的挂载，分别挂载在/dev/sda1 ,/dev/sdb1 , /dev/sdd1。

我们接下来以/dev/sda1分区为例：

$ umount /dev/sda1

$ btrfs-convert /dev/sda1

$ umount /dev/sda1

$ btrfs-convert /dev/sda1

几个小时后（3TB），会输出如下信息：

creating btrfs metadata.
creating ext2fs image file.
cleaning up system chunk.
conversion complete.

creating btrfs metadata.

creating ext2fs image file.

cleaning up system chunk.

conversion complete.

表示已经转换完成了。

注意，转换完成后磁盘的UUID会发生变化，需要重新手工修正。

$ blkid /dev/sda1

1	$ blkid /dev/sda1

得到如下输出：

/dev/sda1: UUID="6357625f-c966-49ba-9c90-9e8f8ff50433" UUID_SUB="cd51e4cf-1b77-488a-ae29-d4669c0a4cdd" TYPE="btrfs" PARTUUID="82b68e98-9341-4095-b152-f51f00c2e577"

1	/dev/sda1: UUID="6357625f-c966-49ba-9c90-9e8f8ff50433" UUID_SUB="cd51e4cf-1b77-488a-ae29-d4669c0a4cdd" TYPE="btrfs" PARTUUID="82b68e98-9341-4095-b152-f51f00c2e577"

接下来，调整磁盘加载参数

$ cp /etc/openmediavault/config.xml /etc/openmediavault/config.xml.bak
$ sed -i 's/7948f871-78ff-4448-a0e7-ad508359238e/6357625f-c966-49ba-9c90-9e8f8ff50433/g' /etc/openmediavault/config.xml

1 2	$ cp /etc/openmediavault/config.xml /etc/openmediavault/config.xml.bak $ sed -i 's/7948f871-78ff-4448-a0e7-ad508359238e/6357625f-c966-49ba-9c90-9e8f8ff50433/g' /etc/openmediavault/config.xml

找到

<mntent>
  <uuid>95ed6452-f93d-4092-af4a-c72e138f0072</uuid>
  <fsname>6357625f-c966-49ba-9c90-9e8f8ff50433</fsname>
  <dir>/media/6357625f-c966-49ba-9c90-9e8f8ff50433</dir>
  <type>ext4</type>
  <opts>defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl</opts>
  <freq>0</freq>
  <passno>2</passno>
  <hidden>0</hidden>
</mntent>

<dir>/media/6357625f-c966-49ba-9c90-9e8f8ff50433</dir>

<opts>defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl</opts>

</mntent>

修改为

<mntent>
  <uuid>95ed6452-f93d-4092-af4a-c72e138f0072</uuid>
  <fsname>6357625f-c966-49ba-9c90-9e8f8ff50433</fsname>
  <dir>/media/6357625f-c966-49ba-9c90-9e8f8ff50433</dir>
  <type>btrfs</type>
  <opts>defaults,nofail,noexec,acl,compress=lzo,autodefrag,commit=0,noatime</opts>
  <freq>0</freq>
  <passno>2</passno>
  <hidden>0</hidden>
</mntent>

<dir>/media/6357625f-c966-49ba-9c90-9e8f8ff50433</dir>

<type>btrfs</type>

<opts>defaults,nofail,noexec,acl,compress=lzo,autodefrag,commit=0,noatime</opts>

</mntent>

注意我们增加的参数，分别是修改文件系统格式从ext4修改为btrfs,同时增加了几个关键参数

compress=lzo,autodefrag,commit=0,noatime

1	compress=lzo,autodefrag,commit=0,noatime

其中的compress为压缩算法，目前我们指定lzo压缩。autodefrag为自动碎片整理，提升我们的性能。commit为数据提交的延迟，默认是30秒，适当增加时间可以提升磁盘性能，但是可能在突然断电的时候造成数据的丢失，由于我们是NAS，数据安全性第一，因此正时间被设置成0，要求文件系统在修改后立即刷新到磁盘上，放置数据丢失。另外强烈建议增加noatime参数，这个参数是要求系统不必在每次访问文件的时候都修改最后一次的访问时间，可以明显提升服务器性能，尤其是对于NAS服务器来说，除非是安全审计需要，否在完全没必要使用文件访问时间。

另外注意我们移除的参数

user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0

1	user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0

这几个参数是btrfs不支持的。

完成后重启系统

$ omv-mkconf fstab

$ sudo reboot

$ omv-mkconf fstab

$ sudo reboot

注意，上面的操作完成后，并不会真正压缩已经存在的文件，只压缩以后创建的文件

$ cd /media/6357625f-c966-49ba-9c90-9e8f8ff50433

$ btrfs filesystem defragment -r -v -clzo .

$ cd /media/6357625f-c966-49ba-9c90-9e8f8ff50433

$ btrfs filesystem defragment -r -v -clzo .

上面的整个过程执行之后，会发现磁盘占用实际上是增加了的，这个不必在意，属于btrfs的特性，到一定程度会自动回收空间的。

如果想手工回收这部分空间，执行如下命令即可:

$ cd /media/6357625f-c966-49ba-9c90-9e8f8ff50433

$ btrfs balance start -v -dusage=0 .

$ btrfs balance start -v .

$ cd /media/6357625f-c966-49ba-9c90-9e8f8ff50433

$ btrfs balance start -v -dusage=0 .

$ btrfs balance start -v .

整个过程非常耗时间，可以通过新开一个SHELL中执行如下命令来查看进度信息

$ cd /media/6357625f-c966-49ba-9c90-9e8f8ff50433

$ btrfs balance status .

$ cd /media/6357625f-c966-49ba-9c90-9e8f8ff50433

$ btrfs balance status .

注意

目前遇到了执行

$ cd /media/6357625f-c966-49ba-9c90-9e8f8ff50433

$ btrfs balance start -v -dusage=0 .

$ btrfs balance start -v .

$ cd /media/6357625f-c966-49ba-9c90-9e8f8ff50433

$ btrfs balance start -v -dusage=0 .

$ btrfs balance start -v .

之后，整个OpenMediaVault系统无响应的问题，即使强制重新开机，也会在挂载完成刚刚转换后的磁盘后系统继续宕机，这个问题还在查找原因中。

刚刚开始是怀疑btrfs-tools版本太低导致的，系统默认自带的是btrfs-tools 3.17，但是Linux内核确是Linux Kernel 4.9.0，按理说，两者版本号应该是一致的，但是标准源上只更新到了btrfs-tools 4.7.3，使用如下命令更新后，问题依旧

$ sudo apt-get install btrfs-progs

1	$ sudo apt-get install btrfs-progs

通过移除硬盘，重启系统后,查看系统日志

$ cat /var/log/syslog

1	$ cat /var/log/syslog

看到如下内容:

Aug 21 23:08:45 openmediavault kernel: [   11.572669] CPU: 1 PID: 501 Comm: mount Not tainted 4.9.0-0.bpo.3-amd64 #1 Debian 4.9.30-2+deb9u2~bpo8+1
Aug 21 23:08:45 openmediavault kernel: [   11.572805] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Q1900-ITX, BIOS C1.80 12/17/2015
Aug 21 23:08:45 openmediavault kernel: [   11.572944] task: ffff8fc0799a6dc0 task.stack: ffffa84ec0ae4000
Aug 21 23:08:45 openmediavault kernel: [   11.573033] RIP: 0010:[<ffffffffc0344fcb>]  [<ffffffffc0344fcb>] qgroup_fix_relocated_data_extents+0x2b/0x2c0 [btrfs]
Aug 21 23:08:45 openmediavault kernel: [   11.573234] RSP: 0018:ffffa84ec0ae79f0  EFLAGS: 00010246
Aug 21 23:08:45 openmediavault kernel: [   11.573315] RAX: ffff8fc0741b6800 RBX: ffff8fc077d26770 RCX: 000000000000128b
Aug 21 23:08:45 openmediavault kernel: [   11.573421] RDX: ffff8fc079343810 RSI: ffff8fc074741800 RDI: ffff8fc079343780
Aug 21 23:08:45 openmediavault kernel: [   11.573527] RBP: ffff8fc074ec2800 R08: ffff8fc07405c000 R09: ffff8fc079343780
Aug 21 23:08:45 openmediavault kernel: [   11.573633] R10: 0000000000000000 R11: 0000000000000000 R12: ffffa84ec0ae7a88
Aug 21 23:08:45 openmediavault kernel: [   11.573740] R13: ffff8fc074741800 R14: 0000000000000000 R15: ffff8fc079343780
Aug 21 23:08:45 openmediavault kernel: [   11.573847] FS:  00007f8570bbe840(0000) GS:ffff8fc07fc80000(0000) knlGS:0000000000000000
Aug 21 23:08:45 openmediavault kernel: [   11.573967] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Aug 21 23:08:45 openmediavault kernel: [   11.574054] CR2: fffffffffffffe10 CR3: 00000001367e6000 CR4: 00000000001006e0
Aug 21 23:08:45 openmediavault kernel: [   11.574160] Stack:
Aug 21 23:08:45 openmediavault kernel: [   11.574196]  ffffffffc02ed592 ffff8fc079343780 0000000000000801 ffff8fc0741b6800
Aug 21 23:08:45 openmediavault kernel: [   11.574335]  ffff8fc079343780 0000000000000801 ffffffffc02efffd ffff8fc0799a6dc0
Aug 21 23:08:45 openmediavault kernel: [   11.574478]  0000000000000000 a11cd9e1ac42d412 ffff8fc077d26770 ffff8fc074ec2800
Aug 21 23:08:45 openmediavault kernel: [   11.574616] Call Trace:
Aug 21 23:08:45 openmediavault kernel: [   11.579190]  [<ffffffffc02ed592>] ? join_transaction.isra.14+0x22/0x3f0 [btrfs]
Aug 21 23:08:45 openmediavault kernel: [   11.583819]  [<ffffffffc02efffd>] ? start_transaction+0x9d/0x4a0 [btrfs]
Aug 21 23:08:45 openmediavault kernel: [   11.588451]  [<ffffffffc0349638>] ? btrfs_recover_relocation+0x2e8/0x420 [btrfs]
Aug 21 23:08:45 openmediavault kernel: [   11.593105]  [<ffffffffc02ec94d>] ? open_ctree+0x223d/0x2760 [btrfs]
Aug 21 23:08:45 openmediavault kernel: [   11.597702]  [<ffffffff8ed35c49>] ? snprintf+0x49/0x60
Aug 21 23:08:45 openmediavault kernel: [   11.602250]  [<ffffffffc02bfe1d>] ? btrfs_mount+0xd3d/0xe80 [btrfs]
Aug 21 23:08:45 openmediavault kernel: [   11.606742]  [<ffffffff8eba538d>] ? pcpu_alloc+0x34d/0x650
Aug 21 23:08:45 openmediavault kernel: [   11.611187]  [<ffffffff8ec077a6>] ? mount_fs+0x36/0x170
Aug 21 23:08:45 openmediavault kernel: [   11.615562]  [<ffffffff8ec247c4>] ? vfs_kern_mount+0x64/0x100
Aug 21 23:08:45 openmediavault kernel: [   11.619940]  [<ffffffffc02bf29c>] ? btrfs_mount+0x1bc/0xe80 [btrfs]
Aug 21 23:08:45 openmediavault kernel: [   11.624250]  [<ffffffff8eba538d>] ? pcpu_alloc+0x34d/0x650
Aug 21 23:08:45 openmediavault kernel: [   11.628596]  [<ffffffff8ec077a6>] ? mount_fs+0x36/0x170
Aug 21 23:08:45 openmediavault kernel: [   11.632988]  [<ffffffff8ec247c4>] ? vfs_kern_mount+0x64/0x100
Aug 21 23:08:45 openmediavault kernel: [   11.637301]  [<ffffffff8ec26dad>] ? do_mount+0x1dd/0xc70
Aug 21 23:08:45 openmediavault kernel: [   11.641568]  [<ffffffff8ec27b24>] ? SyS_mount+0x84/0xc0
Aug 21 23:08:45 openmediavault kernel: [   11.645762]  [<ffffffff8f0077bb>] ? system_call_fast_compare_end+0xc/0x9b
Aug 21 23:08:45 openmediavault kernel: [   11.649937] Code: 0f 1f 44 00 00 41 57 41 56 41 55 41 54 55 53 48 83 ec 50 4c 8b 76 10 65 48 8b 04 25 28 00 00 00 48 89 44 24 48 31 c0 48 8b 46 08 <49> 8b ae 10 fe ff ff 48 8b 98 f0 01 00 00 31 c0 48 8b 53 20 83 
Aug 21 23:08:45 openmediavault kernel: [   11.659055] RIP  [<ffffffffc0344fcb>] qgroup_fix_relocated_data_extents+0x2b/0x2c0 [btrfs]
Aug 21 23:08:45 openmediavault kernel: [   11.663502]  RSP <ffffa84ec0ae79f0>
Aug 21 23:08:45 openmediavault kernel: [   11.667815] CR2: fffffffffffffe10
Aug 21 23:08:45 openmediavault kernel: [   11.671992] ---[ end trace 5342438d9209c318 ]---
Aug 21 23:08:45 openmediavault systemd[1]: media-6357625f\x2dc966\x2d49ba\x2d9c90\x2d9e8f8ff50433.mount mount process exited, code=killed status=9

Aug 21 23:08:45 openmediavault kernel: [ 11.572669] CPU: 1 PID: 501 Comm: mount Not tainted 4.9.0-0.bpo.3-amd64 #1 Debian 4.9.30-2+deb9u2~bpo8+1

Aug 21 23:08:45 openmediavault kernel: [ 11.572805] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Q1900-ITX, BIOS C1.80 12/17/2015

Aug 21 23:08:45 openmediavault kernel: [ 11.572944] task: ffff8fc0799a6dc0 task.stack: ffffa84ec0ae4000

Aug 21 23:08:45 openmediavault kernel: [ 11.573033] RIP: 0010:[<ffffffffc0344fcb>] [<ffffffffc0344fcb>] qgroup_fix_relocated_data_extents+0x2b/0x2c0 [btrfs]

Aug 21 23:08:45 openmediavault kernel: [ 11.573234] RSP: 0018:ffffa84ec0ae79f0 EFLAGS: 00010246

Aug 21 23:08:45 openmediavault kernel: [ 11.573315] RAX: ffff8fc0741b6800 RBX: ffff8fc077d26770 RCX: 000000000000128b

Aug 21 23:08:45 openmediavault kernel: [ 11.573421] RDX: ffff8fc079343810 RSI: ffff8fc074741800 RDI: ffff8fc079343780

Aug 21 23:08:45 openmediavault kernel: [ 11.573527] RBP: ffff8fc074ec2800 R08: ffff8fc07405c000 R09: ffff8fc079343780

Aug 21 23:08:45 openmediavault kernel: [ 11.573633] R10: 0000000000000000 R11: 0000000000000000 R12: ffffa84ec0ae7a88

Aug 21 23:08:45 openmediavault kernel: [ 11.573740] R13: ffff8fc074741800 R14: 0000000000000000 R15: ffff8fc079343780

Aug 21 23:08:45 openmediavault kernel: [ 11.573847] FS: 00007f8570bbe840(0000) GS:ffff8fc07fc80000(0000) knlGS:0000000000000000

Aug 21 23:08:45 openmediavault kernel: [ 11.573967] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

Aug 21 23:08:45 openmediavault kernel: [ 11.574054] CR2: fffffffffffffe10 CR3: 00000001367e6000 CR4: 00000000001006e0

Aug 21 23:08:45 openmediavault kernel: [ 11.574160] Stack:

Aug 21 23:08:45 openmediavault kernel: [ 11.574196] ffffffffc02ed592 ffff8fc079343780 0000000000000801 ffff8fc0741b6800

Aug 21 23:08:45 openmediavault kernel: [ 11.574335] ffff8fc079343780 0000000000000801 ffffffffc02efffd ffff8fc0799a6dc0

Aug 21 23:08:45 openmediavault kernel: [ 11.574478] 0000000000000000 a11cd9e1ac42d412 ffff8fc077d26770 ffff8fc074ec2800

Aug 21 23:08:45 openmediavault kernel: [ 11.574616] Call Trace:

Aug 21 23:08:45 openmediavault kernel: [ 11.579190] [<ffffffffc02ed592>] ? join_transaction.isra.14+0x22/0x3f0 [btrfs]

Aug 21 23:08:45 openmediavault kernel: [ 11.583819] [<ffffffffc02efffd>] ? start_transaction+0x9d/0x4a0 [btrfs]

Aug 21 23:08:45 openmediavault kernel: [ 11.588451] [<ffffffffc0349638>] ? btrfs_recover_relocation+0x2e8/0x420 [btrfs]

Aug 21 23:08:45 openmediavault kernel: [ 11.593105] [<ffffffffc02ec94d>] ? open_ctree+0x223d/0x2760 [btrfs]

Aug 21 23:08:45 openmediavault kernel: [ 11.597702] [<ffffffff8ed35c49>] ? snprintf+0x49/0x60

Aug 21 23:08:45 openmediavault kernel: [ 11.602250] [<ffffffffc02bfe1d>] ? btrfs_mount+0xd3d/0xe80 [btrfs]

Aug 21 23:08:45 openmediavault kernel: [ 11.606742] [<ffffffff8eba538d>] ? pcpu_alloc+0x34d/0x650

Aug 21 23:08:45 openmediavault kernel: [ 11.611187] [<ffffffff8ec077a6>] ? mount_fs+0x36/0x170

Aug 21 23:08:45 openmediavault kernel: [ 11.615562] [<ffffffff8ec247c4>] ? vfs_kern_mount+0x64/0x100

Aug 21 23:08:45 openmediavault kernel: [ 11.619940] [<ffffffffc02bf29c>] ? btrfs_mount+0x1bc/0xe80 [btrfs]

Aug 21 23:08:45 openmediavault kernel: [ 11.624250] [<ffffffff8eba538d>] ? pcpu_alloc+0x34d/0x650

Aug 21 23:08:45 openmediavault kernel: [ 11.628596] [<ffffffff8ec077a6>] ? mount_fs+0x36/0x170

Aug 21 23:08:45 openmediavault kernel: [ 11.632988] [<ffffffff8ec247c4>] ? vfs_kern_mount+0x64/0x100

Aug 21 23:08:45 openmediavault kernel: [ 11.637301] [<ffffffff8ec26dad>] ? do_mount+0x1dd/0xc70

Aug 21 23:08:45 openmediavault kernel: [ 11.641568] [<ffffffff8ec27b24>] ? SyS_mount+0x84/0xc0

Aug 21 23:08:45 openmediavault kernel: [ 11.645762] [<ffffffff8f0077bb>] ? system_call_fast_compare_end+0xc/0x9b

Aug 21 23:08:45 openmediavault kernel: [ 11.649937] Code: 0f 1f 44 00 00 41 57 41 56 41 55 41 54 55 53 48 83 ec 50 4c 8b 76 10 65 48 8b 04 25 28 00 00 00 48 89 44 24 48 31 c0 48 8b 46 08 <49> 8b ae 10 fe ff ff 48 8b 98 f0 01 00 00 31 c0 48 8b 53 20 83

Aug 21 23:08:45 openmediavault kernel: [ 11.659055] RIP [<ffffffffc0344fcb>] qgroup_fix_relocated_data_extents+0x2b/0x2c0 [btrfs]

Aug 21 23:08:45 openmediavault kernel: [ 11.663502] RSP <ffffa84ec0ae79f0>

Aug 21 23:08:45 openmediavault kernel: [ 11.667815] CR2: fffffffffffffe10

Aug 21 23:08:45 openmediavault kernel: [ 11.671992] ---[ end trace 5342438d9209c318 ]---

Aug 21 23:08:45 openmediavault systemd[1]: media-6357625f\x2dc966\x2d49ba\x2d9c90\x2d9e8f8ff50433.mount mount process exited, code=killed status=9

根据Re: mount troubles after crash里面的回复，这个是Linux Kernel 4.9.0已知的BUG,在Linux Kernel 4.10-rcs之后的版本被修复。因此涉及到了Linux Kernel的升级操作。

目前看来要么自己编译内核，要么等待Debian Jessie的back-backports更新Linux内核了，希望整个修复已经合并到Linux Kernel 4.9.44版本中了吧。

或者关闭btrfs的磁盘配额(btrfs-quota）功能(崩溃的原因就是磁盘配额部分的BUG),也可以解决这个问题。

$ sudo btrfs quota disable /media/`whoami`/6357625f-c966-49ba-9c90-9e8f8ff50433

1	$ sudo btrfs quota disable /media/`whoami`/6357625f-c966-49ba-9c90-9e8f8ff50433

注意，上面的命令是在Ubuntu 16.04 Linux Kernel 4.4.0-92系统上执行的（硬盘被单独拿出来，然后挂载到Ubuntu 16.04 Linux Kernel 4.4.0-92的机器上），貌似由于这个版本的内核不支持btrfs的磁盘配额。因此，没有这个问题。

目前测试来看，上面的办法（关闭磁盘配额）并不能解决问题，看来只有升级到Linux Kernel 4.10，或者把补丁重新应用到Linux Kernel 4.9这一条路了。

手工升级到 Linux Kernel 4.13.0-rc5-amd64,则执行如下操作：

$ sudo cp /etc/apt/preferences.d/openmediavault-kernel-backports.pref /etc/apt/preferences.d/openmediavault-kernel-backports.pref.bak

$ sudo vi /etc/apt/preferences.d/openmediavault-kernel-backports.pref

$ sudo cp /etc/apt/preferences.d/openmediavault-kernel-backports.pref /etc/apt/preferences.d/openmediavault-kernel-backports.pref.bak

$ sudo vi /etc/apt/preferences.d/openmediavault-kernel-backports.pref

把里面的如下内容

Package: linux-base
Pin: release a=jessie-backports
Pin-Priority: 500

Package: linux-headers-*
Pin: release a=jessie-backports
Pin-Priority: 500

Package: linux-image-*
Pin: release a=jessie-backports
Pin-Priority: 500

Package: linux-base

Pin: release a=jessie-backports

Pin-Priority: 500

Package: linux-headers-*

Pin: release a=jessie-backports

Pin-Priority: 500

Package: linux-image-*

Pin: release a=jessie-backports

Pin-Priority: 500

替换为：

Package: linux-base
Pin: release o=Debian,a=experimental
Pin-Priority: 102

Package: linux-headers-*
Pin: release o=Debian,a=experimental
Pin-Priority: 102

Package: linux-image-*
Pin: release o=Debian,a=experimental
Pin-Priority: 102

Package: linux-base

Pin: release o=Debian,a=experimental

Pin-Priority: 102

Package: linux-headers-*

Pin: release o=Debian,a=experimental

Pin-Priority: 102

Package: linux-image-*

Pin: release o=Debian,a=experimental

Pin-Priority: 102

然后执行如下命令

#国内用户建议使用这个地址 deb http://mirrors.163.com/debian/ experimental main

$ sudo echo "deb http://deb.debian.org/debian experimental main" >> /etc/apt/sources.list

$ sudo apt-get update

$ sudo apt-get -t experimental install search linux-image-4.1

#目前最新的就是 linux-image-4.13.0-rc5-amd64 
$ sudo apt-get -t experimental install linux-image-4.13.0-rc5-amd64 

#使用完成后，建议移除我们刚刚的修改，这样可以避免误安装其他东西，导致系统异常。
$ sudo rm -rf  /etc/apt/preferences.d/openmediavault-kernel-backports.pref 
$ sudo mv  /etc/apt/preferences.d/openmediavault-kernel-backports.pref.bak  /etc/apt/preferences.d/openmediavault-kernel-backports.pref 
$ sudo sed -i '/deb\ http:\/\/deb.debian.org\/debian\ experimental\ main/d' /etc/apt/sources.list

$ sudo reboot

#国内用户建议使用这个地址 deb http://mirrors.163.com/debian/ experimental main

$ sudo echo "deb http://deb.debian.org/debian experimental main" >> /etc/apt/sources.list

$ sudo apt-get update

$ sudo apt-get -t experimental install search linux-image-4.1

#目前最新的就是 linux-image-4.13.0-rc5-amd64

$ sudo apt-get -t experimental install linux-image-4.13.0-rc5-amd64

#使用完成后，建议移除我们刚刚的修改，这样可以避免误安装其他东西，导致系统异常。

$ sudo rm -rf /etc/apt/preferences.d/openmediavault-kernel-backports.pref

$ sudo mv /etc/apt/preferences.d/openmediavault-kernel-backports.pref.bak /etc/apt/preferences.d/openmediavault-kernel-backports.pref

$ sudo sed -i '/deb\ http:\/\/deb.debian.org\/debian\ experimental\ main/d' /etc/apt/sources.list

$ sudo reboot

注意，这个源，可以替换成Debian 9的backport的源，貌似可以安装 linux-image-4.12版本的内核，内核部分不必追求最新，一般追求最稳定，能解决问题即可。

貌似linux-image-4.13.0-RC5版本内核依旧存在BUG，如下所示:

Aug 23 22:20:13 openmediavault kernel: [  153.478300] kernel BUG at /build/linux-yioSfB/linux-4.13~rc5/fs/btrfs/relocation.c:4667!
Aug 23 22:20:13 openmediavault kernel: [  153.478481] invalid opcode: 0000 [#1] SMP
Aug 23 22:20:13 openmediavault kernel: [  153.478553] Modules linked in: cpufreq_conservative cpufreq_powersave cpufreq_userspace nfsd auth_rpcgss nfs_acl nfs lockd grace fscache sunrpc quota_v2 quota_tree snd_hda_codec_hdmi snd_hda_codec_realtek hci_uart snd_hda_codec_generic snd_soc_rt5670 snd_soc_rt5645 btbcm snd_soc_rt5640 btqca snd_soc_rl6231 snd_intel_sst_acpi btintel snd_intel_sst_core bluetooth snd_soc_sst_atom_hifi2_platform snd_soc_sst_match drbg snd_soc_core iTCO_wdt ppdev iTCO_vendor_support ansi_cprng parport_pc parport i915 ecdh_generic snd_compress evdev snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm drm_kms_helper dw_dmac snd_timer battery drm snd video i2c_algo_bit dw_dmac_core shpchp lpc_ich rfkill soundcore mfd_core intel_rapl intel_soc_dts_thermal intel_soc_dts_iosf intel_powerclamp coretemp kvm_intel kvm
Aug 23 22:20:13 openmediavault kernel: [  153.479699]  irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel cryptd intel_cstate pcspkr button loop fuse autofs4 ext4 crc16 mbcache jbd2 fscrypto btrfs xor raid6_pq dm_mod md_mod sg sd_mod hid_generic usbhid ata_generic crc32c_intel i2c_i801 ahci r8169 mii libahci ata_piix xhci_pci libata xhci_hcd usbcore scsi_mod usb_common fan thermal i2c_hid hid sdhci_acpi sdhci i2c_designware_platform i2c_designware_core mmc_core
Aug 23 22:20:13 openmediavault kernel: [  153.480340] CPU: 0 PID: 112 Comm: kworker/u8:3 Tainted: G        W       4.13.0-rc5-amd64 #1 Debian 4.13~rc5-1~exp1
Aug 23 22:20:13 openmediavault kernel: [  153.480504] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Q1900-ITX, BIOS C2.10 11/30/2016
Aug 23 22:20:13 openmediavault kernel: [  153.480710] Workqueue: btrfs-endio-write btrfs_endio_write_helper [btrfs]
Aug 23 22:20:13 openmediavault kernel: [  153.480822] task: ffff8b09b5308380 task.stack: ffff993500afc000
Aug 23 22:20:13 openmediavault kernel: [  153.480965] RIP: 0010:btrfs_reloc_cow_block+0x1f8/0x370 [btrfs]
Aug 23 22:20:13 openmediavault kernel: [  153.481062] RSP: 0018:ffff993500aff9e0 EFLAGS: 00010246
Aug 23 22:20:13 openmediavault kernel: [  153.481150] RAX: ffff8b09b9d8c000 RBX: ffff8b09b6f19800 RCX: ffff8b08b62e05b8
Aug 23 22:20:13 openmediavault kernel: [  153.481265] RDX: ffff8b09b60c87a8 RSI: ffff8b09b6f19800 RDI: ffff8b09b8a33e88
Aug 23 22:20:13 openmediavault kernel: [  153.481379] RBP: ffff8b09b7efb000 R08: ffff993500affa70 R09: 0000000000001000
Aug 23 22:20:13 openmediavault kernel: [  153.481494] R10: fffffffffffffff7 R11: ffff8b09b8e94358 R12: ffff8b09b8a33e88
Aug 23 22:20:13 openmediavault kernel: [  153.481608] R13: 0000000000000000 R14: ffff8b08b62e05b8 R15: ffff8b09b9d8c000
Aug 23 22:20:13 openmediavault kernel: [  153.481724] FS:  0000000000000000(0000) GS:ffff8b09bfc00000(0000) knlGS:0000000000000000
Aug 23 22:20:13 openmediavault kernel: [  153.481854] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Aug 23 22:20:13 openmediavault kernel: [  153.481948] CR2: 00007f9964755000 CR3: 0000000129809000 CR4: 00000000001006f0
Aug 23 22:20:13 openmediavault kernel: [  153.482063] Call Trace:
Aug 23 22:20:13 openmediavault kernel: [  153.482150]  ? update_ref_for_cow+0x254/0x350 [btrfs]
Aug 23 22:20:13 openmediavault kernel: [  153.482274]  ? __btrfs_cow_block+0x35d/0x5c0 [btrfs]
Aug 23 22:20:13 openmediavault kernel: [  153.482395]  ? btrfs_cow_block+0xcb/0x1b0 [btrfs]
Aug 23 22:20:13 openmediavault kernel: [  153.487038]  ? btrfs_search_slot+0x1fd/0x9e0 [btrfs]
Aug 23 22:20:13 openmediavault kernel: [  153.491662]  ? btrfs_lookup_file_extent+0x4a/0x70 [btrfs]
Aug 23 22:20:13 openmediavault kernel: [  153.496270]  ? __btrfs_drop_extents+0x156/0xe10 [btrfs]
Aug 23 22:20:13 openmediavault kernel: [  153.500816]  ? kmem_cache_alloc+0xbb/0x5a0
Aug 23 22:20:13 openmediavault kernel: [  153.505321]  ? __schedule+0x3d0/0x860
Aug 23 22:20:13 openmediavault kernel: [  153.509822]  ? insert_reserved_file_extent.constprop.65+0x97/0x2f0 [btrfs]
Aug 23 22:20:13 openmediavault kernel: [  153.514424]  ? btrfs_finish_ordered_io+0x33b/0x790 [btrfs]
Aug 23 22:20:13 openmediavault kernel: [  153.519029]  ? dequeue_task_fair+0x58/0x640
Aug 23 22:20:13 openmediavault kernel: [  153.523595]  ? __switch_to+0x234/0x430
Aug 23 22:20:13 openmediavault kernel: [  153.528159]  ? btrfs_scrubparity_helper+0xcf/0x300 [btrfs]
Aug 23 22:20:13 openmediavault kernel: [  153.532691]  ? __schedule+0x3d0/0x860
Aug 23 22:20:13 openmediavault kernel: [  153.537179]  ? process_one_work+0x181/0x370
Aug 23 22:20:13 openmediavault kernel: [  153.541641]  ? worker_thread+0x4d/0x3a0
Aug 23 22:20:13 openmediavault kernel: [  153.546128]  ? kthread+0xfc/0x130
Aug 23 22:20:13 openmediavault kernel: [  153.550568]  ? process_one_work+0x370/0x370
Aug 23 22:20:13 openmediavault kernel: [  153.554980]  ? kthread_create_on_node+0x70/0x70
Aug 23 22:20:13 openmediavault kernel: [  153.559390]  ? ret_from_fork+0x25/0x30
Aug 23 22:20:13 openmediavault kernel: [  153.563694] Code: 5e 41 5f e9 8b ad ff ff f6 85 b1 05 00 00 01 0f 84 ab fe ff ff c7 04 24 01 00 00 00 e9 d8 fe ff ff 49 83 fa f7 0f 85 42 fe ff ff <0f> 0b 41 0f b6 cf 4d 8d 7a 30 4c 89 44 24 20 48 89 c8 48 89 4c 
Aug 23 22:20:13 openmediavault kernel: [  153.572587] RIP: btrfs_reloc_cow_block+0x1f8/0x370 [btrfs] RSP: ffff993500aff9e0
Aug 23 22:20:13 openmediavault kernel: [  153.576943] ---[ end trace bc1f498ba941cbb6 ]---

Aug 23 22:20:13 openmediavault kernel: [ 153.478300] kernel BUG at /build/linux-yioSfB/linux-4.13~rc5/fs/btrfs/relocation.c:4667!

Aug 23 22:20:13 openmediavault kernel: [ 153.478481] invalid opcode: 0000 [#1] SMP

Aug 23 22:20:13 openmediavault kernel: [ 153.478553] Modules linked in: cpufreq_conservative cpufreq_powersave cpufreq_userspace nfsd auth_rpcgss nfs_acl nfs lockd grace fscache sunrpc quota_v2 quota_tree snd_hda_codec_hdmi snd_hda_codec_realtek hci_uart snd_hda_codec_generic snd_soc_rt5670 snd_soc_rt5645 btbcm snd_soc_rt5640 btqca snd_soc_rl6231 snd_intel_sst_acpi btintel snd_intel_sst_core bluetooth snd_soc_sst_atom_hifi2_platform snd_soc_sst_match drbg snd_soc_core iTCO_wdt ppdev iTCO_vendor_support ansi_cprng parport_pc parport i915 ecdh_generic snd_compress evdev snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm drm_kms_helper dw_dmac snd_timer battery drm snd video i2c_algo_bit dw_dmac_core shpchp lpc_ich rfkill soundcore mfd_core intel_rapl intel_soc_dts_thermal intel_soc_dts_iosf intel_powerclamp coretemp kvm_intel kvm

Aug 23 22:20:13 openmediavault kernel: [ 153.479699] irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel cryptd intel_cstate pcspkr button loop fuse autofs4 ext4 crc16 mbcache jbd2 fscrypto btrfs xor raid6_pq dm_mod md_mod sg sd_mod hid_generic usbhid ata_generic crc32c_intel i2c_i801 ahci r8169 mii libahci ata_piix xhci_pci libata xhci_hcd usbcore scsi_mod usb_common fan thermal i2c_hid hid sdhci_acpi sdhci i2c_designware_platform i2c_designware_core mmc_core

Aug 23 22:20:13 openmediavault kernel: [ 153.480340] CPU: 0 PID: 112 Comm: kworker/u8:3 Tainted: G W 4.13.0-rc5-amd64 #1 Debian 4.13~rc5-1~exp1

Aug 23 22:20:13 openmediavault kernel: [ 153.480504] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Q1900-ITX, BIOS C2.10 11/30/2016

Aug 23 22:20:13 openmediavault kernel: [ 153.480710] Workqueue: btrfs-endio-write btrfs_endio_write_helper [btrfs]

Aug 23 22:20:13 openmediavault kernel: [ 153.480822] task: ffff8b09b5308380 task.stack: ffff993500afc000

Aug 23 22:20:13 openmediavault kernel: [ 153.480965] RIP: 0010:btrfs_reloc_cow_block+0x1f8/0x370 [btrfs]

Aug 23 22:20:13 openmediavault kernel: [ 153.481062] RSP: 0018:ffff993500aff9e0 EFLAGS: 00010246

Aug 23 22:20:13 openmediavault kernel: [ 153.481150] RAX: ffff8b09b9d8c000 RBX: ffff8b09b6f19800 RCX: ffff8b08b62e05b8

Aug 23 22:20:13 openmediavault kernel: [ 153.481265] RDX: ffff8b09b60c87a8 RSI: ffff8b09b6f19800 RDI: ffff8b09b8a33e88

Aug 23 22:20:13 openmediavault kernel: [ 153.481379] RBP: ffff8b09b7efb000 R08: ffff993500affa70 R09: 0000000000001000

Aug 23 22:20:13 openmediavault kernel: [ 153.481494] R10: fffffffffffffff7 R11: ffff8b09b8e94358 R12: ffff8b09b8a33e88

Aug 23 22:20:13 openmediavault kernel: [ 153.481608] R13: 0000000000000000 R14: ffff8b08b62e05b8 R15: ffff8b09b9d8c000

Aug 23 22:20:13 openmediavault kernel: [ 153.481724] FS: 0000000000000000(0000) GS:ffff8b09bfc00000(0000) knlGS:0000000000000000

Aug 23 22:20:13 openmediavault kernel: [ 153.481854] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

Aug 23 22:20:13 openmediavault kernel: [ 153.481948] CR2: 00007f9964755000 CR3: 0000000129809000 CR4: 00000000001006f0

Aug 23 22:20:13 openmediavault kernel: [ 153.482063] Call Trace:

Aug 23 22:20:13 openmediavault kernel: [ 153.482150] ? update_ref_for_cow+0x254/0x350 [btrfs]

Aug 23 22:20:13 openmediavault kernel: [ 153.482274] ? __btrfs_cow_block+0x35d/0x5c0 [btrfs]

Aug 23 22:20:13 openmediavault kernel: [ 153.482395] ? btrfs_cow_block+0xcb/0x1b0 [btrfs]

Aug 23 22:20:13 openmediavault kernel: [ 153.487038] ? btrfs_search_slot+0x1fd/0x9e0 [btrfs]

Aug 23 22:20:13 openmediavault kernel: [ 153.491662] ? btrfs_lookup_file_extent+0x4a/0x70 [btrfs]

Aug 23 22:20:13 openmediavault kernel: [ 153.496270] ? __btrfs_drop_extents+0x156/0xe10 [btrfs]

Aug 23 22:20:13 openmediavault kernel: [ 153.500816] ? kmem_cache_alloc+0xbb/0x5a0

Aug 23 22:20:13 openmediavault kernel: [ 153.505321] ? __schedule+0x3d0/0x860

Aug 23 22:20:13 openmediavault kernel: [ 153.509822] ? insert_reserved_file_extent.constprop.65+0x97/0x2f0 [btrfs]

Aug 23 22:20:13 openmediavault kernel: [ 153.514424] ? btrfs_finish_ordered_io+0x33b/0x790 [btrfs]

Aug 23 22:20:13 openmediavault kernel: [ 153.519029] ? dequeue_task_fair+0x58/0x640

Aug 23 22:20:13 openmediavault kernel: [ 153.523595] ? __switch_to+0x234/0x430

Aug 23 22:20:13 openmediavault kernel: [ 153.528159] ? btrfs_scrubparity_helper+0xcf/0x300 [btrfs]

Aug 23 22:20:13 openmediavault kernel: [ 153.532691] ? __schedule+0x3d0/0x860

Aug 23 22:20:13 openmediavault kernel: [ 153.537179] ? process_one_work+0x181/0x370

Aug 23 22:20:13 openmediavault kernel: [ 153.541641] ? worker_thread+0x4d/0x3a0

Aug 23 22:20:13 openmediavault kernel: [ 153.546128] ? kthread+0xfc/0x130

Aug 23 22:20:13 openmediavault kernel: [ 153.550568] ? process_one_work+0x370/0x370

Aug 23 22:20:13 openmediavault kernel: [ 153.554980] ? kthread_create_on_node+0x70/0x70

Aug 23 22:20:13 openmediavault kernel: [ 153.559390] ? ret_from_fork+0x25/0x30

Aug 23 22:20:13 openmediavault kernel: [ 153.563694] Code: 5e 41 5f e9 8b ad ff ff f6 85 b1 05 00 00 01 0f 84 ab fe ff ff c7 04 24 01 00 00 00 e9 d8 fe ff ff 49 83 fa f7 0f 85 42 fe ff ff <0f> 0b 41 0f b6 cf 4d 8d 7a 30 4c 89 44 24 20 48 89 c8 48 89 4c

Aug 23 22:20:13 openmediavault kernel: [ 153.572587] RIP: btrfs_reloc_cow_block+0x1f8/0x370 [btrfs] RSP: ffff993500aff9e0

Aug 23 22:20:13 openmediavault kernel: [ 153.576943] ---[ end trace bc1f498ba941cbb6 ]---

执行如下命令，修复一下文件系统：

$ sudo umount /dev/sda1

# sudo btrfsck --repair --init-csum-tree --init-extent-tree /dev/sda1 太慢了，如果没有严重问题，只执行修复即可
$ sudo btrfsck --repair /dev/sda1

$ sudo umount /dev/sda1

# sudo btrfsck --repair --init-csum-tree --init-extent-tree /dev/sda1 太慢了，如果没有严重问题，只执行修复即可

$ sudo btrfsck --repair /dev/sda1

貌似不管用，估计还要继续升级内核，btrfs还是不够成熟啊！

参考OpenMdeiaValut 3.0.86上编译Linux Kernel 4.13-rc6编译安装最新的内核，貌似可以解决上面的问题。

参考链接

机器人程序设计之如何正确入门ROS

当前大家学习ROS还是以自学为主，所以会走很多的弯路，目前所谓的大神们也都是这样过来的。基本上早期开发机器人大家都是各干各的，甚至是防着彼此，生怕别人把我们的代码、设计抄袭过去，这样其实大家就是在重复地造轮子，进行一些底层的无聊工作。

继续阅读机器人程序设计之如何正确入门ROS

ROS开发环境RoboWare Studio

RoboWare Studio是ROS的一款IDE，基于微软开源的VSCode开发，功能比较强大，使得开发更加快速、简单。是目前最好用的ROS开发工具了。

继续阅读ROS开发环境RoboWare Studio

2025 年 11 月
一	二	三	四	五	六	日
					1	2
3	4	5	6	7	8	9
10	11	12	13	14	15	16
17	18	19	20	21	22	23
24	25	26	27	28	29	30

1.从GitHub上获取项目代码

2.安装ROS

3.安装OpenPTrack

4.链接OpenPTrack目录

5.Kinect V2驱动程序安装

7.测试系统

参考链接

参考连接

参考链接

参考连接

参考链接

参考链接

注意

参考链接

3.安装`OpenPTrack`

4.链接`OpenPTrack`目录

5.`Kinect V2`驱动程序安装