Package: e2fsprogs Version: 1.39-1.1 Severity: wishlist File: /sbin/badblocks
I need to badblocks-scan a 400Gb drive. It's been running for 13 hours and it's nowhere near done. Now I would really like to reboot the machine. How difficult would it be to give badblocks an option to resume scans? I imagine that it outputs some status identifier if you ctrl-c it, and then you can pass that to an -r flag of sorts to make it start where it left off. I think the identifier could be simple, e.g. 2r,12345678,0 meaning that it's reading and verifying block 12345678 in the second iteration, and 0 bad blocks have been found. 2,3w,87654321,1 would mean one bad block has been found and we're at 87654321 during the first part of the third iteration of the second pass (pass 0 is implicit). Thoughts? -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.17-2-amd64 Locale: LANG=en_GB, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages e2fsprogs depends on: ii e2fslibs 1.39-1.1 ext2 filesystem libraries ii libblkid1 1.39-1.1 block device id library ii libc6 2.3.999.2-12 GNU C Library: Shared libraries ii libcomerr2 1.39-1.1 common error description library ii libss2 1.39-1.1 command-line interface parsing lib ii libuuid1 1.39-1.1 universally unique id library e2fsprogs recommends no packages. -- no debconf information -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems
signature.asc
Description: Digital signature (GPG/PGP)
