From: Bill Davidsen <davidsen@tmr.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux Kernel 2.6.6 IDE shutdown problems.
Date: Mon, 17 May 2004 18:25:51 -0400 [thread overview]
Message-ID: <c8bdqv$lib$1@gatekeeper.tmr.com> (raw)
In-Reply-To: <200405151506.20765.bzolnier@elka.pw.edu.pl>
Bartlomiej Zolnierkiewicz wrote:
> On Saturday 15 of May 2004 14:20, Justin Piszcz wrote:
>
>>The problem is the 2.6.6 kernel muxed my drive and when it fscked upon
>>reboot it deleted /etc/mtab and lilo.conf!
>
>
> What fs are you using?
>
>
>>Luckily I restored them from a backup and now run 2.6.5 and it is working
>>fine.
>>
>>Linux 2.6.6 is a nightmare.
>>
>>I am looking into the benchmark problem with 2.6.6 now.
>>
>>--- In linux-kernel@yahoogroups.com, "Justin Piszcz" <jpiszcz@h...> wrote:
>>
>>>Now whenever I reboot it says input/output errors when it tries to mount
>>>the drive? I will look into this further.
>
>
> This errors are HARMLESS and CAN'T corrupt your data.
> Please see http://bugme.osdl.org/show_bug.cgi?id=2672 for description+fix.
I would think that if the drive didn't properly flush cache on shutdown
that it might cause corruption. Feel free to tell me no drive would
bahave like that ;-)
--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
next prev parent reply other threads:[~2004-05-17 22:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-15 12:20 Linux Kernel 2.6.6 IDE shutdown problems Justin Piszcz
2004-05-15 13:06 ` Bartlomiej Zolnierkiewicz
2004-05-17 22:25 ` Bill Davidsen [this message]
2004-05-24 2:41 ` Tom Vier
2004-05-24 3:09 ` Daniel Pittman
2004-05-24 17:16 ` Eric D. Mudama
2004-05-25 9:05 ` Giuliano Pochini
2004-05-25 15:03 ` Bartlomiej Zolnierkiewicz
2004-05-26 10:21 ` Ian Stirling
2004-05-25 17:02 ` Eric D. Mudama
-- strict thread matches above, loose matches on Subject: below --
2004-05-15 14:59 Justin Piszcz
2004-05-15 12:02 Justin Piszcz
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='c8bdqv$lib$1@gatekeeper.tmr.com' \
--to=davidsen@tmr.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.