It is silent for me too, I'd like to know how to put it verbose. 2009/1/23 Charly Ghislain <charlyghislain@gmail.com>

On Friday 23 January 2009 16:12:26 Ashish SHUKLA wrote:

...

Is there any switch for fsck (during startup) to be somewhat verbose like displaying the progress of filesystem check ?

It does for me, without changing anything... Im using ext3

On Fri, Jan 23, 2009 at 10:45, Ashish SHUKLA <wahjava.ml@gmail.com> wrote:

I'm also using ext3 and I'm talking about the file-system check which takes after every n days or n mounts during boot-up. It is not showing any status of file-system check. Are you getting any progress-bar during the file-system check ? If yes, what changes you made to get that.

Thanks -- Ashish SHUKLA

if [ -x /sbin/fsck ]; then stat_busy "Checking Filesystems" if /bin/grep -qw quiet /proc/cmdline; then /sbin/fsck -A -T -C -a -t $NETFS $FORCEFSCK >/dev/null 2>&1 else /sbin/fsck -A -T -C -a -t $NETFS $FORCEFSCK 2>/dev/null fi line 245..251 in /etc/rc.sysinit fsck is running with -C which means it will display progress bars as long as your fsck.* supports it. I know ext2 and 3 do, I'm not sure about the others. You need to check your /etc/fstab to see if you've turned off fs checks, and confirm you are actually using ext3. Also, man 8 fsck, vi /etc/rc.sysinit, and google.com // jeff

On Fri, Jan 23, 2009 at 2:24 PM, Ashish SHUKLA <wahjava.ml@gmail.com> wrote:

Jeff Mickey writes:

...

On Fri, Jan 23, 2009 at 10:45, Ashish SHUKLA <wahjava.ml@gmail.com> wrote:

...

I'm also using ext3 and I'm talking about the file-system check which takes after every n days or n mounts during boot-up. It is not showing any status of file-system check. Are you getting any progress-bar during the file-system check ? If yes, what changes you made to get that.

Thanks -- Ashish SHUKLA

...

if [ -x /sbin/fsck ]; then stat_busy "Checking Filesystems" if /bin/grep -qw quiet /proc/cmdline; then /sbin/fsck -A -T -C -a -t $NETFS $FORCEFSCK >/dev/null 2>&1 else /sbin/fsck -A -T -C -a -t $NETFS $FORCEFSCK 2>/dev/null fi

...

line 245..251 in /etc/rc.sysinit

...

fsck is running with -C which means it will display progress bars as long as your fsck.* supports it. I know ext2 and 3 do, I'm not sure about the others. You need to check your /etc/fstab to see if you've turned off fs checks, and confirm you are actually using ext3.

Thanks for the hint. I guess it is due to the 'quiet' option passed to the kernel during boot-up, which causes stdout and stderr to redirect to /dev/null. I'll verify it the next time I reboot.

Thanks :) -- Ashish SHUKLA

It is because of it, indeed. I was also puzzled by the fact that in some boxes there was progress status and other boxes wasn't. I think I will change the rc.sysinit to the old behaviour, because I don't want the kernel loading messages and want the fsck progress bars. :) -- ------------------------------------------- Denis A. Altoe Falqueto ------------------------------------------- Emo Philips - "I was sleeping the other night, alone, thanks to the exterminator."

you won't see the progress if you have 'quiet' in as kernel argument (see your boot loader config). to display the progress while quieting everything else, edit your /etc/rc.sysinit (Jeff Mickey posted the code part already).

On Fri, Jan 23, 2009 at 2:35 PM, Markus Heuser <mheuser@mi.fu-berlin.de> wrote:

Hi,

are you using the "quiet" parameter in GRUBs "kernel" line? This is what caused fsck to be silent in my case.

The problem is that I don't wan't the extremely verbose kerneloutputs when not using "quiet". Besides, it also slows down booting since writing so much text into framebuffer isn't fast at all.

So if there was a way to have both, the "quiet" parameter and a fsck progressbar that would be very neat.

Markus

I was looking into the initscripts git history and found the commit for that change made in 12/12/2005: http://projects.archlinux.org/?p=initscripts.git;a=blob;f=rc.sysinit;hb=675e... There is no information of bugreport or feature request about it, so should it be sane to open a feature request to remove this behaviour? Would anyone disagree? -- ------------------------------------------- Denis A. Altoe Falqueto ------------------------------------------- Robert Benchley - "Drawing on my fine command of the English language, I said nothing."

On Fri, Jan 23, 2009 at 6:09 PM, Markus Heuser <mheuser@mi.fu-berlin.de> wrote:

Hey Denis,

...

There is no information of bugreport or feature request about it, so should it be sane to open a feature request to remove this behaviour?

Well, that depends on whether the devs think it's "working as intended". Personally, I don't think that suppressing the progress bar does much sense, especially since it's not _that_ verbose. I mean, seeing a progress bar every 30 mounts/180 days can't be very annoying ;)

...

Would anyone disagree?

I would definitly second a feature request/bugreport.

Greetings, Markus

Hi, The feature request is http://bugs.archlinux.org/task/12928 -- ------------------------------------------- Denis A. Altoe Falqueto ------------------------------------------- Marilyn Monroe - "It's not true that I had nothing on. I had the radio on."