From: "Fao, Sean" <sean.fao@capitalgenomix.com>
To: Jakob Oestergaard <jakob@unthought.net>
Cc: Vladimir Saveliev <vs@namesys.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Filesystem/kernel bug?
Date: Wed, 29 Dec 2004 09:38:04 -0500 [thread overview]
Message-ID: <41D2C14C.6090201@capitalgenomix.com> (raw)
In-Reply-To: <20041229135510.GQ347@unthought.net>
Jakob Oestergaard wrote:
>I've seen this on ext3 and XFS as well.
>
>Both locally (ext3 and XFS) and NFS exported (XFS).
>
>About to try out 2.6.10 with CVS XFS and patches from the list - but
>somehow I doubt that the actual problem is in the filesystems.
>
Part of my reason for panic was that I recently had my Linux router kick
the bucket. I also used reiserfs on this system and *believe* it was
running a 2.6.8 kernel.
The strange thing about this system was that, at first glance, it
appeared to have a complete hard disk failure. However, when I rebooted
the computer, the system did indeed start to boot. When it came time to
mount the root file system, it became apparent that it had become
corrupt. I've been running Linux systems for years and this was the
first system that I ever experienced a corrupted file system on.
As a result of my success with file systems on Linux in the past, I've
been somewhat lazy when partitioning drives lately. I've been creating
100 MB boot, system_ram * 2 swap, and throwing everything else in the
root. I might have to go back to my old style to separate /, /home and
/usr onto separate file systems.
--
Sean
prev parent reply other threads:[~2004-12-29 14:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-27 15:50 Filesystem/kernel bug? Fao, Sean
2004-12-28 13:52 ` Fao, Sean
2004-12-28 16:27 ` Vladimir Saveliev
2004-12-29 12:54 ` Fao, Sean
2004-12-29 13:55 ` Jakob Oestergaard
2004-12-29 14:38 ` Fao, Sean [this message]
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=41D2C14C.6090201@capitalgenomix.com \
--to=sean.fao@capitalgenomix.com \
--cc=jakob@unthought.net \
--cc=linux-kernel@vger.kernel.org \
--cc=vs@namesys.com \
/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