Max Pyziur
2013-Apr-09 18:41 UTC
[CentOS] fsck - anyway to increase verbosity to show point in process
Greetings, I'm running CentOS 5.x on one ancient but reasonably reliable machine: root at leeloo ~> uname -a Linux leeloo 2.6.18-308.24.1.el5 #1 SMP Tue Dec 4 17:42:30 EST 2012 i686 i686 i386 GNU/Linux root at leeloo ~> cat /proc/cpu cat: /proc/cpu: No such file or directory root at leeloo ~> cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 11 model name : Intel(R) Pentium(R) III CPU family 1400MHz .. I am running some fsck's on some of the larger drives (750GB and 2TB) that are used for backups. There is a verbosity flag (-V); but because of the size of the drives along with slowness of the processor, the process is taking a long time. And there is no indication how much of the process has been completed (nothing like a %tage indicator), at least the way that I am running it. Is this expected, or is there some way of amping up the feedback? Much thanks, Max Pyziur pyz at brama.com
m.roth at 5-cent.us
2013-Apr-09 18:47 UTC
[CentOS] fsck - anyway to increase verbosity to show point in process
Max Pyziur wrote:> > Greetings, > > I'm running CentOS 5.x on one ancient but reasonably reliable machine:<snip>> I am running some fsck's on some of the larger drives (750GB and 2TB) that > are used for backups. There is a verbosity flag (-V); but because of the > size of the drives along with slowness of the processor, the process is > taking a long time. > > And there is no indication how much of the process has been completed > (nothing like a %tage indicator), at least the way that I am running it. > > Is this expected, or is there some way of amping up the feedback?-C gives you nice warm fuzzies, something for you to watch as you fall asleep (it takes a *long* bloody while for big drives, he says from experience.) mark
Santi Saez
2013-Apr-10 10:03 UTC
[CentOS] fsck - anyway to increase verbosity to show point in process
El 09/04/13 20:41, Max Pyziur escribi?:> And there is no indication how much of the process has been completed > (nothing like a %tage indicator), at least the way that I am running it.Tip: if you have already launched "fsck" you can recover the progress bar sending SIGUSR1 signal, see this behavior in action: http://www.youtube.com/watch?v=cS4eztFtS0U SantiSaez http://powerstack.org