From: Chris Mason <mason@suse.com>
To: Samium Gromoff <_deepfire@mail.ru>,
"Vladimir V. Saveliev" <monstr@namesys.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Re[2]: ReiserFS 2.4.4/3.x.0k-pre2
Date: Tue, 15 May 2001 11:43:19 -0400 [thread overview]
Message-ID: <1078540000.989941399@tiny> (raw)
In-Reply-To: <E14zc0K-0000ya-00@f6.mail.ru>
On Tuesday, May 15, 2001 02:24:36 PM +0400 Samium Gromoff
<_deepfire@mail.ru> wrote:
> Hello,
> I`m still experiencing file tail corruptions
> on subj.
> And more: after i had restored bblocked patrition
> (by relying on drive`s ability to remap bblks on
> write by wroting small modification of debugreiserfs
> which zeroified all bblks), i had _runtime_ tail
> corruptions of the mc`s dir hotlist which i tried
> to rewrite again and again.
> i found, that "sync"ing after modifying helps to keep
> file fine, so it does until now.
Hmmm, are you sure the disk is good now?
What kinds of things are you doing on the files where you see tail
corruptions? Can you reliably reproduce the corruption?
-chris
next prev parent reply other threads:[~2001-05-15 15:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3AF6A6D2.B0C285BC@namesys.com>
2001-05-15 10:24 ` Re[2]: ReiserFS 2.4.4/3.x.0k-pre2 Samium Gromoff
2001-05-15 15:43 ` Chris Mason [this message]
2001-05-18 22:55 ` Hans Reiser
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=1078540000.989941399@tiny \
--to=mason@suse.com \
--cc=_deepfire@mail.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=monstr@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox