[sroot@alfie:/dock]# cat unix_mount
#!/bin/tcsh -f
mount -t nfs -o ro ${*}:/ /dock/$*/live || exit -1
echo " ${*}:/ mounted on /dock/$*/live/"
foreach a (`cat /dock/$*/live/etc/mtab | \
egrep '^[^ ]+ /[^ ]+ ext2 ' | cut -f2 -d' '`)
mount -t nfs -o ro,rsize=8192,wsize=8192,hard,intr,timeo=6,retrans=9 \
${*}:$a /dock/$*/live$a/ || exit -1
echo " ${*}:$a mounted on /dock/$*/live$a/"
end
:
I was told this is necessary in order to avoid inode hash clashes. I was
having a problem where as soon as it stat()ed or touch a certain remote
file, the mount point would instantly turn into that file. Apparently
mounting each remote filesystem separately after mounting the root avoids
this problem (somehow).
I hit this problem the first time I tried to back up about 40 GB worth of
files from a whole bunch of servers onto a machine with RAID0 drives and
ext2 compression...Since I made it mount each remote filesystem
separately, it hasn't had a problem since (now backing up over 100 GB
worth nightly :)).
Simon-
| Simon Kirby | Systems Administration |
| mailto:sim@netnation.com | NetNation Communications |
| http://www.netnation.com/ | Tech: (604) 684-6892 |
--- On Sun, 21 Feb 1999, Richard B. Johnson wrote:> In the following I show that about 40 minutes into an across-the > network-backup, the remote mount-point becomes inaccessible. > Both machines are running Linux 2.2.1 The server is running a > Red Hat 5.2 release. The client is running software accumulated > over several years (not a vendor release). > > Neither the client, nor the server appear to run out of memory. > There are no entries in the logs of either machines to show the > problem. > > This is 100% repeatable. > > > Script started on Sun Feb 21 15:07:34 1999 > groveland:/root # mount skunkworks:/ /mnt > groveland:/root # cd /mnt > groveland:/mnt # ls > [01;34mbin[0m [01;34mdev[0m [01;34minitrd[0m [01;34mmnt[0m [01;34msbin[0m [01;34mvar[0m > [01;34mboot[0m [01;34metc[0m [01;34mlib[0m [01;34mproc[0m [01;34mtmp[0m > [01;34mcdrom[0m [01;34mhome[0m [01;34mlost+found[0m [01;34mroot[0m [01;34musr[0m > groveland:/mnt # tar --exclude=proc -cf /dev/st0 . > tar: can't add file usr/src/linux-2.2.1/net/econet/Makefile : I/O error > tar: can't add file usr/src/linux-2.2.1/net/econet/econet.c : I/O error > tar: can't add file usr/src/linux-2.2.1/net/econet/.depend : I/O error > tar: can't add file usr/src/linux-2.2.1/net/lapb : I/O error > tar: can't add file usr/src/linux-2.2.1/net/x25 : I/O error > tar: can't add file usr/src/linux-2.2.1/net/rose : I/O error > tar: can't add file usr/src/linux-2.2.1/net/wanrouter : I/O error > tar: can't add file usr/src/linux-2.2.1/net/sunrpc : I/O error > tar: can't add file usr/src/linux-2.2.1/net/netlink : I/O error > tar: can't add file usr/src/linux-2.2.1/net/packet : I/O error > tar: can't add file usr/src/linux-2.2.1/net/sched : I/O error > tar: can't add file usr/src/linux-2.2.1/net/irda : I/O error > tar: can't add file usr/src/linux-2.2.1/net/.depend : I/O error > tar: can't add file usr/src/linux-2.2.1/net/netsyms.o : I/O error > tar: can't add file usr/src/linux-2.2.1/net/.netsyms.o.flags : I/O error > tar: can't add file usr/src/linux-2.2.1/net/socket.o : I/O error > tar: can't add file usr/src/linux-2.2.1/net/.socket.o.flags : I/O error > tar: can't add file usr/src/linux-2.2.1/net/sock_n_syms.o : I/O error > tar: can't add file usr/src/linux-2.2.1/net/.sock_n_syms.o.flags : I/O error > tar: can't add file usr/src/linux-2.2.1/net/protocols.o : I/O error > tar: can't add file usr/src/linux-2.2.1/net/.protocols.o.flags : I/O error > tar: can't add file usr/src/linux-2.2.1/net/sysctl_net.o : I/O error > tar: can't add file usr/src/linux-2.2.1/net/.sysctl_net.o.flags : I/O error > tar: can't add file usr/src/linux-2.2.1/net/network.a : I/O error > tar: can't add file usr/src/linux-2.2.1/net/.network.a.flags : I/O error > tar: can't add file usr/src/linux-2.2.1/COPYING : I/O error > tar: can't add file usr/src/linux-2.2.1/README : I/O error > tar: can't add file usr/src/linux-2.2.1/MAINTAINERS : I/O error > tar: can't add file usr/src/linux-2.2.1/ipc : I/O error > tar: can't add file usr/src/linux-2.2.1/drivers : I/O error > tar: can't add file usr/src/linux-2.2.1/arch : I/O error > tar: can't add file usr/src/linux-2.2.1/scripts : I/O error > tar: can't add file usr/src/linux-2.2.1/Documentation : I/O error > tar: can't add file usr/src/linux-2.2.1/REPORTING-BUGS : I/O error > tar: can't add file usr/src/linux-2.2.1/modules : I/O error > tar: can't add file usr/src/linux-2.2.1/.depend : I/O error > tar: can't add file usr/src/linux-2.2.1/.hdepend : I/O error > tar: can't add file usr/src/linux-2.2.1/.config : I/O error > tar: can't add file usr/src/linux-2.2.1/.config.old : I/O error > tar: can't add file usr/src/linux-2.2.1/World.Log : I/O error > tar: can't add file usr/src/linux-2.2.1/.version : I/O error > tar: can't add file usr/src/linux-2.2.1/vmlinux : I/O error > tar: can't add file usr/src/linux-2.2.1/System.map : I/O error > tar: can't add file usr/src/networking : I/O error > tar: can't add file usr/src/X11R6Clients : I/O error > tar: can't add file usr/tmp : I/O error > tar: can't add file usr/i386-redhat-linux : I/O error > tar: can't add file usr/libexec : I/O error > tar: can't add file usr/i486-linux-libc5 : I/O error > tar: can't add file cdrom : I/O error > tar: can't add file initrd : I/O error > groveland:/mnt # ls > ls: .: I/O error > groveland:/mnt # exit > exit > > Script done on Sun Feb 21 15:44:44 1999 > > > Cheers, > Dick Johnson > ***** FILE SYSTEM WAS MODIFIED ***** > Penguin : Linux version 2.2.1 on an i686 machine (400.59 BogoMips). > Warning : It's hard to remain at the trailing edge of technology. > Wisdom : It's not a Y2K problem. It's a Y2Day problem. > > > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.rutgers.edu > Please read the FAQ at http://www.tux.org/lkml/
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/