From: "Damian Wrobel" <dwrobel@ertel.com.pl>
To: <linux-kernel@vger.kernel.org>
Subject: RE: Compaq Alpha DS10 - Kernel 2.4.18
Date: Tue, 9 Apr 2002 13:25:56 +0200 [thread overview]
Message-ID: <CDEOINGOFOFAOEOLKDEDOENACAAA.dwrobel@ertel.com.pl> (raw)
In-Reply-To: <000d01c1dfb0$0da74a30$010b10ac@sbp.uptime.at>
>-----Original Message-----
>From: linux-kernel-owner@vger.kernel.org
>[mailto:linux-kernel-owner@vger.kernel.org]On Behalf Of Oliver Pitzeier
>Sent: Tuesday, April 09, 2002 12:20 PM
>To: linux-kernel@vger.kernel.org
>Subject: Compaq Alpha DS10 - Kernel 2.4.18
>
>
>Hi all!
>
>I've got a really big problem with kernel 2.4.18 and 2.4.17 on
>an Alpha.
>
>I can compile, install and boot the kernel on my Alpha.
>But if I shutdown the machine without shutting down the
>system - I know this is crazy, but sometimes this happens...
>
>So if I'm this mad and restart the machine afterwards, I get
>a lot of fsck errors 'til the system give up and tell's me,
>that I have to check it with fsck myself.
>
>OK, I did so... fsck -y /dev/sda1 -> Works perfectly. After
>fsck has corrected more than 1000 errors I'm able to
>reboot the machine.
>
>And than: MY SYSTEM IS NO LONGER BOOTABLE. It's totally
>currupted...
>
>I never saw the filesystem curruption bug on Intel, but it
>sounds like this.
>
>Is this the same bug that was on Intel?
>Have I done something wrong?
>
>Are there any alpha-users in this list? :o))))
>
>Greetz, I look forward for answers,
> Oliver
>
>
>-
Think about one of journaling filesystems: ext3, reiserfs, xfs, jfs...
Regards,
Damian Wrobel
next prev parent reply other threads:[~2002-04-09 11:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-09 2:10 syscals mark manning
2002-04-09 10:06 ` syscals Frank Schaefer
2002-04-09 10:19 ` Compaq Alpha DS10 - Kernel 2.4.18 Oliver Pitzeier
2002-04-09 11:25 ` Damian Wrobel [this message]
2002-04-09 12:16 ` dr john halewood
2002-04-09 15:09 ` syscals Randy.Dunlap
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=CDEOINGOFOFAOEOLKDEDOENACAAA.dwrobel@ertel.com.pl \
--to=dwrobel@ertel.com.pl \
--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®