NFS +ext3 - je to dobry napad ?

[Dalibor Straka]

On Mon, Jan 06, 2003 at 12:48:31PM +0100, Michal Kaspar wrote:
> On Mon, Jan 06, 2003 at 12:25:04PM +0100, Ing. Pavel PaJaSoft Janousek wrote:
> > Zdenek Pizl wrote:
> > > damy a panove narazil jsem na hloupy a obtezujici problem. Log stanice, kde je 
> > > primounteny NFS svazek, ma log plny hlasek:
> > > - kernel: nfs: server FILESERVER not responding, timed out
> > > V okamziky, kdy je FILESERVER nedostupny, cela stanice ztuhne, pak se zase vse 
> > > rozbehne, ale vadi to :(
> > 

Chyba rozhodne neni v pouziti ext3. 

> Ano. To že se při nedostupnosti nfs serveru čeká, až bude opšt
> k dispozici je vlastnost NFS. Na klientu lze mountovat s -o soft, která
> zajistí, že po určité době nedostupnosti serveru dojde k time outu. Viz.
> man mount.
> 

muzete napsat do /etc/fstab
#device                mountpoint fs-type options dump fsckord
server.foo.cz:/home/  /mnt/home     nfs   rw,soft  0     0

jenze ouha! Soft musi byt v programu osetrena. Dokumentace uvadi,
cituji:
soft  If a file request fails, the NFS client will report an error to
      the process on the client machine requesting the file access.  
      Some programs can handle this with composure, most won't. We do
      not recommend using this setting; it is a recipe for corrupted
      files and lost data. You should especially not use this for mail
      disks--if you value your mail, that is.

hard  The program accessing a file on a NFS mounted file system will
      hang when the server crashes. The process cannot be interrupted or
      killed (except by a "sure kill") unless you also specivy intr.
      When the NFS server is back online the program will continue
      undisturbed from where it was. we recommend using hard, intr on
      all NFS mounted file system.

tedy   options
    rw,hard,intr


S pozdravem Dada