All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Francisco Javier Cabello <fjcabello@visual-tools.com>
Cc: reiserfs-list@namesys.com, Chris Mason <mason@suse.com>
Subject: Re: data corruption with 2.4.25 and datalogging patches
Date: Wed, 12 Jul 2006 01:24:11 -0700	[thread overview]
Message-ID: <44B4B1AB.5060001@namesys.com> (raw)
In-Reply-To: <200607120816.11292.fjcabello@visual-tools.com>

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. 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
>
>
>  
>
Unless Chris has an idea what might be going on off the top of his head,
this sounds like a paid support problem, and I must say it sounds like
it could be a lot of work to reproduce it.  If solving it still
interests you, we charge $150/hr.

I have made no efforts to test and verify the datalogging patches
myself, and most users do meta-data journaling, so I cannot say much
without assigning to someone the task of reviewing them and your problem.

Reiser4 might be a desirable answer for you.

  reply	other threads:[~2006-07-12  8:24 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 [this message]
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
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=44B4B1AB.5060001@namesys.com \
    --to=reiser@namesys.com \
    --cc=fjcabello@visual-tools.com \
    --cc=mason@suse.com \
    --cc=reiserfs-list@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.