Package: flashbench
Version: 62-1+b1

I tried the following commands on a 2GB usbstick:

flashbench /dev/disk/by-label/usbstklb 
flashbench -f /dev/disk/by-label/usbstklb 
flashbench -O /dev/disk/by-label/usbstklb 

all of which should have been harmless, but the first 0x1800000 bytes
at least of the first partition were overwritten, destroying the file
system on the usbstick.

>From dmesg when that usb drive is hotplugged:-

Direct-Access     Flash    Drive SM 2.0     3000 PQ: 0 ANSI: 0 CCS
sd 6:0:0:0: Attached scsi generic sg2 type 0
sd 6:0:0:0: [sdb] 4021248 512-byte logical blocks: (2.06 GB/1.92 GiB)
sd 6:0:0:0: [sdb] Write Protect is off
sd 6:0:0:0: [sdb] Mode Sense: 43 00 00 00
sd 6:0:0:0: [sdb] No Caching mode page found
sd 6:0:0:0: [sdb] Assuming drive cache: write through
sdb: sdb1
sd 6:0:0:0: [sdb] Attached SCSI removable disk

#fdisk:
Disk /dev/sdb: 1.9 GiB, 2058878976 bytes, 4021248 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xc3072e18

Device     Boot Start     End Sectors  Size Id Type
/dev/sdb1          32 4015999 4015968  1.9G  c W95 FAT32 (LBA)


So flashbench seems very dangerous, and needs to ask for confirmation
before modifying the contents of a drive. The very sparse documentation
does not help.

This is on current debian testing:
# uname -a
Linux machine 4.9.0-2-amd64 #1 SMP Debian 4.9.13-1 (2017-02-27) x86_64 GNU/Linux

I have purged flashbench from my system as it is just too dangerous.

Reply via email to