public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <mason@suse.com>
To: Andrej Borsenkow <Andrej.Borsenkow@mow.siemens.ru>,
	linux-kernel@vger.kernel.org
Subject: Re: NULL characters in file on ReiserFS again.
Date: Thu, 31 May 2001 09:56:53 -0400	[thread overview]
Message-ID: <874280000.991317413@tiny> (raw)
In-Reply-To: <000201c0e9c5$7643d540$21c9ca95@mow.siemens.ru>



On Thursday, May 31, 2001 03:33:06 PM +0400 Andrej Borsenkow
<Andrej.Borsenkow@mow.siemens.ru> wrote:

> This happened to me yesterday on kernel-2.4.4-6mdk (Mandrake cooker, based
> on 2.4.4-ac14), single reiser root filesystem, mounted with default
> options. Hardware - ASUS CUSL2 (i815e chipset), Fujitsu UDMA-4 drive.
> 
> I tried to change hostname and did not have the corresponding entry in
> /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.
> 

There are two ways to get nulls in log files.  reiserfs bugs, and a crash
before data blocks are flushed to disk.  You've probably hit the second.
Reiserfs only logs metadata, so it is possible for newly allocated data
blocks to have null bytes after a crash.

Patches are in progress to flush new data blocks before transaction commit.
I'm about to send out the first building block for this...

-chris



  reply	other threads:[~2001-05-31 14:07 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 [this message]
2001-05-31 16:57 ` Hans Reiser
2001-06-06 16:22   ` Stephen C. Tweedie
2001-06-07 17:04     ` Eric W. Biederman
     [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=874280000.991317413@tiny \
    --to=mason@suse.com \
    --cc=Andrej.Borsenkow@mow.siemens.ru \
    --cc=linux-kernel@vger.kernel.org \
    /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