>> On Thu, 5 Apr 2007, Justin Piszcz wrote:
quoted text
>> 
>>> http://www.ussg.iu.edu/hypermail/linux/kernel/0701.3/0315.html
>>>

Here is the badblocks output:

p34:~# /usr/bin/time badblocks -b 512 -s -v -w /dev/sdl
Checking for bad blocks in read-write mode
quoted text
>From block 0 to 293046768
Testing with pattern 0xaa: done
Reading and comparing: done
Testing with pattern 0x55: done
Reading and comparing: done
Testing with pattern 0xff: done
Reading and comparing: done
Testing with pattern 0x00: done
Reading and comparing: done
Pass completed, 0 bad blocks found.
1929.06user 467.89system 4:36:23elapsed 14%CPU (0avgtext+0avgdata 
0maxresident)k
0inputs+0outputs (1major+257minor)pagefaults 0swaps
p34:~#

Nothing wrong with the drive.  This problem concerns me greatly as I am 
not sure what I can do to fix this issue, how can I make sure it does not 
happen again?

Justin.
-
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/