mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chiaki <ishikawa@yk.rim.or.jp>
To: Bernd Eckenfels <ecki-news2004-05@lina.inka.de>
Cc: linux-kernel@vger.kernel.org, ishikawa@yk.rim.or.jp
Subject: Re: FSCK message suppressed during booting? (2.6.9-rc2)
Date: Fri, 01 Oct 2004 00:51:08 +0900	[thread overview]
Message-ID: <415C2B6C.6050401@yk.rim.or.jp> (raw)
In-Reply-To: <E1CCtxn-00075V-00@calista.eckenfels.6bone.ka-ip.net>

Bernd Eckenfels wrote:
> In article <415B5034.6060809@yk.rim.or.jp> you wrote:
> 
>>That is, under previous 2.4.xx kernel, I would have gotten
>>"The disk was not unmounted cleanly. Running fsck." or
>>some such message and fsck printed its
>>progress bar using ASCII characters.
> 
> 
> Well, this is not a kernel function, your Distribution is calling fsck in
> the bootup scripts, and fsck is calling the filesystem specific
> implementation and this is checking if fsck is needed.
> 
> If you do not get this messages anymore contact your linux distribution
> provider.
> 
> 

Thank you for the comment.

Well, I have installed 2.6.9-rc2 on my own after having used
Debian with my own updated kernel 2.4.2x series for a few years now.
I certainly upgraded moduleutil and other packages to run
2.6.9-rc2, but have not specifically updated fsck.
(I DID ran apt-get -u update and apt-get -u upgrade to pick up
the latest packages a week ago or so.).

Agreed that the starting fsck under stock Debian scheme
may depend on 2.4.xx features which may not be available
on 2.6.yy series kernel. I will get in contact with fsck
package (or boot script) maintainer to see
if we can improve this.

 >Do you habe maybe a journalling filesystem? Or do you have set some 
flags to
 > force the skip of fsck (/fastboot)
 >

Well, I am running 2.6.9-rc2 from loadlin as follows.

loadlin 269rc2 root=/dev/sda6 ro vga=3 scsihosts=sym53c8xx:tmscsim

I noticed the fsck message lines were missing on the reboot after
a hard-hung forced me to hit reset button in the end.
The message lines were missing, but it seems that fsck
certainly was running invisibly. Thus the
boot sequence halted as if the computer got hung again
until fsck finished and bootting continued. This was very
annoying.



-- 
int main(void){int j=2003;/*(c)2003 cishikawa. */
char t[] ="<CI> @abcdefghijklmnopqrstuvwxyz.,\n\"";
char *i ="g>qtCIuqivb,gCwe\np@.ietCIuqi\"tqkvv is>dnamz";
while(*i)((j+=strchr(t,*i++)-(int)t),(j%=sizeof t-1),
(putchar(t[j])));return 0;}/* under GPL */

  reply	other threads:[~2004-09-30 15:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-30  0:15 Chiaki
2004-09-30  5:58 ` Bernd Eckenfels
2004-09-30 15:51   ` Chiaki [this message]
2004-09-30 20:36     ` Chiaki
2004-09-30 22:11       ` Chiaki
2004-10-02 20:28         ` Chiaki

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=415C2B6C.6050401@yk.rim.or.jp \
    --to=ishikawa@yk.rim.or.jp \
    --cc=ecki-news2004-05@lina.inka.de \
    --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®