You get NFS timeouts because you are using soft mounts. Normally, mounts are hard, which requires the client to continue attempts to reach the server forever. A soft mount allows the client to stop trying an operation after a period of time. A soft timeout may cause silent data corruption if it occurs during data or metadata transmissions, so you should only use soft mounts in the cases where client responsiveness is more important than data integrity.

We expect the following local file systems to work, as they are tested often: ext2, ext3, jfs, reiserfs, xfs. These local file systems may work or may have a few minor-ish issues: iso9660, ntfs, reiser4, udf. Ask on the NFS mailing list for details. Any file system based on FAT or not having the ability to provide permanent inode numbers will have trouble with NFS versions 2 and 3 (see question C4).

NFS Version 2 supports up to 8KB reads and writes. NFS Version 3 allows larger reads and writes (see question A1). Stock 2.4 kernels earlier than 2.4.20 do not support read or write operations larger than 8192 bytes for either NFS Version 2 or 3. Server-side TCP support, introduced as an experimental compile-time option in 2.4.20, increases the server's maximum I/O size to 32KB by increasing the value of NFSSVC_MAXBLKSIZE (see question B2).

Some versions of the Linux NFS code only accept mount requests from a privileged port; try # mount -o -P linuxbox:/blah /mnt

Sun workstations running SunOS 4.X only accept mount requests from a privileged port; try # mount -o -P sunbox:/blah /mnt The most frequent problem is not understanding the correct format of /etc/exports. Please review exports(5) and the NFS entry in the Handbook, especially the section on configuring NFS.

Yes, but there is no guarantee it will always work. There are no restrictions in the software which limit where the source data is located. However, CD-R requires a continuous stream of data as it is writing, and a busy network could interfere with performance. Also remember, the greater the recording speed the greater the sustained data transfer rate the drive requires. It is easy to test using a Dummy Write. Slow down the write speed and increase the buffer size.

Some versions of the Linux NFS code only accept mount requests from a privileged port; try # mount -o -P linuxbox:/blah /mnt

etc/exports contains information about how file systems should normally be exported. This is only read by exportfs. var/lib/nfs/etab contains information about what filesystems should be exported to whom at the moment. var/lib/nfs/rmtab contains a list of which filesystems actually are mounted by certain clients at the moment. proc/fs/nfs/exports contains information about what filesystems are exported to actual client (individual, not subnet or whatever) at the moment.

Servers A, B, and C each have a $50 setup fee, as do our Solaris Servers. Server M has a $100 setup fee and includes SSL. When paying by credit card, the setup fee will automatically be charged to your card when the Server is first setup. When paying by check, order processing begins upon receipt of the setup fee and a deposit equivalent to the cost of one month of service.

ie. yourdomain.com or yourdomain.4java.ca). Note that if you are trying to have your application talk to the smtp server, you should use localhost as the url to connect to.

The FAT file systems can be exported, starting with the early 2.4 kernels, but if used extensively, it may cause grief. First, only those operations supported by the exported file system will be honoured. Operations such as "chown", "link", and "symlink" are not supported by these file systems, and will fail. Read/write/create etc., should be fine, as long as the files remain relatively unchanged.

When an NFS server exports a subdirectory of a local file system, but leaves the rest unexported, the NFS server must check whether each NFS request is against a file residing in the area that is exported. This check is called the subtree check. To perform this check, the server includes information about the parent directory of each file in NFS file handles that are handed out to NFS clients.

They happen when a NFS setattr operation is attempted on a file you don't have write access to. These messages are harmless.

A file server is a computer and a storage device that is dedicated to storing files. It hosts, or "contains", the file you're trying to download, so when you click on a download link, your computer connects to the server and copies the file over to your system. [Back to Top]

We are encouraging this for users so their files are backed-up! This is not a do-it-yourself project. Please contact your dept tech or Brent Norum, x4560.

Solution is to mount remote systems on the parent system and then access those files from the /mnt/host directory on the UML virtual machine. This has been fixed in version 1.2 onwards. Alternatively use mount with smbfs as this does work.

Yes. Just backup as usual but add '-d /mnt/nfs' or wherever your partition is mounted; don't use '-Oc' or '-Ot' at all; just '-Oi -d /root'. Then, after booting from the media which Mondo generates, you need to type 'ISO' at the console.

Yes, you can export files on OCFS2 via the standard Linux NFS server. Please note that only NFS version 3 and above will work. In practice, this means clients need to be running a 2.4.x kernel or above.

Actually X-Cart license forbids running X-Cart on unregistered URL, but anyway we allow to setup the software on your local computer if the software is not used for commercial purposes and your local website is not available for public visitors. Since the administrator back-end of X-Cart online demo is publicly available for demonstration purposes, we limited some X-Cart administrator functions using the so-called "safe mode".