LABEL=backup /media/backup ext4 user,noauto,rw 0 0
sudo blkid -c /dev/null
viking777 wrote:you may well be better off manually changing the ID value of one of them with tune2fs.
AlbertP wrote:Probably the harddisks come from the same manufacturer which hasn't realized that UUID's have to be unique. It looks like one NTFS partition was cloned and put on all those disks.
The disks use NTFS, so tune2fs (which works on ext2/3/4 filesystems) will be useless
statistical perspective, it's much more likely that you'll run into duplicated NTFS or FAT filesystem serial numbers.
viking777 wrote:What kind of UUID it sets I have no idea though I guess it will be a 'Linux' UUID not a 'True' UUID.
grimdestripador wrote:statistical perspective, it's much more likely that you'll run into duplicated NTFS or FAT filesystem serial numbers.
Probability of Collisions
viking777 wrote:So based on the fact that the OP has three identical UUID's out of 13 partitions I guess he should definitely do the lottery this week (and probably shouldn't go out in a thunderstorm).
The intent of UUIDs is to enable distributed systems to uniquely identify information without significant central coordination. In this context the word unique should be taken to mean "practically unique" rather than "guaranteed unique". Since the identifiers have a finite size, it is possible for two differing items to share the same identifier The identifier size and generation process need to be selected so as to make this sufficiently improbable in practice...
Manufacturer's quality control issue for hard drives: they would have the option of ensuring randomness as far as it is possible.
Users browsing this forum: Google Adsense [Bot] and 2 guests