NFS ja Dolphinin kaatuminen???_Ratkaistu!

[COBHC]

Moi,

Eli käytössäni pari konetta, olohuoneessa hyrrää ns. "HTPC" jossa NFS serveri. Kun käytän jaettuja foldereita ne toimivat kuin unelma mutta.....jos vahingossa sammuttaa serverin niin "Client" koneessa jossa levyt näkyvät mountattuna niin dolphin sekoaa täysin eikä näytä home folderissa enää yhtään kansiota...aina joutuu tappamaan X:än ennen kuin saa kansiot näkyviin uudestaan?

Koodia: [Valitse]

ozzman@sorvaamo:~$ uname -a
Linux sorvaamo 2.6.24-19-server #1 SMP Wed Aug 20 23:54:28 UTC 2008 i686 GNU/Linux

Ja käytössä siis KDE 3.5.10... sitten vielä fstab...

Koodia: [Valitse]

ozzman@sorvaamo:~$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    defaults        0       0
# /dev/sda1
UUID=171d78d7-1d3c-44d0-bdb0-df55a14dc609 /               ext3    relatime,errors=remount-ro 0       1
# /dev/sda2
UUID=2aa23f16-fa9d-494e-978f-5ab2c705988b /home           ext3    relatime        0       2
# /dev/sda3
UUID=d1c4ddf9-7e49-4cd7-9ae7-2a6317ac0ca1 none            swap    sw              0       0
/dev/scd0       /media/cdrom0   udf,iso9660 user,noauto,exec,utf8 0       0
/dev/fd0        /media/floppy0  auto    rw,user,noauto,exec,utf8 0       0
#192.168.11.4:/mnt/localnetwork /mnt/localnetwork nfs rw,hard,intr 0 0
192.168.11.4:/home/cobhc/TV /home/ozzman/TV nfs rw,hard,intr 0 0
192.168.11.4:/home/cobhc/Downloads /home/ozzman/Downloads_Server nfs rw,hard,intr 0 0
192.168.11.4:/home/cobhc/MP3 /home/ozzman/MP3_Server nfs rw,hard,intr 0 0
ozzman@sorvaamo:~$


Kiitos ja kumarrus etukäteen...

COB

[Ville Pöntinen]

Tässä lainausta sivulta http://www.faqs.org/docs/linux_network/x-087-2-nfs.mountd.html. Jokin tämmöinen tuli mieleeni kysymyksestäsi...

Itselläni on töissä koko /home mountattuna nfs:n takaa, joten kaiken kuuluukin kaatua jos servu tööttää. Siksi en ole koskaan lukenut tätä ajatuksella, mutta saattaisi liittyä hard/soft -parametriin.

hard

    Explicitly mark this volume as hard-mounted. This is on by default. This option causes the server to report a message to the console when a major timeout occurs and continues trying indefinitely.
soft

    Soft-mount (as opposed to hard-mount) the driver. This option causes an I/O error to be reported to the process attempting a file operation when a major timeout occurs.
intr

    Allow signals to interrupt an NFS call. Useful for aborting when the server doesn't respond.

Except for rsize and wsize, all of these options apply to the client's behavior if the server should become temporarily inaccessible. They work together in the following way: Whenever the client sends a request to the NFS server, it expects the operation to have finished after a given interval (specified in the timeout option). If no confirmation is received within this time, a so-called minor timeout occurs, and the operation is retried with the timeout interval doubled. After reaching a maximum timeout of 60 seconds, a major timeout occurs.

By default, a major timeout causes the client to print a message to the console and start all over again, this time with an initial timeout interval twice that of the previous cascade. Potentially, this may go on forever. Volumes that stubbornly retry an operation until the server becomes available again are called hard-mounted. The opposite variety, called soft-mounted, generate an I/O error for the calling process whenever a major timeout occurs. Because of the write-behind introduced by the buffer cache, this error condition is not propagated to the process itself before it calls the write function the next time, so a program can never be sure that a write operation to a soft-mounted volume has succeeded at all.

Whether you hard- or soft-mount a volume depends partly on taste but also on the type of information you want to access from a volume. For example, if you mount your X programs by NFS, you certainly would not want your X session to go berserk just because someone brought the network to a grinding halt by firing up seven copies of Doom at the same time or by pulling the Ethernet plug for a moment. By hard-mounting the directory containing these programs, you make sure that your computer waits until it is able to re-establish contact with your NFS server. On the other hand, non-critical data such as NFS-mounted news partitions or FTP archives may also be soft-mounted, so if the remote machine is temporarily unreachable or down, it doesn't hang your session. If your network connection to the server is flaky or goes through a loaded router, you may either increase the initial timeout using the timeo option or hard-mount the volumes. NFS volumes are hard-mounted by default.

Hard mounts present a problem because, by default, the file operations are not interruptible. Thus, if a process attempts, for example, a write to a remote server and that server is unreachable, the user's application hangs and the user can't do anything to abort the operation. If you use the intr option in conjuction with a hard mount, any signals received by the process interrupt the NFS call so that users can still abort hanging file accesses and resume work (although without saving the file).

[COBHC]

Moi,

Kiitos ja kumarrus...homma toimii...

Terveisin

COB