How do you get e2fsck to show progress information?

Solution 1:

The -C flag will display a progress bar. Performance differences depending on how fsck is called.

And very cool, if e2fsck is already running, you can send a USR1 signal for it to start displaying a progress bar. USR2 to stop. Example:

killall -USR1 e2fsck

From FSCK(8):

   -C     Display completion/progress bars for those filesys-
          tems  checkers (currently only for ext2) which sup-
          port them.   Fsck will manage the filesystem check-
          ers  so  that  only  one  of  them  will  display a
          progress bar at a time.

From E2FSCK(8):

   -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 pro-
          grams  which  are  running  e2fsck.   If  the  file
          descriptor specified is 0, e2fsck will print a com-
          pletion bar as it goes about  its  business.   This
          requires  that e2fsck is running on a video console
          or terminal.

Solution 2:

from man page for version 1.41

   -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.

so I guess the answer is

e2fsck -C 0 /dev/sda1

---

Solution 3:

ps -ef | grep fsck

  5079  5007 47 00:55 pts/1    00:08:25 /sbin/fsck.ext3 -yv /dev/hda2

with the process ID,

kill -USR1 5079

---

Solution 4:

Why?

BSD Systems and their descendants have SIGINFO signal. It makes programs to output their current status to the console. A lot of basic BSD tools know about this signal and support it. You can send this signal to a current process using Ctrl+T.

SysV systems have no such signal and no Ctrl+T too. Some of the Linux tools support SIGUSR1 instead. I know only about "dd" and "e2fsck" but there can be more. There is no Ctrl+? shortcut to send it, so you have to do it manually by using "kill -USR1" on the pid of the process.

Most other programs will react to SIGUSR1 the same way they react to SIGTERM (exit) so don't send this signal unless you know that it's supported.