From: mru@kth.se (Måns Rullgård)
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.1 + XFS wierdness
Date: Sat, 24 Jan 2004 11:03:25 +0100 [thread overview]
Message-ID: <yw1xhdyl7jf6.fsf@ford.guide> (raw)
In-Reply-To: <8D2C6B0D-21C8-11B2-9DDD-000A958B60EE__36670.0378632688$1074934610@runbox.com>
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
next parent reply other threads:[~2004-01-24 10:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8D2C6B0D-21C8-11B2-9DDD-000A958B60EE__36670.0378632688$1074934610@runbox.com>
2004-01-24 10:03 ` Måns Rullgård [this message]
[not found] <8D2C6B0D-21C8-11B2-9DDD-000A958B60EE__36670.0378632688$1074934610@runbox.com.suse.lists.linux.kernel>
[not found] ` <yw1xhdyl7jf6.fsf@ford.guide.suse.lists.linux.kernel>
2004-01-24 15:45 ` Andi Kleen
1970-01-06 1:01 Igor
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=yw1xhdyl7jf6.fsf@ford.guide \
--to=mru@kth.se \
--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®