badblocks from e2fsprogs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



[ Please CC me I am not subscribed to this ML ]

Hi,

I am here on Debian/testing AMD64 and have e2fsprogs version 1.46.1-1
from Debian/unstable.

Just for the sake of completeness:
Here I use a selfmade Linux v5.12-rc1 (and pre-git as of yesterday).

To check the health of my disk I used badblocks the first time.
( All partitions are ExtFS-formatted on /dev/sdc. )

root@iniza:~/DISK-HEALTH# LC_ALL=C badblocks -v -p 1 -s /dev/sdc -o
badblocks-v-p-1-s_dev-sdc_$(uname -r).txt
Checking blocks 0 to 976762583
Checking for bad blocks (read-only test): done
Pass completed, 0 bad blocks found. (0/0/0 errors)

root@iniza:~/DISK-HEALTH# ll
badblocks-v-p-1-s_dev-sdc_5.11.0-11646.1-amd64-clang13-cfi.txt
-rw-r--r-- 1 root root 0 28. Feb 19:33
badblocks-v-p-1-s_dev-sdc_5.11.0-11646.1-amd64-clang13-cfi.txt

Unfortunately, the output-file is empty.
Do I miss something (order of options for example)?

The whole single-pass badblocks run took approx. 3 hours - last I
looked 50% was 01:26 [hh:mm].
On stdout (and in output-file) - no summary of the total-time.

Is that possible to have:

Pass completed, 0 bad blocks found. (0/0/0 errors) + <total-time_of_run>

Thanks in advance.

Regards,
- Sedat -



[Index of Archives]     [Reiser Filesystem Development]     [Ceph FS]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite National Park]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]     [Linux Media]

  Powered by Linux