public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Samium Gromoff <_deepfire@mail.ru>
Cc: "Vladimir V. Saveliev" <monstr@namesys.com>,
	linux-kernel@vger.kernel.org
Subject: Re: ReiserFS 2.4.4/3.x.0k-pre2
Date: Fri, 18 May 2001 15:55:43 -0700	[thread overview]
Message-ID: <3B05A86F.96E380DC@namesys.com> (raw)
In-Reply-To: <E14zc0K-0000ya-00@f6.mail.ru>

Samium Gromoff 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.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
we would be very eager to receive any testing method that could incurr tail
corruption on a disk drive other than the one that you have that is known
unreliable.


Hans

      parent reply	other threads:[~2001-05-18 22:56 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
2001-05-18 22:55   ` 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=3B05A86F.96E380DC@namesys.com \
    --to=reiser@namesys.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