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: Fri, 14 Jul 2006 14:03:30 +0200 [thread overview]
Message-ID: <200607141403.33613.fjcabello@visual-tools.com> (raw)
In-Reply-To: <1152877739.6407.37.camel@tribesman.namesys.com>
[-- Attachment #1: Type: text/plain, Size: 3492 bytes --]
Yes. I have a sef of system with the same main board, memory,
microprocessor... They are identical. The difference is the conditions where
they are working. Perhaps the cpu load average is difference, the amount of
data they are writting, the number of power failure...
I am going to send you the output of reiserfsck of some the systems.
Regards,
Paco
On Friday, 14 de July de 2006 13:48, Vladimir V. Saveliev wrote:
> Hello
>
> On Fri, 2006-07-14 at 10:25 +0200, Francisco Javier Cabello wrote:
> > Hello,
> > I am almost sure that unclean shutdowns happen in those systems. We have
> > tried to reproduce removing power each 5 minutes and the filesystem
> > wasn't suffering corruption. Perhaps it's related, but I don't know.
> >
> > I have talked about 'Datalogging patches' because it's the only thing
> > different from our system.
>
> sorry, I am confused. Am I correct that you have set of systems and they
> all run similar load on the same kernel and only ~10% of them encounter
> reiserfs corruptions? Do they have identical hardware?
>
> > I have searched a lot and few people have
> > corruption with reiserfs standalone... so, it may be datalogging patches.
> >
> > what do you need from reiserfsck? I guess the output of 'reiserfsck
> > --check device'
>
> yes. There is -l option to redirect output to log file.
>
> > of perhaps you need the output of reiserfsck --rebuild tree.
> >
> >
> > Regards,
> >
> > Paco
> >
> > On Thursday, 13 de July de 2006 16:34, Vladimir V. Saveliev wrote:
> > > Hello
> > >
> > > On Wed, 2006-07-12 at 08:16 +0200, Francisco Javier Cabello wrote:
> > > > Hello,
> > > > My company develops video recorder system. Basically we work with
> > > > linux boxes running kernel 2.4.25. The system captures analogue
> > > > video, and after processing and compressing, digital video is stored
> > > > to hard disk. We are recording continuously (24x7).
> > > >
> > > > We have realized that more or less a 10% of our systems are suffering
> > > > data corruption in the reiserfs partition.
> > >
> > > Did unclean shutdowns take place on those systems?
> > > If you let us see what does reiserfsck report in those cases that could
> > > help to understand what is is happening.
> > >
> > > > Sometimes it's possible to fix it
> > > > running 'reiserfsck --rebuild-tree' but not always.
> > > > More information:
> > > > -Kernel 2.4.25 + v4l2 patches
> > > > -Reiserfsprogs 3.6.19
> > > > -Datalogging patches.
> > > > (http://mirror.mcs.anl.gov/suse-people/mason/patches/data-logging/2.4
> > > >.25/ )
> > > >
> > > > I have checked datalogging patches from Reiserfs website and they
> > > > seem equal to suse ones.
> > > >
> > > > I don't have any idea of what it's happening. The disk bandwidth is
> > > > not so high (300-500kb/sec). The disk is always full at 90% (we have
> > > > a process deleting old video).
> > > >
> > > > I have been thinking about removing Dataloggin patches but I would
> > > > like to have serious reason. It's not easy to check that the problem
> > > > is solved because we are not able to reproduce the error in our
> > > > headquarter.
> > > >
> > > > Regards,
> > > >
> > > > Paco
--
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-14 12:03 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 [this message]
2006-07-14 12:20 ` Francisco Javier Cabello
2006-07-14 12:59 ` Vladimir V. Saveliev
2006-07-17 8:53 ` Francisco Javier Cabello
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=200607141403.33613.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.