|
osdir.com mailing list archive |
|
Subject: unable to mount sfs - msg#00001List: file-systems.sfs.generalI was unable to mount sfs from the client. The Link in /etc/sfs/Hostname just points into deep space. It seems that there are already many postings about this here, but none was solved - and yes, I have NFS v.3 Support in kernel - both server and client. Server is a Linux 2.4.27, client is Linux 2.6.9, and I was unable to find any error in my logs. I'm trying to export home Thats a part of my /etc/exports: /var/lib/sfs/root localhost(rw,sync) /home localhost(rw,sync) Thats my /etc/sfs/sfsrwsd_config: Export /var/lib/sfs/root / Export /home /home The directory /var/lib/sfs/root/home/ does exist. Now when I login /sfs/$Location points to /sfs/@$Location,$HostID and /sfs/@$Location,$HostID points to /sfs/.mnt/1/00000000000000000000000000000037 now while /sfs/.mnt/1/ doest exist, /sfs/.mnt/1/00000000000000000000000000000037 does not. Any Ideas that can help me so far? greetings, Erik Andresen Thread at a glance:
Previous Message by Date: click to view message previewCannot create a symbolic link to the sfs server (fwd)Hi I do have a problem with sfs. After executing "sfssd -d" and "sfscd -d" on the server and the client, I can login to the server, but I cannot browse the directories. This is what I get: -----------------------------server server# sfssd -d sfssd: version 0.7.2, pid 13017 rexd: version 0.7.2, pid 13018 rexd: serving @server.cs.wits.ac.za,ubi4bxdkim3a2qpu43799k9837wpcx6v sfsauthd: version 0.7.2, pid 13019 rexd: spawning /usr/local/lib/sfs-0.7.2/ptyd sfsauthd: serving @server.cs.wits.ac.za,ubi4bxdkim3a2qpu43799k9837wpcx6v sfsrwsd: version 0.7.2, pid 13020 sfsrwsd: serving /sfs/@server.cs.wits.ac.za,ubi4bxdkim3a2qpu43799k9837wpcx6v sfssd: accepted connection from 146.141.27.251 sfsauthd: accepted user root from 146.141.27.251!sfsauthd using SRP password -------------------------------client client# sfscd -d sfscd: version 0.7.2, pid 13066 sfscd: not dropping privileges for debugging nfsmounter: version 0.7.2, pid 13068 nfsmounter: mounted /sfs nfsmounter: mounted /sfs/.mnt/wait sfsrwcd: version 0.7.2, pid 13067 nfsmounter: mounted /sfs/.mnt/0 sfscd: @server.cs.wits.ac.za,ubi4bxdkim3a2qpu43799k9837wpcx6v: No such file or directory sfscd: @server.cs.wits.ac.za,ubi4bxdkim3a2qpu43799k9837wpcx6v: No such file or directory Any help will be appreciated. Thanks Vincent Next Message by Date: click to view message previewSFS-KNOPPIXDear, We customize a KNOPPIX which uses cloop file (compressed loop back device which stores root file system of KNOPPIX) on SFS (Self-certifying File System) via Internet. We call it "SFS-KNOPPIX". SFS-KNOPPIX requires small boot loader (20MB image) only and offers full KNOPPIX functions, Autoconfig, etc. The root file system is obtained via Internet with SFS. SFS-KNOPPIX makes possible to change a cloop file at boot time. It means we don't need to burn extra CD for many KNOPPIX offshoots. SFS-KNOPPIX has three boot variations; CD-boot, USB-Memory-boot and coLinux. The detail is described in the following Home Page. http://unit.aist.go.jp/it/knoppix/sfs/index-en.html Please try if you are interested. And tell me the boot time. We want to know the effect of network latency. The boot time was around 3 minutes in Japan. ------------------------------------------------------------------------ The summary of benefits is as follows. 1. SFS-KNOPPIX enables to use many KNOPPIX offshoots with only one CD-ROM. It enables to select a cloop file at boot time. 2. Network traffic is reduced. 2.1 The Download image of SFS-KNOPPIX is only 20MB, although normal KNOPPIX is 700MB. 2.2 After boot, only necessary cloop blocks are downloaded. The blocks are compressed. 2.3 It requires 50MB download to boot KDE window manager. 3. SFS-KNOPPIX is compatible for normal KNOPPIX. (CD and USB boot version only) 3.1 It uses same kernel version and cloop file. AutoConfig loads same device drivers. 3.4 Hard Disk installer works in the same manner. 4. On USB version. It does not required to burn a CD-ROM. 4.1 The bootability is depend on BIOS on each PC. 5. On coLinux version. It can boot with any cloop file, because coLinux is independent form device drivers. ------------------------------------------------------------------------ ------ suzaki Previous Message by Thread: click to view message previewCannot create a symbolic link to the sfs server (fwd)Hi I do have a problem with sfs. After executing "sfssd -d" and "sfscd -d" on the server and the client, I can login to the server, but I cannot browse the directories. This is what I get: -----------------------------server server# sfssd -d sfssd: version 0.7.2, pid 13017 rexd: version 0.7.2, pid 13018 rexd: serving @server.cs.wits.ac.za,ubi4bxdkim3a2qpu43799k9837wpcx6v sfsauthd: version 0.7.2, pid 13019 rexd: spawning /usr/local/lib/sfs-0.7.2/ptyd sfsauthd: serving @server.cs.wits.ac.za,ubi4bxdkim3a2qpu43799k9837wpcx6v sfsrwsd: version 0.7.2, pid 13020 sfsrwsd: serving /sfs/@server.cs.wits.ac.za,ubi4bxdkim3a2qpu43799k9837wpcx6v sfssd: accepted connection from 146.141.27.251 sfsauthd: accepted user root from 146.141.27.251!sfsauthd using SRP password -------------------------------client client# sfscd -d sfscd: version 0.7.2, pid 13066 sfscd: not dropping privileges for debugging nfsmounter: version 0.7.2, pid 13068 nfsmounter: mounted /sfs nfsmounter: mounted /sfs/.mnt/wait sfsrwcd: version 0.7.2, pid 13067 nfsmounter: mounted /sfs/.mnt/0 sfscd: @server.cs.wits.ac.za,ubi4bxdkim3a2qpu43799k9837wpcx6v: No such file or directory sfscd: @server.cs.wits.ac.za,ubi4bxdkim3a2qpu43799k9837wpcx6v: No such file or directory Any help will be appreciated. Thanks Vincent Next Message by Thread: click to view message previewSFS-KNOPPIXDear, We customize a KNOPPIX which uses cloop file (compressed loop back device which stores root file system of KNOPPIX) on SFS (Self-certifying File System) via Internet. We call it "SFS-KNOPPIX". SFS-KNOPPIX requires small boot loader (20MB image) only and offers full KNOPPIX functions, Autoconfig, etc. The root file system is obtained via Internet with SFS. SFS-KNOPPIX makes possible to change a cloop file at boot time. It means we don't need to burn extra CD for many KNOPPIX offshoots. SFS-KNOPPIX has three boot variations; CD-boot, USB-Memory-boot and coLinux. The detail is described in the following Home Page. http://unit.aist.go.jp/it/knoppix/sfs/index-en.html Please try if you are interested. And tell me the boot time. We want to know the effect of network latency. The boot time was around 3 minutes in Japan. ------------------------------------------------------------------------ The summary of benefits is as follows. 1. SFS-KNOPPIX enables to use many KNOPPIX offshoots with only one CD-ROM. It enables to select a cloop file at boot time. 2. Network traffic is reduced. 2.1 The Download image of SFS-KNOPPIX is only 20MB, although normal KNOPPIX is 700MB. 2.2 After boot, only necessary cloop blocks are downloaded. The blocks are compressed. 2.3 It requires 50MB download to boot KDE window manager. 3. SFS-KNOPPIX is compatible for normal KNOPPIX. (CD and USB boot version only) 3.1 It uses same kernel version and cloop file. AutoConfig loads same device drivers. 3.4 Hard Disk installer works in the same manner. 4. On USB version. It does not required to burn a CD-ROM. 4.1 The bootability is depend on BIOS on each PC. 5. On coLinux version. It can boot with any cloop file, because coLinux is independent form device drivers. ------------------------------------------------------------------------ ------ suzaki Loading Comments...
|
|
