Received: (from majordomo@localhost)
	by oss.sgi.com (8.11.2/8.11.3) id f6ABS7u09502
	for linux-xfs-outgoing; Tue, 10 Jul 2001 04:28:07 -0700
Received: from piro.kabuki.sfarc.net (postfix@[203.36.158.121])
	by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6ABS4V09498
	for <linux-xfs@oss.sgi.com>; Tue, 10 Jul 2001 04:28:05 -0700
Received: by piro.kabuki.sfarc.net (Postfix, from userid 1000)
	id B667814AC961; Tue, 10 Jul 2001 21:28:28 +1000 (EST)
Date: Tue, 10 Jul 2001 21:28:28 +1000
From: Daniel Stone <daniel@sfarc.net>
To: Steve Lord <lord@sgi.com>
Cc: Scott Jaderholm <scott@jaderholm.com>, linux-xfs@oss.sgi.com,
   walters@cis.ohio-state.edu
Subject: Re: XFS and Emacs don't play nice
Message-ID: <20010710212828.B10357@kabuki.sfarc.net>
Mail-Followup-To: Steve Lord <lord@sgi.com>,
	Scott Jaderholm <scott@jaderholm.com>, linux-xfs@oss.sgi.com,
	walters@cis.ohio-state.edu
References: <200107100917.f6A9HIR14760@jen.americas.sgi.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200107100917.f6A9HIR14760@jen.americas.sgi.com>
User-Agent: Mutt/1.3.18i
Organisation: Sadly lacking
Sender: owner-linux-xfs@oss.sgi.com
Precedence: bulk

On Tue, Jul 10, 2001 at 04:17:17AM -0500, Steve Lord wrote:
> As for what is happening to your file. This is not corruption per se, the
> updated inode size made it out to disk, but the data did not. If you do
> an xfs_bmap you will probably find there are are no extents in the file.
> (xfs_bmap .emacs). It is also not in in kernel buffer corruption problem,
> it is because the buffers were not written to disk before the crash, but
> the inode size was written in a transaction.
> 
> Please try a later kernel as I have not seen reports like this in a
> while.

Let me add my voice - I haven't posted this as yet, because I've been trying
to track it down as to where it started, but I'm getting null-byte
corruption through entire files (my entire /etc/mailcap got replaced with
null bytes, as did the postinst's for a few packages). I'm tracking CVS, and
it appears to only have happened with the -pre2 sync, everything previous
seemed to work OK (though admittedly I haven't tried -pre1, and that was
most likely the culprit, being a large -ac sync). The affected partitions
are on IDE drives, not a VIA chipset or anything.

:) d

-- 
Daniel Stone						     <daniel@sfarc.net>
<Nuke> "can NE1 help me aim nuclear weaponz????? /MSG ME!!"