On Sat, Jan 12, 2008 at 11:14:13AM -0800, Towncat wrote: > On jan. 12, 19:20, Michael Shuler <[EMAIL PROTECTED]> wrote: > > On 01/12/2008 11:40 AM, Towncat wrote: > > > > > /sbin/badblocks -c 10240 -w -t random -v /dev/sda2 > > > > > where sda2 is a 320 gb partition. The process has been running for > > > approx 18 hours and is just over three thirds. Is this really supposed > > > to be so slow, or is there something wrong? The machine is a Core Duo > > > 1,6, 2GB memory. > > > > Yes, and no. badblocks -w is a full write-mode check - you could do a > > default read-only check, which would certainly be faster, but it all > > depends on how thorough you would like to be - you chose the most > > thorough check, so it will take a while, yeah. Just over 3/3's (= 1/1 = > > done)? ;) > > ? > > Sorry, three quarters... :) > > I thought I'd be thorough, since I can only do this now when it's > still empty.
Why? e2fsck -c -c will do a read/write/read. OK, not random, but does random matter or are you trying to wipe the drive at the same time? Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
