From: Oleg Drokin <green@namesys.com>
To: Robert Tiismus <robert@fi.tartu.ee>
Cc: reiserfs-list@namesys.com
Subject: Re: Catastrophe with mailboxes on ReiserFS
Date: Wed, 9 Oct 2002 12:18:11 +0400 [thread overview]
Message-ID: <20021009121811.A22948@namesys.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0210091041350.880-100000@fii.fi.tartu.ee>
Hello!
On Wed, Oct 09, 2002 at 11:06:36AM +0300, Robert Tiismus wrote:
> > Also you probably want to run reiserfsck on that disk to make sure
> > no other damage happened.
> Thank you. Reiserfsck said that all is ok. It's just that I have seen nothing
This is good.
> similar happening with other filesystems. I would prefer disappearing
> data to leaking data. Am I completely wrong, when I say that because of
> 'tail packing' in ReiserFS, it can leak information with more
> probability than, lets say ext2 or ufs or...? Will notails option give
No, tail packing should have no effect on leakign data.
Anyway tail packing is only takes effect for files less than 16K in size.
> me more secure FS? I have to assure company management, and myself, that this
notails will have no effect on that.
> incident happened not because I put ReiserFS on new server. It could
> have happened also with other filesystems :)
Indeed it seems that you've got either some metadata altered (block pointers)
or the block content swapped somehow, both of which could happen on any FS
with absolutely same results.
BTW, I just remembered that until you apply Chris' Mason "data logging" patches,
there is a certain window where system crash would lead to "deleted"
data appearing at the end of files that were appended before the crash.
(that's it, metadata is already updated and list newly allocated blocknumbers,
but old content od those blocks is still intact since crash prevented system
from putting new content in there), but since you've got other file's data
in the middle of file, this is not the case.
Bye,
Oleg
>
> Robert Tiismus
>
next prev parent reply other threads:[~2002-10-09 8:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-08 20:55 Catastrophe with mailboxes on ReiserFS Robert Tiismus
2002-10-09 5:42 ` Oleg Drokin
2002-10-09 8:06 ` Robert Tiismus
2002-10-09 8:18 ` Oleg Drokin [this message]
2002-10-09 14:02 ` Dieter Nützel
2002-10-09 14:09 ` Oleg Drokin
2002-10-09 14:20 ` Dieter Nützel
2002-10-09 14:31 ` Oleg Drokin
2002-10-09 14:23 ` Dieter Nützel
2002-10-09 14:32 ` Oleg Drokin
2002-10-09 15:15 ` Dieter Nützel
2002-10-09 15:19 ` Oleg Drokin
2002-10-09 15:26 ` Dieter Nützel
2002-10-09 14:10 ` Dieter Nützel
2002-10-09 23:07 ` Matthias Andree
2002-10-10 11:58 ` Newsmail
2002-10-10 11:25 ` Matthias Andree
2002-10-09 11:24 ` 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=20021009121811.A22948@namesys.com \
--to=green@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=robert@fi.tartu.ee \
/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.