NFS Network Mount Problem resolution

In the case of embedded development, NFS is often used to remotely mount a directory on the board, which eliminates the process of copying files and speeding up development. Here, give your own questions about NFS-related settings.

Native IP: 192.168.0.104 Development Board IP: 192.168.0.200, must ensure that they are within the same network segment.

Mount command after starting the system:

I previously used the following:

Mount is successful, read and write shared directory files, both sides can also be synchronized. There seems to be no problem, but when trying to write some slightly more complex drivers, there is a problem. In the case of problems, I start with a simple, hello world, no problem, in the process of gradually increasing the header file, or the same program, but in the execution, will cause the system to panic, it is very strange, the program is only on the original basis, the addition of a few header files, How does it cause the system to die? Oneself tangled for a long time, tried a variety of methods to solve, or can not solve.

In one chance, the suspicion may be a problem on the Mount command, find the following mount method:

Using this method, the difference between the two, I use the red box to give, in this way to mount, some complex drivers can also be performed normally.

This is really a big problem to solve yourself between the unintended. Here's a summary of the principles:

The above is two different versions of NFS mount mode, VER2 can set up to 8K Read and write, V3 not limit the transmission size.

Technorati Tags: NFS

NFS Network Mount Problem resolution