Lustre devel - Dec 2006 - [Bug 10991] mds_intent_policy()) ASSERTION(new_lock != NULL)

Please don''t reply to lustre-devel. Instead, comment in Bugzilla by
using the following link:
https://bugzilla.lustre.org/show_bug.cgi?id=10991

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |lustre-
                   |                            |list@forge.frec.bull.fr


cc: lustre-list@forge.frec.bull.fr

Please don''t reply to lustre-devel. Instead, comment in Bugzilla by
using the following link:
https://bugzilla.lustre.org/show_bug.cgi?id=10991



*** Bug 11492 has been marked as a duplicate of this bug. ***

Please don''t reply to lustre-devel. Instead, comment in Bugzilla by
using the following link:
https://bugzilla.lustre.org/show_bug.cgi?id=10991



We''ve applied this fix to our tree and it appears to be working out
well with
one remaining issue.  Part of the fix resides server side so in our environment
where we simply plan to update the clients and not the server this fix will not
totally resolve the issue.  That is lustre 1.4.7.2-pre-12llnl clients talking to
1.4.6.95-17.2llnl servers can still crash due to this bug.  As a futher
improvement to maintain lustre version compatibility it would be better if
instead of having the client LBUG it would simply discard the RPC and carry on,
perhaps logging a message.