How to Combine a badblock Scan With a Time-To-Run Calculation?

[DrCR]

Learned about badblock from this post, and this post mentioned the importance of noting the time-to-complete.

So how would I sequentially run the following commands with a way of measuring how long it took to complete each command:
nohup badblocks -v /dev/sdx &
(time-to-complete printed to screen)
nohup badblocks -c 10240 -s -w -t random -v /dev/sdx &
(time-to-complete printed to screen)

Thanks for helping a scripting noob!
DrCR

[Rubberman]

Example:

nohup /usr/bin/time --portability badblocks -v /dev/sdx &

That will give you an output like this (in nohup.out):

... output from badblocks command ...
real N.NN
user N.NN
sys N.NN

where N.NN is the time in seconds.

[DrCR]

Awesomeness, thanks. I'll give it a go when I get in the replacement drive (it had badblock errors). Thanks again.

[DrCR]

Example:

nohup /usr/bin/time --portability badblocks -v /dev/sdx &

Hum, that didn't work for me, at least not for a different purpose I tried to apply it to below.

server:~# nohup /usr/bin/time --portability mkfs.jfs -c /dev/sda1 &
[1] 24843
server:~# nohup: ignoring input and appending output to `nohup.out'
nohup: cannot run command `/usr/bin/time': No such file or directory

Is the --portability part for nohup or time? I tried to search the man files, but I don't know how to access the additional documentation e.g. time(1) instead of time(7).

What am I doing wrong? Thanks

[Rubberman]

Hum, that didn't work for me, at least not for a different purpose I tried to apply it to below.

server:~# nohup /usr/bin/time --portability mkfs.jfs -c /dev/sda1 &
[1] 24843
server:~# nohup: ignoring input and appending output to `nohup.out'
nohup: cannot run command `/usr/bin/time': No such file or directory

Is the --portability part for nohup or time? I tried to search the man files, but I don't know how to access the additional documentation e.g. time(1) instead of time(7).

What am I doing wrong? Thanks

Most systems have 2 'time' programs - one builtin to the shell, and the other an executable. Usually it is found as /usr/bin/time, but on your system it might be elsewhere, such as in /bin. Find it and use that path instead of /usr/bin/time as I did in my example. BTW, which linux distribution+version and kernel version are you running?

The --portability option is applied to the time command.