From: Samium Gromoff <_deepfire@mail.ru>
To: reiser@namesys.com
Cc: linux-kernel@vger.kernel.org
Subject: tail corruptions: saga continues
Date: Thu, 13 Sep 2001 00:33:23 +0000 (UTC) [thread overview]
Message-ID: <200109130033.f8D0XPw00866@vegae.deep.net> (raw)
2.4.7/3.x.0k-pre8 pair in _very_rare_ circumsistances
gives tails corruptions with --rebuild-tree.
Actually i found only one file filled with "." (ofcourse <4k)
As a detail, on sudden reboots i have log tails filled with "."
but it seems to be unrelated.
It may look like this one file "." fill was caused by sudden
inability to sync while corruption raised, but in fact at the moment
when fs was corrupted i havent accessed this file for ages... (.c file)
Cheers, Samium Gromoff
next reply other threads:[~2001-09-12 20:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-13 0:33 Samium Gromoff [this message]
[not found] <3BA080E2.39742E30@namesys.com>
2001-09-15 4:04 ` Samium Gromoff
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=200109130033.f8D0XPw00866@vegae.deep.net \
--to=_deepfire@mail.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@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
all inboxes | Powered by JetHome®