Hi,

I'm using an embedded linux with a TX25 starterkit board.

To start, this board proceeds as below :

1. connect to my PC to download the kernel (using a ftp connection).
2. uncompress the kernel and start it.
3. connect to my pc to mount the root file system using nfs.
4. start the system.

Everything works fine, except that I noticed there's maybe a nfs cache issue.

for example, if a program run on the board creates a file in /home, I can see it from my PC (nfs server). => perfect !
But if a program creates a file in /var/lib/dpkg/, I can see it from the board but not from my PC, so when I restart the board everything is lost.

It seems to be a bad configuration.
I tried to restart the nfs and nfslock services.

here is my /etc/eports file.
I tried to use async.

Any ideas ?

thanks
Alex

Could it be an ACL issue? I was dealing with that on a server yesterday where I had the root of the fs limited to the users home directory.

Symbolic linking didn't show up because the link went outside the users home directory. In the end I fixed it by modifying group permissions via the chown command.

Maybe the user you're using to create the file in /var/lib/dpkg/ does not have the access rights on the nfs server to sync it.

I don't think so because the TX25 board mount the nfs directory as its root directory. On my NFS server the directory /tftpboot/rootfs_tx25 is the / directory of the TX25 board.

When a user, on the TX25 board, wants to write a file in /home he writes in /tftpboot/rootfs_tx25/home and when we wants to write to /var/lib/dpkg he write to /tftpboot/rootfs_tx25/var/lib/dpkg.

As I export only /tftpboot/rootfs_tx25 the rights should be the same for /tftpboot/rootfs_tx25/home and /tftpboot/rootfs_tx25/var/lib/dpkg.

And I use the root user on the TX25 board. It seems that all the modifications made is /var/lib/dpkg (/tftpboot/rootfs_tx25//var/lib/dpkg) are made in RAM but never flushed on the server disk.

by using the command df, i realized that /var is mounted as tmpfs...

Check the owner and permissions on the files created in /home...

Then you can check the permissions where it's trying to write to. It still depends how you set up your nfs server and the permissions the server has on parts of the system.

tmpfs doesn't matter only that it is wiped upon restart.

the permissions are exactly the same (drwxrwxr-x) for /tftpboot/rootfs_tx25/var/lib/dpkg and /tftpboot/rootfs_tx25/home.
same user, same group.