On Thu, 14 Jun 2007 12:46:18 +0300 lonely wolf wrote: > MOROIANU Dragos wrote: > >>> > >>> > >> verifica daca nu cumva crapa cind incearca sa scrie > >> un lock file in NFS. > > > > Interesanta idee wolfy, dar cum fac verificarea asta? > > Daca incerc sa scriu un fisier "touch cucu", merge, > > dar banuiesc ca nu la asta te-ai referit. > > > fa un test -- de amorul artei -- cu mount -o nolock nfsserver > mount_point
NFS client code s^<ks. http://lkml.org/lkml/2006/10/18/264 Dupa un upgrade de kernel (cine m-a pus?) m-am lovit de problema de acolo. Extras: --- CUT HERE --- "> >>>> I can't write on mounted nfs filesystem since 2.6.19-rc1 (nfs > >>>> client): touch: cannot touch `aaa': Read-only file system [...] I'll bet that you have always had a subdirectory of the exact same filesystem mounted somewhere else ro, right? The new NFS mount code will put those in the same superblock, and whichever directory gets mounted first will determine whether or not the superblock is marked as read-only." --- CUT HERE --- Workaround: se demonteaza toate directoarele montate sub acelasi director si apoi se re-monteaza mai intai cele rw, apoi cele ro. Dragos, sper sa fie si la tine aceeasi problema. -- Adi Pircalabu BitDefender official forum: http://forum.bitdefender.com _______________________________________________ RLUG mailing list RLUG@lists.lug.ro http://lists.lug.ro/mailman/listinfo/rlug
