From: Hans Reiser <reiser@namesys.com>
To: Bill Rees <bill@billrees.com>
Cc: reiserfs-list <reiserfs-list@namesys.com>,
Vitaly Fertman <vitaly@namesys.com>,
vs@namesys.com
Subject: Re: Filesystem Corruption Problems
Date: Wed, 07 May 2003 21:40:22 +0400 [thread overview]
Message-ID: <3EB94506.8020106@namesys.com> (raw)
In-Reply-To: <NHBBIGLOALLFLCNJNOLHGELNCAAA.bill@billrees.com>
Bill Rees wrote:
>Hello,
>
>I have an application that uses multiple drives formatted with reiserfs to
>store many thousands of JPEG images for later retrieval. These images are
>coming from one or more cameras in the form of a streaming MJPEG. My
>application essentially writes images to one or more drives as fast as it
>can. When a set number of hours of storage is reached for a particular
>camera, the program begins deleting old images. Depending on the framerate
>of image capture, the contents of the disk could be rewritten entirely in
>the process of just a few days.
>
>When this application is left running for an extended period of time, severe
>disk corruption usually crops up. Usually, there are media errors in the
>kernel log from the reiser file system indicating something very bad is
>occuring. I have tried recovering from this with reiserfsck but the only
>solution is usually a reformat. Sometimes the corruption does not allow the
>deletion of any files from the drive and sometimes it causes a kernel panic
>whenever the disk is accessed. I am using version 2.4.19 of the kernel
>without any patches. The application is written in Java and runs under JDK
>v1.4.1.
>
>Is this a known issue? I realize that the creation and deletion of thousands
>of files per day creates problems that might not be seen on the typical file
>server. Any info would be appreciated.
>
>Bill
>
>
>
>
>
This is not a known issue. Vladimir and Vitaly will work with you on
trying to debug and reproduce it.
--
Hans
prev parent reply other threads:[~2003-05-07 17:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-07 13:40 Filesystem Corruption Problems Bill Rees
2003-05-07 17:40 ` Hans Reiser [this message]
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=3EB94506.8020106@namesys.com \
--to=reiser@namesys.com \
--cc=bill@billrees.com \
--cc=reiserfs-list@namesys.com \
--cc=vitaly@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.