Hi, I''m kind of replying to a discussion from October 2006, when someone asked for the meaning of "LustreError: 9799:0:(filter_io_26.c:646:filter_commitrw_write())error starting transaction: rc = -30". Evan replied>The -30 is the Error EROFS or Read-only file system.My question: where does this knowledge come from? How can I find out about the meaning of Lustre crypticism if Google does not send me to a helpful note on a mailing list? I have never been able to find a coherent explanation of the constant blubbering of Lustre (even if there is no error). Likewise I have never found the part of the Lustre message that is officially called "Lustre error message or error ID" and thus could be pasted into RAS, error.lustre.org Anybody ever been able to use that page? Thanks, Thomas
On Thursday 13 September 2007 18:05:35 Thomas Roth wrote:> Hi, > > I''m kind of replying to a discussion from October 2006, when someone > asked for the meaning of > "LustreError: 9799:0:(filter_io_26.c:646:filter_commitrw_write())error > starting transaction: rc = -30". > Evan replied > > >The -30 is the Error EROFS or Read-only file system. > > My question: where does this knowledge come from? How can I find out > about the meaning of Lustre crypticism if Google does not send me to a > helpful note on a mailing list? I have never been able to find a > coherent explanation of the constant blubbering of Lustre (even if there > is no error). > Likewise I have never found the part of the Lustre message that is > officially called "Lustre error message or error ID" and thus could be > pasted into RAS, error.lustre.org Anybody ever been able to use that page?Usually these are just errno numbers. So for -30 see errno-base.h: #define EROFS 30 /* Read-only file system */ Cheers, Bernd -- Bernd Schubert Q-Leap Networks GmbH
Yes, these are standard C errnos. Here''s the bash macro I use to
translate
them for me:
errno() {
for i in `find /usr/include -name errno*.h`; do
expand $i | grep " "$1" "
done
}
The RAS message IDs are clearly identified in the messages that have them,
but only a very few have them
at present. We are trying to clean them up in a "most-common-first"
order,
and they only appear in the most recent Lustre releases.
On 9/13/07, Thomas Roth <t.roth at gsi.de> wrote:>
> Hi,
>
> I''m kind of replying to a discussion from October 2006, when
someone
> asked for the meaning of
> "LustreError: 9799:0:(filter_io_26.c:646:filter_commitrw_write())error
> starting transaction: rc = -30".
> Evan replied
> >The -30 is the Error EROFS or Read-only file system.
>
> My question: where does this knowledge come from? How can I find out
> about the meaning of Lustre crypticism if Google does not send me to a
> helpful note on a mailing list? I have never been able to find a
> coherent explanation of the constant blubbering of Lustre (even if there
> is no error).
> Likewise I have never found the part of the Lustre message that is
> officially called "Lustre error message or error ID" and thus
could be
> pasted into RAS, error.lustre.org Anybody ever been able to use that page?
>
> Thanks,
> Thomas
>
> _______________________________________________
> Lustre-discuss mailing list
> Lustre-discuss at clusterfs.com
> https://mail.clusterfs.com/mailman/listinfo/lustre-discuss
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://mail.clusterfs.com/pipermail/lustre-discuss/attachments/20070913/a2af40fa/attachment-0001.html
hmm.. I like that..
here is what I have as my script:
------------------BEGIN
#!/bin/sh
grep -h $1 /usr/include/*/errno*
-------------------END
Evan
________________________________
From: Nathan Rutman [mailto:nathan at clusterfs.com]
Sent: Thursday, September 13, 2007 9:46 AM
To: Thomas Roth
Cc: lustre-discuss; Felix, Evan J
Subject: Re: [Lustre-discuss] Understanding Lustre errors
Yes, these are standard C errnos. Here''s the bash macro I use
to translate them for me:
errno() {
for i in `find /usr/include -name errno*.h`; do
expand $i | grep " "$1" "
done
}
The RAS message IDs are clearly identified in the messages that
have them, but only a very few have them
at present. We are trying to clean them up in a
"most-common-first" order, and they only appear in the most recent
Lustre releases.
On 9/13/07, Thomas Roth <t.roth at gsi.de> wrote:
Hi,
I''m kind of replying to a discussion from October 2006,
when someone
asked for the meaning of
"LustreError:
9799:0:(filter_io_26.c:646:filter_commitrw_write())error
starting transaction: rc = -30".
Evan replied
>The -30 is the Error EROFS or Read-only file system.
My question: where does this knowledge come from? How
can I find out
about the meaning of Lustre crypticism if Google does
not send me to a
helpful note on a mailing list? I have never been able
to find a
coherent explanation of the constant blubbering of
Lustre (even if there
is no error).
Likewise I have never found the part of the Lustre
message that is
officially called "Lustre error message or error ID" and
thus could be
pasted into RAS, error.lustre.org Anybody ever been able
to use that page?
Thanks,
Thomas
_______________________________________________
Lustre-discuss mailing list
Lustre-discuss at clusterfs.com
https://mail.clusterfs.com/mailman/listinfo/lustre-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://mail.clusterfs.com/pipermail/lustre-discuss/attachments/20070913/37d45144/attachment.html