To: linux-kernel@vger.kernel.org
From: mru@kth.se (=?iso-8859-1?q?M=E5ns_Rullg=E5rd?=)
Subject: Re: 2.6.1 + XFS wierdness
Date: Sat, 24 Jan 2004 11:03:25 +0100
Message-ID: <yw1xhdyl7jf6.fsf@ford.guide>
References: <8D2C6B0D-21C8-11B2-9DDD-000A958B60EE__36670.0378632688$1074934610@runbox.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: Gnus/5.1002 (Gnus v5.10.2) XEmacs/21.4 (Rational FORTRAN, linux)
Cancel-Lock: sha1:VckBSVnVcGsYMlCN/aymHqHC+QQ=
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1242
Lines: 26

Igor <ivi@runbox.com> writes:

> Ok, as advised I'm reporting what happened to my system:
> I run Kernel 2.6.1 with XFS on a laptop, I forgot to send it to "sleep"
> and battery died, so there was unclean unmount (This is, what I
> believe was the cause),
> at some point after I restarted my system many of the files couldn't
> be executed:
> "binary file can't be executed reported", However the system was
> functional and I could boot it.
> So I hexopened some of the problematic files and found that although
> the size of the file is maintained, there was no data, every byte was
> replaced by 0, I guess it was lucking reference on a hard drive or
> maybe something else. The reason I think the root of the problem is
> filesystem + kernel because the "corrupted" files have nothing in
> common, e.g:
> /usr/bin/file
> /etc/init.d/cron
> /usr/bin/lynx
> and that only happened when I updated kernel to 2.6.1

See http://oss.sgi.com/projects/xfs/faq.html#nulls

-- 
M?ns Rullg?rd
mru@kth.se

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/