From: Jorge G. <jor...@wh...> - 2012-09-11 16:41:37
|
Hi everybody, We are facing a tricky problem which involves fuse volumes, zfs and nfs. We are using linux (debian) and kernel 3.0.8, also latests versions of fuse library and zfs-fuse. We have zfs file systems (working over zfs-fuse library) and we need to share them over nfs. In most cases it works fine. But when shared volume gets stressed, we start getting "stale file handlers" problems on clients. We have tried sharing the volume with exports, also with 'zfs set sharenfs=on', putting same fsid on server and client, setting a lot of combinations of mount options on client (defaults,timeo=20,retrans=5,rsize=8192,wsize=8192,intr ...). But, although the problem reduces itself with some configurations, ends failing always. To reproduce the error, here is a simple scenario: /Server / zfs set sharenfs=on pool1/vol1 /Client / mount x.x.x.x:/mnt/pool1/vol1 testNFS Execute the little script I post at the end of this mail at the nfs volume mountpoint on server. Wait for the end of directory creation process. A few seconds after, try to do several "ls -l" at client and you should get the stales file handler errors: #!/bin/bash BASE_DIR= if [ ! -z $1 ]; then BASE_DIR=$1 fi for D in $(seq 1 1 100); do if [ -z $BASE_DIR ]; then DIR="dir$D" else DIR="$BASE_DIR/dir$D" fi if [ ! -d $DIR ]; then echo -n "$DIR-> " mkdir $DIR for F in $(seq 1 1 100); do echo -n "." FILE=$(seq 1 1 100) echo $FILE > $DIR/$F.txt done echo " done" fi done if [ ! -e $BASE_DIR/lista_ficheros.txt ]; then find $BASE_DIR -type f \( ! -iname "backup.cpio" \) > $BASE_DIR/lista_ficheros.txt fi for D in $(seq 1 1 20); do cat $BASE_DIR/lista_ficheros.txt | cpio -o > $BASE_DIR/backup.cpio done Thank you all in advance for any help, Jorge Gea -- WBSGo <http://www.whitebearsolutions.com> *Jorge Gea Martínez* /I+D WBSAirback Developer/ Tlf: (+34) 902906969 Fax: (+34) 902906970 E-mail: jor...@wh... <mailto:jor...@wh...> Web: http://www.wbsgo.com <http://www.whitebearsolutions.com> click here <http://www.wbsgo.com/apps/info-mail/mail-banner-content.html> |