From: ebiederm@xmission.com (Eric W. Biederman)
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: Hans Reiser <reiser@namesys.com>,
Andrej Borsenkow <Andrej.Borsenkow@mow.siemens.ru>,
linux-kernel@vger.kernel.org
Subject: Re: NULL characters in file on ReiserFS again.
Date: 07 Jun 2001 11:04:59 -0600 [thread overview]
Message-ID: <m1d78g43wk.fsf@frodo.biederman.org> (raw)
In-Reply-To: <000201c0e9c5$7643d540$21c9ca95@mow.siemens.ru> <3B16780F.D5FF04D8@namesys.com> <20010606172209.A3362@redhat.com>
In-Reply-To: <20010606172209.A3362@redhat.com>
"Stephen C. Tweedie" <sct@redhat.com> writes:
> Hi,
>
> On Thu, May 31, 2001 at 09:57:51AM -0700, Hans Reiser wrote:
>
> > > /etc/hosts (or anywhere). As a tesult, startx hung starting X server; it was
>
> > > not possible to switch to alpha console or kill X server. I pressed reset
> > > and after reboot looked into /var/log/XFree86*log - and there were a bunch
> > > of ^@ there.
>
> > this is the nature of metadata journaling filesystems.
>
> Umm, no, it isn't. Ext3 would never allow that to happen in ordered
> metadata-journaling mode, and Chris Mason is already working to remove
> that window in reiserfs. It is by no means a necessary consequence of
> doing metadata-only journaling.
Hans seemed to be refering to the fact that fsck.reiser returned
without errors on the partition being looked at. Which is the nature
of metadata journalling. The filesystem doesn't get corrupted though
the files might.
Eric
next prev parent reply other threads:[~2001-06-07 17:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-31 11:33 NULL characters in file on ReiserFS again Andrej Borsenkow
2001-05-31 13:56 ` Chris Mason
2001-05-31 16:57 ` Hans Reiser
2001-06-06 16:22 ` Stephen C. Tweedie
2001-06-07 17:04 ` Eric W. Biederman [this message]
[not found] <fa.kdp2rnv.1bma03f@ifi.uio.no>
2001-06-07 16:31 ` Tor Arntsen
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=m1d78g43wk.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=Andrej.Borsenkow@mow.siemens.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@namesys.com \
--cc=sct@redhat.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