mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: tor@spacetec.no (Tor Arntsen)
To: linux-kernel@vger.kernel.org
Subject: Re: NULL characters in file on ReiserFS again.
Date: Thu, 7 Jun 2001 18:31:07 +0200	[thread overview]
Message-ID: <200106071631.SAA07241@pallas.spacetec.no> (raw)
In-Reply-To: <fa.kdp2rnv.1bma03f@ifi.uio.no>
In-Reply-To: <fa.kdp2rnv.1bma03f@ifi.uio.no>

On Thu, May 31, 2001 at 09:57:51AM -0700, Hans Reiser wrote:
>Andrej Borsenkow 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.

Exactly the same thing happens on XFS filesystems on IRIX 6.5.
We had a bunch of Origin systems that crashed every so often because
of some PCI bus problems, and every time this happened every file
on the system that had been updated the last seconds before the
crash would be full of, or almost full of ^@.  Needless to say
this created havoc with CVS repositories and also checked-out
trees, since the CVS/Entries files would end up modified.

I first noticed this when my setiathome status files were empty
after the restarts.. *every* time.  I had to install a cron job 
that copied the status file every two minutes or so, the slightly
older copy would be okay so I could just copy it back after the
restart.

That was a nuisance, but when the CVS systems got wrecked it became
a little worse.  Obviously we have backups, but the problem was that
you wouldn't necessarily notice right away that anything was screwed.

Hopefully SGI will fix it, or maybe they have fixed it already -- 
I don't know.  I'm running 6.5.8 which isn't the latest (IRIX is
at 6.5.11 or 6.5.12 now I think), and it certainly wasn't fixed there.
If not, then XFS will never run on my Linux boxes, and certainly
not on the big Linux server that now holds our CVS repositories
instead of the SGI Origin system that we originally used :-)

In another posting Stephen Tweedie writes:
>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.

That's good news.

-Tor

       reply	other threads:[~2001-06-07 16:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.kdp2rnv.1bma03f@ifi.uio.no>
2001-06-07 16:31 ` Tor Arntsen [this message]
2001-05-31 11:33 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

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=200106071631.SAA07241@pallas.spacetec.no \
    --to=tor@spacetec.no \
    --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

all inboxes | Powered by JetHome®