**SPAM** Re: [Linux-cluster] (no subject)

[Stéphane Messerli]

Thanks for your answer.
We will definitely try the latest cvs code very soon. 

In the meantime, we've been able to identify a potential cause of our
problems.
Most (80%) of the lock_dlm (and a few other gfs related bugs) errors happen
while a tar is reading files from the gfs file system and writing the output
to a nfs mount point of another machine.

Does gfs have known issues with nfs mount points?

Thanks,
- Stéphane Messerli (stephane.messerli at urbanet.ch)




-----Message d'origine-----
De : linux-cluster-bounces at redhat.com
[mailto:linux-cluster-bounces at redhat.com] De la part de David Teigland
Envoyé : mercredi, 15. septembre 2004 05:41
À : St?phane Messerli
Cc : linux-cluster at redhat.com
Objet : **SPAM** Re: [Linux-cluster] (no subject)

On Tue, Sep 14, 2004 at 11:22:55AM +0200, St?phane Messerli wrote:

> Any idea of what's wrong or what we should we check next?

I think this is a new one.

> Is it possible to "unlock" the machines after such an error without 
> reboot?

No, the machine needs to be reset when you get this.

> The release version is DEVEL.1090589850.

That looks like July 23; you should probably update to what's in cvs and let
us know if anything changes.

--
Dave Teigland  <teigland at redhat.com>

--
Linux-cluster mailing list
Linux-cluster at redhat.com
http://www.redhat.com/mailman/listinfo/linux-cluster