Hot answers tagged

5

The drive names are (on a typical Linux system) decided by udev.How it decides which hardware maps to which block special file is an implementation detail that will depend your udev configuration, kernel configuration, module setup, and many other things, too (including plain luck). Typically udev will assign the first letter to whichever device it detects ...


4

Most filesystems have unique UUIDs and have labels which you can set to a distinctive values. These allow you to refer to the volume containing the filesystem through /dev/disk/by-uuid or /dev/disk/by-label. Other types of volumes (RAID, LVM, etc.) generally have a name as well. RAID and LVM volumes are assembled based on unique identifiers in the physical ...


1

Yes, you can treat the device file as a raw device file, and read/write data from/to it using the same APIs used to access normal files. In most cases, you can use dd, or simply cat data to/from the device file. Keep in mind that there are several practical differences between raw devices and real files on a filesystem: Devices have a fixed size. Writing ...


1

You could use CharybdeFS that was made exactly for this kind of purpose. It's a passthrough fuse filesystem like PetardFS but much more configurable. See the CharybdeFS cookbook here: http://www.scylladb.com/2016/05/02/fault-injection-filesystem-cookbook/ It's advanced enough to test a database.



Only top voted, non community-wiki answers of a minimum length are eligible