reiserfs-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Edward Shishkin <edward.shishkin@gmail.com>
To: Jaroslav Fojtik <jafojtik@seznam.cz>
Cc: reiserfs-devel@vger.kernel.org
Subject: Re: Re2: linux-2.6.37 crash reproduced - here is a screenshot
Date: Wed, 09 Mar 2011 23:16:31 +0100	[thread overview]
Message-ID: <4D77FC3F.1020504@gmail.com> (raw)
In-Reply-To: <4D7214C2.30303.1B55FC@jafojtik.seznam.cz>

On 03/05/2011 11:47 AM, Jaroslav Fojtik wrote:
> Dear Edward Shishkin,
>
>> I don't see any reiser4 bits in the stacktrace.
> It might be scrolled down.

Could you please send your .config?

Thanks,
Edward.

>
> I am sending two new hang reports.
>
>
>> Could you please try to reproduce it without
>> reiser4? Report about results.
> I could try it, but reformating partition on test disk and fill it with
> graphics magick mirror spends around 8 hours. Fortunatelly this process
> is automatical and could run during night.
>
>
> Linux-2.6.32 is very stable. I have never experimented with other releases.
>
> regards
>    Jara
>
>
>
>
>> Thanks,
>> Edward
>>
>>
>>>
>>> best regards
>>>      Jara
>>>
>>>
>>>> On 03/04/2011 12:24 AM, Jaroslav Fojtik wrote:
>>>>> Dear Edward Shishkin,
>>>>>
>>>>>> Great.
>>>>>
>>>>> Sorry, after several attempts I managed to crash Linux even with kernel
>>>>> linux-2.6.37. No trace in log, system completely frozen and beeper
>>>>> sounded.
>>>>>
>>>>> It takes several hours to transfer 400 Gigabyte test data and create
>>>>> full stress of filesystem.
>>>>>
>>>>> I have improved my stress test and managed to find something with mc
>>>>> paralelly with data copying.
>>>>
>>>>
>>>> Ok, I'll try to reproduce.
>>>> Is you "/" on reiser4 partition?
>>>>
>>>> Thanks,
>>>> Edward.
>>>
>>>
>>
>
>


      parent reply	other threads:[~2011-03-09 22:16 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-24  0:19 Question about reiser performance - short system freezes Jaroslav Fojtik
2011-02-24 12:07 ` Edward Shishkin
2011-02-24  3:21   ` Jaroslav Fojtik
2011-02-24 18:29     ` Edward Shishkin
2011-03-01 15:12       ` Re2: " Jaroslav Fojtik
2011-03-01 16:42         ` Edward Shishkin
2011-03-01 21:00           ` Re4: " Jaroslav Fojtik
2011-03-01 21:19             ` Nicolas Barbier
2011-03-01 21:23             ` Edward Shishkin
2011-03-01 21:24               ` Edward Shishkin
2011-03-03 21:26               ` Re6: " Jaroslav Fojtik
2011-03-03 22:09                 ` Edward Shishkin
2011-03-03 23:24                   ` Re8: Question about reiser performance - linux-2.6.37 crash reproduced Jaroslav Fojtik
2011-03-03 23:29                     ` Edward Shishkin
2011-03-03 23:38                       ` Re10: " Jaroslav Fojtik
2011-03-04 14:30                         ` Edward Shishkin
2011-04-16 11:17                         ` doiggl
     [not found]                       ` <4D7161F7.2754.6FF32@jafojtik.seznam.cz>
2011-03-04 22:58                         ` linux-2.6.37 crash reproduced - here is a screenshot Edward Shishkin
     [not found]                           ` <4D7214C2.30303.1B55FC@jafojtik.seznam.cz>
2011-03-05 22:44                             ` Re2: " Edward Shishkin
2011-03-09 22:16                             ` Edward Shishkin [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=4D77FC3F.1020504@gmail.com \
    --to=edward.shishkin@gmail.com \
    --cc=jafojtik@seznam.cz \
    --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).