From: Eddie Chapman <eddie@ehuk.net>
To: Edward Shishkin <edward.shishkin@gmail.com>,
reiserfs-devel@vger.kernel.org
Subject: Re: Reiser4 Oops on vanilla 2.6.37.2
Date: Wed, 09 Mar 2011 22:10:37 +0000 [thread overview]
Message-ID: <4D77FADD.9040003@ehuk.net> (raw)
In-Reply-To: <4D77F908.6080206@gmail.com>
On 09/03/11 22:02, Edward Shishkin wrote:
> On 03/06/2011 12:08 AM, reiserfs-devel@vger.kernel.org wrote:
>> On 05/03/11 22:40, Edward Shishkin wrote:
>>> On 03/05/2011 03:29 PM, Eddie Chapman wrote:
>>>> Hello,
>>>
>>> Hello.
>>
>> Thanks for the prompt reply :)
>>
>>>
>>>>
>>>> Firstly many thanks for the brilliant work being put into reiser4.
>>>>
>>>> Been using reiser4 for about 10 days or so on two software raid6
>>>> devices
>>>> containing lots of imap mail directories. One partition has about 55GB
>>>> mail in total, the other only about 4GB.
>>>>
>>>> So far so good with no major problems until this morning, when the Oops
>>>> below (scroll down to bottom of mail) happened. The system continued
>>>> functioning with no apparent data loss except load average rose to 24
>>>> within about 30 secs of the Oops and continued to rise steadily until
>>>> system became unresponsive after 3-4 hrs with load average at 1189.
>>>>
>>>> This is a Centos 5.5 64 bit box with vanilla kernel.org 2.6.37.2 and
>>>> reiser4-for-2.6.37.patch
>>>>
>>>> I have both the raid md devices mounted as reiser4 with
>>>> noatime,nodiratime
>>>>
>>>> I notice this Oops reported here and Edward's patch to address the
>>>> problem:
>>>> http://www.spinics.net/lists/reiserfs-devel/msg02648.html
>>>>
>>>> Searching through reiser4-for-2.6.37.patch it seems that patch is in
>>>> there, but I still got the Oops.
>>>
>>> This is another problem.
>>
>> Aaah yes you're right, I just saw jbd2__journal_start and
>> ext4_journal_start_sb in both Oops but didn't look further.
>>
>>>
>>>>
>>>> Similarly to the previous case, this box is using ext4 for all the
>>>> other
>>>> filesystems.
>>>>
>>>> If another patch is not possible in the near future would downgrading
>>>> the
>>>> other filesystems to ext3 be a temporary workaround for this issue?
>>>
>>> I have attached a temporal workaround, it should help.
>>> Note, that I didn't test this patch: I'll be able to do it
>>> at the end of weekends.
>>
>> Many thanks, I will apply it tonight and report back.
>>
>> Eddie
>
> Sorry, I've encountered strange deadlocks with this patch.
> Please, roll it back and use the attached one as the temporal
> workaround.
>
> Thanks,
> Edward.
Hi Edward,
OK, thanks. I applied the first one at the weekend and the box hasn't
had any problems it is still up. I'll apply this one tonight and email
an update after it has been in use for a while.
I'll update to vanilla 2.6.27.3 at the same time, hope that's OK, if you
think that's a bad idea let me know.
Thanks,
Eddie
next prev parent reply other threads:[~2011-03-09 22:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-05 14:29 Reiser4 Oops on vanilla 2.6.37.2 Eddie Chapman
2011-03-05 22:40 ` Edward Shishkin
2011-03-05 23:08 ` reiserfs-devel
2011-03-09 22:02 ` Edward Shishkin
2011-03-09 22:10 ` Eddie Chapman [this message]
2011-03-15 19:57 ` Eddie Chapman
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=4D77FADD.9040003@ehuk.net \
--to=eddie@ehuk.net \
--cc=edward.shishkin@gmail.com \
--cc=reiserfs-devel@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;
as well as URLs for NNTP newsgroup(s).