From: "Janos Haar" <janos.haar@netcenter.hu>
To: "Dave Chinner" <david@fromorbit.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Whats going on? (somebody can say something?)
Date: Tue, 30 Sep 2008 14:09:44 +0200 [thread overview]
Message-ID: <3c5801c922f5$a3a8a440$0400a8c0@dcccs> (raw)
In-Reply-To: 20080927014431.GU27997@disturbed
----- Original Message -----
From: "Dave Chinner" <david@fromorbit.com>
To: "Janos Haar" <djani22@netcenter.hu>
Cc: <linux-kernel@vger.kernel.org>; <xfs@premium9.geo.yahoo7.akadns.net>
Sent: Saturday, September 27, 2008 3:44 AM
Subject: Re: Whats going on? (somebody can say something?)
> On Fri, Sep 26, 2008 at 11:27:27AM +0200, Janos Haar wrote:
>> Hello list,
>>
>> Good day for everibody.
>>
>> I have one problem with my new linux box. (again)
>> The hw is tested. (memtest86, 4 days)
>>
>> The samba freezed and makes 40 load.
>>
>> All what i am using is in-kernel solution, excepting samba.
>>
>> libata ->bock -> raid -> cryptoloop -> xfs -> [samba] ->eth
>>
>> The log file is here:
>>
>> http://download.netcenter.hu/bughunt/20080925/messages
>>
>> some points:
>> Sep 24 01:15:58 - Sep 24 01:19:16 -> i have repaired the 2 xfs on loop0
>> and loop1Sep 24 14:18:00 -> only a little interesting time, when the
>> first bug was issued. (cron?)Sep 25 21:47:39 -> i have logged in.Sep 25
>> 21:50:50 -> i have forced the sysreq from script to make some more debug
>> information.(I have saved the lsof too if somebody interested.)Any help
>> will be appreciated.Thanks a lot,Janos Haar
>
> What kernel?
Linux version 2.6.26.2 (root@gl-albth) (gcc version 4.1.1 20061011 (Red Hat
4.1.1-30)) #2 SMP Sun Aug 10 00:00:15 CEST 2008
>
> I have seen all those XFS oops/stack traces before. With the last
> pull request to linus for 2.6.27-rc7, all known causes of the btree
> corruption reported in your log messages should be fixed. I guess
> you'll have to wait for 2.6.27-rc8 or 2.6.28 for them....
unfortunately, i can't wait for this, and don't want to step back in the
versions, this is a productive box. :-(
This time i forced to use another FS, but nex time i will check again with
xfs.
>
> FWIW, next time you have XFS issues, please make it clear in the
> subject line and cc xfs@oss.sgi.com.
Ok, Thank you.
Thanks,
Janos Haar
>
> Cheers,
>
> Dave.
> --
> Dave Chinner
> david@fromorbit.com
prev parent reply other threads:[~2008-09-30 12:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-26 9:27 Whats going on? (somebody can say something?) Janos Haar
2008-09-26 14:47 ` Chris Friesen
2008-09-26 18:07 ` Janos Haar
2008-09-26 21:12 ` Ray Lee
2008-09-30 12:06 ` Janos Haar
2008-09-27 1:44 ` Dave Chinner
2008-09-30 12:09 ` Janos Haar [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='3c5801c922f5$a3a8a440$0400a8c0@dcccs' \
--to=janos.haar@netcenter.hu \
--cc=david@fromorbit.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox