On 12.03.16 16:26, Dan062 via luv-main wrote:
Hi,
Using Ubuntu 12.04:
I have a strange situation where a usb drive was initially mounted as /dev/sdb1 to a directory /ut. For several days data read-write to the drive was going just fine. Then suddenly all read-write stopped, with a Input/Output error, and while mount showed that /dev/sd1 was still mounted on /ut.
Investigating further I found using blkid that the usb drive was now showing as /dev/sdc1. How can this happen?
Isn't that why those crazy long UIDs were invented? Dunno how it happens, but it does - certainly on ubuntu, and probably on my current debian box, IIRC. Possibly more directly useful than speculating on why it faffs around unreliably, is how to avoid any negative effect. For plug-in usb drives, I label the stick with e2label (16 characters max.), e.g. ext3_backup_1 The auto-mounting facility then always mounts that on /media/ext3_backup_1 and Murphy doesn't get a look in. The device, just now, is /dev/sdb, without any digit, but I'm able to ignore that. Incidentally, has anyone else found that usb sticks from the supermarket are unreliable? I have a new one which has begun showing up to 6% byte corruption in maybe 0.1% of files. (That failure is obviously not detected by rsync's default "quick check" algorithm which only looks for files that have changed in size or in last-modified time.) It's intended replacement, formatted to ext3, won't take files at all. Much older drives from Harvey Norman are doing fine, after a pile of writes. Erik