From: Edward Shishkin <edward.shishkin@gmail.com>
To: Ivan Shapovalov <intelfx100@gmail.com>
Cc: reiserfs-devel@vger.kernel.org
Subject: Re: [FIXED?] reiser4: problem with key inconsistency
Date: Sat, 03 Nov 2012 17:02:10 +0100 [thread overview]
Message-ID: <50954002.50105@gmail.com> (raw)
In-Reply-To: <2414795.eiFhpRrsg9@intelfx-laptop>
On 10/31/2012 06:24 PM, Ivan Shapovalov wrote:
> On 28 октября 2012 22:56:14 Edward Shishkin wrote:
>> Hi all.
>> It seems I do have the long-awaited fix.
>>
>> The symptoms of the problem: kernel starts to issue complaints
>> about key inconsistency with the suggestions to check the partition
>> with fsck. Fsck sometimes finds corruptions, but sometimes reports
>> that file system is consistent.
>>
>> Please apply the attached patch to reiser4 stuff for 3.6.2, or
>> download reiser4-for-3.6.4 (which already contains this patch), and
>> let me know if the problem has not gone:
>> http://sourceforge.net/projects/reiser4/files/reiser4-for-linux-3.x/
>>
>> Please, don't rush to deploy production systems on reiser4: it can
>> take up to 80 hours to reproduce the problem with high workload.
>>
>> Thank you for your help.
>> Edward.
>
> Alas, it hasn't gone... Or maybe it's a different problem, but today (on a
> debugless build) I've got a massive crash (mostly -2 and -5 errors for
> different VFS operations - e.g.
> nikita-717/edward-1611/edward-430/nikita-2219/nikita-2221, many vs-3533 and
> edward-1460/edward-1608/edward-156 warnings).
> Fsck said SIGSEGV,
There are pending patches for reiser4progs, please don't forget to apply
them when checking your partitions:
http://marc.info/?l=reiserfs-devel&m=129703129519745&w=2
http://marc.info/?l=reiserfs-devel&m=127504471326353&w=2
Thanks,
Edward.
so I had to restore from a daily backup. Don't know if that
> is related to allocator, but anyway.
>
> And I don't have much time these days to set up VM with a clone of my system
> for kgdb, sorry... Though I hope I'll do that on next week (on vacations).
>
> BTW, changing RAM didn't help, and old RAM passes memtest - so here it's truly
> a bug somewhere in allocator.
>
> Regards,
> Ivan.
--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-11-03 16:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-28 21:56 [FIXED?] reiser4: problem with key inconsistency Edward Shishkin
2012-10-31 17:24 ` Ivan Shapovalov
2012-10-31 18:43 ` Edward Shishkin
2012-11-04 12:14 ` Ivan Shapovalov
2012-11-03 16:02 ` Edward Shishkin [this message]
2012-11-04 12:09 ` Ivan Shapovalov
2013-01-07 11:05 ` Dušan Čolić
2013-01-17 18:40 ` 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=50954002.50105@gmail.com \
--to=edward.shishkin@gmail.com \
--cc=intelfx100@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.