From: Francisco Javier Cabello <fjcabello@visual-tools.com>
To: "Vladimir V. Saveliev" <vs@namesys.com>
Cc: reiserfs-list@namesys.com
Subject: Re: data corruption with 2.4.25 and datalogging patches
Date: Mon, 17 Jul 2006 10:53:33 +0200 [thread overview]
Message-ID: <200607171053.42044.fjcabello@visual-tools.com> (raw)
In-Reply-To: <1152881975.6407.58.camel@tribesman.namesys.com>
[-- Attachment #1: Type: text/plain, Size: 2388 bytes --]
Hello Vladimir,
> such corruptions used to be considered as hardware bugs. Memory failure,
> for instance. Did you ever run memtest on your systems?
Yes, We have run memtest in our system. It's very seldom to find a system with
a hardware memory problem running. When we find a memory problem the kernel
doesn't boot. I am going to pass memtest in some of the system with reiserfs
corruption problem.
Could I give you more information? Perhaps if I run 'reiserfsck
--rebuild-tree' and I give you the traces... would it be useful?
Regards,
Paco
On Friday, 14 de July de 2006 14:59, Vladimir V. Saveliev wrote:
> Hello
>
> On Fri, 2006-07-14 at 14:20 +0200, Francisco Javier Cabello wrote:
> > Hello Vladimir,
> >
> > # reiserfsck -l /tmp/reiserfsck.log -y --check /dev/hdc1
> >
> > Standard output:
> > ======================================================
> > Will read-only check consistency of the filesystem on /dev/hdc1
> > Will put log info to '/tmp/reiserfsck.log'
> > ###########
> > reiserfsck --check started at Fri Jul 14 14:09:33 2006
> > ###########
> > Replaying journal..
> > Reiserfs journal '/dev/hdc1' in blocks [18..8211]: 0 transactions
> > replayed Checking internal tree..finished
> > Comparing bitmaps..Bad nodes were found, Semantic pass skipped
> > 1 found corruptions can be fixed only when running with --rebuild-tree
> > ###########
> > reiserfsck finished at Fri Jul 14 14:13:29 2006
> > ###########
> > ======================================================
> >
> > /tmp/reiserfsck.log:
> > ======================================================
> > bad_internal: vpf-10320: block 23868569, items 91 and 92: The wrong order
> > of items: [410810496 11321 0x16abca00 ??? (15)], [11312 11321 0x22f1c880
> > DIR (3)]
>
> such corruptions used to be considered as hardware bugs. Memory failure,
> for instance. Did you ever run memtest on your systems?
>
> > the problem in the internal node occured (23868569), whole subtree is
> > skipped vpf-10640: The on-disk and the correct bitmaps differs.
> > ======================================================
--
One of my most productive days was throwing away 1000 lines of code (Ken
Thompson)
-----------------
PGP fingerprint: AF69 62B4 97EB F5BB 2C60 B802 568A E122 BBBE 5820
PGP Key available at http://pgp.mit.edu
-----------------
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-07-17 8:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-12 6:16 data corruption with 2.4.25 and datalogging patches Francisco Javier Cabello
2006-07-12 8:24 ` Hans Reiser
2006-07-13 14:34 ` Vladimir V. Saveliev
2006-07-14 8:25 ` Francisco Javier Cabello
2006-07-14 11:48 ` Vladimir V. Saveliev
2006-07-14 12:03 ` Francisco Javier Cabello
2006-07-14 12:20 ` Francisco Javier Cabello
2006-07-14 12:59 ` Vladimir V. Saveliev
2006-07-17 8:53 ` Francisco Javier Cabello [this message]
2006-07-17 17:55 ` Vladimir V. Saveliev
2006-07-17 18:14 ` Brad Dameron
2006-07-17 19:12 ` Hans Reiser
2006-07-17 20:09 ` Valdis.Kletnieks
2006-07-17 21:01 ` Toby Thain
2006-07-17 21:01 ` Toby Thain
2006-07-17 10:49 ` Francisco Javier Cabello
2006-07-19 12:33 ` Francisco Javier Cabello
2006-07-20 7:29 ` Francisco Javier Cabello
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=200607171053.42044.fjcabello@visual-tools.com \
--to=fjcabello@visual-tools.com \
--cc=reiserfs-list@namesys.com \
--cc=vs@namesys.com \
/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.