OK, the app is used to deal with standard disks, that is why it is not handling the EINTR signal propoerly. But I assumed that Lustre is 'just' a filesystem, so applications do not need to handle access to it any other way that the usual way. Anyhow, the signal is from the OS not from the App... So it means that the OS signals the app that it has encoutered an error while trying to write to a file, and it is the source of that that I want to track down. Because this app error only arise every few days, it means that it is not a normal condition : something sowewhere in the FS causes it. Interpreting it as a fatal error is certainly a mistake, but I still don't know why I'm getting this EINTR signal from the OS...
Regards weborama line François Chassaing Directeur Technique - CTO ----- Mail Original ----- De: "Brian J. Murrell" <br...@whamcloud.com> À: lustre-discuss@lists.lustre.org Envoyé: Jeudi 24 Février 2011 14h29:27 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne Objet: Re: [Lustre-discuss] clients gets EINTR from time to time On 11-02-24 08:16 AM, Francois Chassaing wrote: > Well, as I understand your point and I do also understand that this signal is > not a malfunction, No, but not handling it properly is. Interpreting an EINTR as "the disk must be full" (i.e. a fatal error) is wrong. > my question was regarding to the intrinsic "why" (and when) does this signal > is sent to the client. That's completely up to your application. It's the way your application has been written that is determining the hows and whys of signals. b. -- Brian J. Murrell Senior Software Engineer Whamcloud, Inc. _______________________________________________ Lustre-discuss mailing list Lustre-discuss@lists.lustre.org http://lists.lustre.org/mailman/listinfo/lustre-discuss _______________________________________________ Lustre-discuss mailing list Lustre-discuss@lists.lustre.org http://lists.lustre.org/mailman/listinfo/lustre-discuss
