Istvan Gabor said the following on 02/23/2010 01:38 PM:

In my openSUSE 11.2 the fsck progress bar is not shown even if I boot the system in text mode. How can I enable it?

What file system are you using? Not all display the progress bar. ReiserFS for example. What settings do you have on the FS? IS it set to fsck on every boot? Every 25th boot? Every 90 days? What? Are you running a laptop on battery? See man e2fsck.conf and man tune2fs

From man tune2fs

-c max-mount-counts Adjust the number of mounts after which the filesystem will be checked by e2fsck(8). If max-mount-counts is 0 or -1, the number of times the filesystem is mounted will be disregarded by e2fsck(8) and the kernel. Staggering the mount-counts at which filesystems are forcibly checked will avoid all filesystems being checked at one time when using journaled filesystems. ... -C mount-count Set the number of times the filesystem has been mounted. If set to a greater value than the max-mount-counts parameter set by the -c option, e2fsck(8) will check the filesystem at the next reboot. Oh, and Charles, I pasted those in using my mouse's scroll wheel -- "Of all tyrannies a tyranny sincerely exercised for the good of its victims may be the most oppressive. It may be better to live under robber barons than under omnipotent moral busybodies, the robber baron's cruelty may sometimes sleep, his cupidity may at some point be satiated; but those who torment us for own good will torment us without end, for they do so with the approval of their own conscience." - C.S. Lewis, _God in the Dock_ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Istvan Gabor said the following on 02/23/2010 03:10 PM:

The question remains: how can I enable fsck progress bar at system boot?

I'm sorry you don't see it. If you have an normal install, then fsck runs and finds it doesn't need to, so you boot quickly. I pointed you to the man pages so you could he how to set fsck to force a full scan on, or example, every boot, every other boot, every ninth boot, every third day .. whatever. Just running fsck, which should be in /etc/init.d/boot.localfs, which should get run at boot time, is not enough. If there was a clean shutdown and no other reason to force a full scan, there won't be one. Most of us consider this a good thing. A clean shutdown means less chance of file system corruption on the next boot, and a fast boot means the system is up and useful sooner. On the whole the old UNIX philosophy was that if nothing untoward happens than ... nothing happens. Unlike VMS and other systems you don't get an NOTICE_ALL_OK message on the completion of command or a NOTHING_FOUND output from grep or find being pushed down the pipeline. If you want a full scan, the go back and read the man pages again and think how you would set a file system to run a full scan on every other boot. Then every boot. I'm sorry you don't see it. However if you're system somehow doesn't have the boot.localfs - I can't imagine how - then I apologise. So, check /var/log/boot.msg Somewhere it should have something like ... Waiting for device /dev/sda1 to appear: ok fsck 1.41.1 (01-Sep-2008) [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a -C0 /dev/sda1 ROOT: clean, 10969/140256 files, 91375/560259 blocks fsck succeeded. Mounting root device read-write. Mounting root /dev/disk/sda1 mount -o rw,noacl -t ext3 /dev/sda1 /root And there you have it. fsck runs. it sees a clean shutdown and just mounts. no need for scan. So, as the manual page made clear, if you want a scan on every boot, or every other boot, or every Nth boot or every Mth day YOU HAVE TO SET IT. Otherwise a clean shutdown means a scanless and fast boot. Personally I like clean shutdowns and I like fast boots. I can imagine though, some people don't. -- Without friends no one would choose to live, though he had all other goods. Aristotle (384 BC - 322 BC), Nichomachean Ethics -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Tuesday 23 February 2010 03:22:39 pm Istvan Gabor wrote:

I do know that at every Nth boot or after a given time the filesystem is checked (I mena full scanned) by fsck, and this number or time can be set. But my problem is different: When fsck does a complete scan it does not show a "progress bar". In my earlier system when fsck ran at boot and did a full scan, a line containing something like this was shown: ################## (50 %) or maybe ===================(50 %)

(I can not recall exactly).

So I knew the progress of the full scan. In my openSUSE 11.2 system there is not such "progress bar/line". Only an empty line below the line which informs that a full scan was started. Because of this I don't see the progress of the full scan.

i don't have an answer but i'll sure watch this thread for one -- i've been missing that progress bar ever since i upgraded i know i can force an fsck by (as root) touching /forcefsck then rebooting, and i *think* there is a commandline option to show the progress bar (the man page mentions -C in this context), but i haven't yet been able to combine those two pieces of information into a visible progress bar -- when i touch /forcefsck there's nowhere to put a -C sc -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Patrick Shanahan said the following on 02/23/2010 06:12 PM:

* sc [02-23-10 17:58]:

...

i know i can force an fsck by (as root) touching /forcefsck then rebooting, and i *think* there is a commandline option to show the progress bar (the man page mentions -C in this context), but i haven't yet been able to combine those two pieces of information into a visible progress bar -- when i touch /forcefsck there's nowhere to put a -C

and you would not consider: fsck /dev/<dev-name> fsck -C /dev/<dev-name>

and I have not to my knowledge ever used "-C" but do see the "progress" bar.

Well look what # grep -e -C /etc/init.d/boot.d/* returns! Well that's interesting on my 11.1. I don't know what it would be on 11.2 -- Whenever men take the law into their own hands, the loser is the law. And when the law loses, freedom languishes. -- JFK -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

* Istvan Gabor [02-23-10 15:15]:

According to man e2fsck I should have an /etc/e2fsck.conf file but I don't. Can this be the problem?

I do not, either. But I see the "progress bar". -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Istvan Gabor said the following on 02/23/2010 03:10 PM:

I looked through the abovementioned man pages but could not find anything related to the progress bar. Have I overlooked it maybe?

Probably. You should have seen -C fd This option causes e2fsck to write completion information to the specified file descriptor so that the progress of the filesystem check can be monitored. This option is typically used by programs which are running e2fsck. If the file descriptor number is negative, then absolute value of the file descriptor will be used, and the progress information will be suppressed initially. It can later be enabled by sending the e2fsck process a SIGUSR1 signal. *** If the file descriptor specified is 0, e2fsck will print a *** completion bar as it goes about its business. This requires *** that e2fsck is running on a video console or terminal.

...

Oh, and Charles, I pasted those in using my mouse's scroll wheel

? I don't understand this one.

That's for Charles Obler who thinks you can't paste using KDE4. You can and I did.

The question remains: how can I enable fsck progress bar at system boot?

Since that's done in /etc/init.d/boot.d/ ... oh maybe there's a systemsetting that turns it on or off. Do a case independent recursive grep under /etc for fsck and see what you uncover. OBTW: what's in initrd and your boot command line? Those get handed to the boot scripts an can affect this -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Istvan Gabor said the following on 02/23/2010 07:01 PM:

It seems my system thinks that it uses a serial console, and therefore does not show the progress bar. Why does it think that, and how could I change it?

Well if you're happy hacking boot.rootfsck, just take the test out :-) After all, you don't seem interested in fastboot and seem to want to see the progress bar all the time. But if you mean why does it think you're using a serial console rather than the PC's own console ... we'll need to know more about your hardware setup to answer that. -- A nation or civilization that continues to produce soft-minded men purchases its own spiritual death on an installment plan. --Martin Luther King, Jr. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Tuesday 23 February 2010 06:01:42 pm Istvan Gabor wrote:

For making sure that this is the culprit I have changed FSCK_OPTS="$FSCK_OPTS -V" to FSCK_OPTS="$FSCK_OPTS -C" in my /etc/init.d/boot.localfs file, set one of my partitions mount-count number above the limit and rebooted. After this fsck initiated a full scan on the given partition at bootup and the progress bar was shown.

i took a slightly different approach i like to force fsck before the 60 days expires (if i don't it will invariably expire on a morning i want to get something done) so i changed FSCK_OPTS="$FSCK_OPTS -f" to FSCK_OPTS="$FSCK_OPTS -f -C" under if test -f /forcefsck -o "$DO_FORCEFSCK" = "yes" ; then in both of /etc/init.d/boot.d/K04boot.localfs /etc/init.d/boot.d/K06boot.rootfsck which through the magic of symbolic links also changed it for me in /etc/init.d/boot.d/S03boot.rootfsck /etc/init.d/boot.d/S11boot.localfx after this i touched /forcefsck, rebooted, and the progress bar showed for me too hopefully i did a sufficiently good job of documenting this change for myself so i can redo it after my next upgrade sc -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org