reiserfs-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Edward Shishkin <edward.shishkin@gmail.com>
To: intelfx@intelfx.name,
	Reiserfs development mailing list
	<reiserfs-devel@vger.kernel.org>
Subject: Re: reiser4: BUG during a backup (sequentially reading the whole fs) on 4.9
Date: Mon, 27 Feb 2017 17:30:58 +0100	[thread overview]
Message-ID: <4a88640c-8d98-1cc0-5713-3abd76abf208@gmail.com> (raw)
In-Reply-To: <1488212421.5395.3.camel@intelfx.name>

Please, check your partition with fsck (repair if damaged).
Then build the kernel with the following patch applied: 
9eca07b7b992724446d5e7327c86bb0bf1f20a41
Let me know, if the oops appears again.

Thanks,
Edward.

On 02/27/2017 05:20 PM, Ivan Shapovalov wrote:
> I'm on this one:
>
> commit 40d2771c607aab3817f21c394ae39e3fba11aa2f
> Author: Edward Shishkin <edward.shishkin@gmail.com>
> Date:   Thu Jan 26 13:16:39 2017 +0100
>
>      Reiser4: use vmalloc instead of kmalloc to alloacte zhash table
>
>      Signed-off-by: Edward Shishkin <edward.shishkin@gmail.com>
>


  reply	other threads:[~2017-02-27 16:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-27 16:01 reiser4: BUG during a backup (sequentially reading the whole fs) on 4.9 Ivan Shapovalov
2017-02-27 16:17 ` Edward Shishkin
2017-02-27 16:20   ` Ivan Shapovalov
2017-02-27 16:30     ` Edward Shishkin [this message]
2017-06-01 14:49       ` Ivan Shapovalov
2017-06-01 17:43         ` Edward Shishkin
2017-06-01 17:46           ` Ivan Shapovalov
2017-06-01 20:00             ` Edward Shishkin
2017-06-01 22:59               ` Ivan Shapovalov
2017-06-02 20:37                 ` Edward Shishkin
2017-06-02 23:21                   ` Ivan Shapovalov
2017-06-03  7:39                     ` Edward Shishkin
2017-06-05 13:41             ` Edward Shishkin

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=4a88640c-8d98-1cc0-5713-3abd76abf208@gmail.com \
    --to=edward.shishkin@gmail.com \
    --cc=intelfx@intelfx.name \
    --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).