[Lustre-discuss] Lustre client bug (?)

[Andrew Godziuk]

Hi,

I'm not sure where I should report it but I couldn't find the error
text in Google so I guess it's not in bug tracker yet.

This appeared on CentOS 64-bit client under light traffic. Lustre
1.8.2 patchless client from Sun, Linux 2.6.28.10 #4 SMP, both without
custom patches. I'm not sure what more details I could supply.

mx1 kernel: LustreError:
20716:0:(statahead.c:149:ll_sai_entry_cleanup())
ASSERTION(list_empty(&entry->se_list)) failed
Message from syslogd@ at Thu Apr 22 04:31:50 2010 ...
mx1 kernel: LustreError: 20716:0:(statahead.c:149:ll_sai_entry_cleanup()) LBUG

--
Andrzej Godziuk
http://CloudAccess.net/
_______________________________________________
Lustre-discuss mailing list
Lustre-...@lists.lustre.org
http://lists.lustre.org/mailman/listinfo/lustre-discuss

--
You received this message because you are subscribed to the Google Groups "lustre-discuss-list" group.
To post to this group, send email to lustre-di...@googlegroups.com.
To unsubscribe from this group, send email to lustre-discuss-...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/lustre-discuss-list?hl=en.

[Brian J. Murrell]

On Thu, 2010-04-22 at 16:36 +0200, Andrew Godziuk wrote:
> Hi,
>
> I'm not sure where I should report it but I couldn't find the error
> text in Google so I guess it's not in bug tracker yet.

Hrm. I'd not be too sure that Google has indexed the entire of our
Bugzilla. Maybe it has, but searching it directly is probably more
definitive.

> This appeared on CentOS 64-bit client under light traffic. Lustre
> 1.8.2 patchless client from Sun, Linux 2.6.28.10 #4 SMP, both without
> custom patches. I'm not sure what more details I could supply.
>
> mx1 kernel: LustreError:
> 20716:0:(statahead.c:149:ll_sai_entry_cleanup())
> ASSERTION(list_empty(&entry->se_list)) failed
> Message from syslogd@ at Thu Apr 22 04:31:50 2010 ...
> mx1 kernel: LustreError: 20716:0:(statahead.c:149:ll_sai_entry_cleanup()) LBUG

I can't find an existing bug in our bugzilla regarding this
ASSERTION/LBUG. ASSERTION/LBUGs are logic conditions that were
unexpected. They are also fatal errors that need the node to rebooted
to resolve.

Can you please a file a bug in our bugzilla about this one. Please
attach the syslog from the node that hit the LBUG. Include a few hours
of syslog prior to the LBUG if you can.

b.