| To: | linux-xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Re: [RESOLVED] Re: XFS internal error |
| From: | Nicolas Kowalski <Nicolas.Kowalski@xxxxxxx> |
| Date: | Fri, 16 May 2003 17:37:57 +0200 |
| In-reply-to: | <1053096849.6181.5.camel@jen.americas.sgi.com> (Steve Lord's message of "16 May 2003 09:54:09 -0500") |
| References: | <vqowugrb4o2.fsf@astazou.imag.fr> <vqok7crf8d6.fsf@astazou.imag.fr> <vqoptmj9cf7.fsf_-_@astazou.imag.fr> <1053096849.6181.5.camel@jen.americas.sgi.com> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Gnus/5.090015 (Oort Gnus v0.15) XEmacs/21.4 (Common Lisp) |
Steve Lord <lord@xxxxxxx> writes: [...] > What you saw was an internal trace message from xfs due to an fs > consistency check. Looks like the bad fid was coming down to a > disk block which was not inodes. > > These stack traces are intended to diagnose problems with corrupt > filesystems, but they appear to be coming out in a couple of spots > where we do not want them to. Ok, thanks for this information. Just for my knowledge, what are the other "spots" where these messages can appear, so that I will not confuse anymore real XFS filesytems consistency problems with other harmless situations ? -- Nicolas |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [RESOLVED] Re: XFS internal error, Steve Lord |
|---|---|
| Next by Date: | Re: [RESOLVED] Re: XFS internal error, James Pearson |
| Previous by Thread: | Re: [RESOLVED] Re: XFS internal error, Steve Lord |
| Next by Thread: | Re: [RESOLVED] Re: XFS internal error, James Pearson |
| Indexes: | [Date] [Thread] [Top] [All Lists] |