From: Samium Gromoff <_deepfire@mail.ru>
To: vs@namesys.com (Vladimir V. Saveliev)
Cc: linux-kernel@vger.kernel.org
Subject: Re: tail corruptions: saga continues
Date: Sat, 15 Sep 2001 04:04:01 +0000 (UTC) [thread overview]
Message-ID: <200109150404.f8F44wV02060@vegae.deep.net> (raw)
In-Reply-To: <3BA080E2.39742E30@namesys.com> from "Vladimir V. Saveliev" at Sep 13, 2001 01:48:18 PM
" Vladimir V. Saveliev wrote:"
>
> Hi
>
> > Subject: tail corruptions: saga continues
> > Date: Thu, 13 Sep 2001 00:33:23 +0000 (UTC)
> > From: Samium Gromoff <_deepfire@mail.ru>
> > To: reiser@namesys.com
> > CC: linux-kernel@vger.kernel.org
> >
> > 2.4.7/3.x.0k-pre8 pair in _very_rare_ circumsistances
>
> You should get 3.x.0k-pre9.
Ouch! Actually that was pre9... sorry for a mistake.
>
> >
> > 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)
> >
>
> So, am I correct that before running reiserfsck --rebuild-tree the file
> contained proper data and did not after it?
Yep
> Or the file appeared corrupted after sudden reboot/mount and it was not
> touched before that sudden crash?
>
> Why did you decide to run --rebuild-tree? Did reiserfsck --check recommend you
> to do that?
To repair fs with some blocks set to zero. Zeroified blks are unrelated though...
>
> Thanks,
> vs
>
>
>
next parent reply other threads:[~2001-09-14 23:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3BA080E2.39742E30@namesys.com>
2001-09-15 4:04 ` Samium Gromoff [this message]
2001-09-13 0:33 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=200109150404.f8F44wV02060@vegae.deep.net \
--to=_deepfire@mail.ru \
--cc=linux-kernel@vger.kernel.org \
--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 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®