lkml.org 
[lkml]   [2004]   [Sep]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: FSCK message suppressed during booting? (2.6.9-rc2)
    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 */
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2005-03-22 14:06    [W:0.023 / U:90.748 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site