четверг, 19 сентября 2013 г.

NFS server mount same directory

I've got this wierd situation. I had few shares:

#/etc/exports
/data/share/ 192.168.0.1/24(rw,fsid=root,no_subtree_check)
/data/share/share1  192.168.19.0/24(rw,fsid=0,insecure,no_subtree_check,async)
/data/share2  192.168.19.0/24(rw,,fsid=0,insecure,no_subtree_check,async)



and everything was working fine. But, when I'd decided to add new share to /data/share:

#/etc/exports
/data/share/  192.168.0.1/24(rw,fsid=root,no_subtree_check)
/data/share/share1  192.168.19.0/24(rw,fsid=0,insecure,no_subtree_check,async)
/data/share/share2  192.168.19.0/24(rw,fsid=0,insecure,no_subtree_check,async)
/data/share2  192.168.19.0/24(rw,,fsid=0,insecure,no_subtree_check,async)

I found out that I cannot mount /data/share/share2: when I was trying something like:

mount nfsserver:/data/share/share2 /mnt

I always had /data/share/share1 being mounted. 
It turns out, that problem is in fsid parameter. It's not mandatory, and I didn't even realized that I set one up (I'd just cpypasted optins for shares). If you'll wath on the first version of /etc/exports, you can notice, that I have same fsid in two shares, but still everything was working. Nevertheless I've changed fsid to diferent numbers:

#/etc/exports
/data/share/  192.168.0.1/24(rw,fsid=root,no_subtree_check)
/data/share/share1  192.168.19.0/24(rw,fsid=1100,insecure,no_subtree_check,async)
/data/share/share2  192.168.19.0/24(rw,fsid=1200,insecure,no_subtree_check,async)
/data/share2  192.168.19.0/24(rw,,fsid=0,insecure,no_subtree_check,async)

And it solved problem.

Комментариев нет:

Отправить комментарий