Greetings,
I'm running CentOS 5.x on one ancient but reasonably reliable machine: root@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@leeloo ~> cat /proc/cpu cat: /proc/cpu: No such file or directory root@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@brama.com
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
On Tue, 9 Apr 2013, m.roth@5-cent.us wrote:
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.)
Yes, I see. Thanks; and it is buried in the man page.
mark
MP pyz@brama.com
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