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@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
