I've only seen msdos partition tables (MBR) on new flash drives.
It's usually FAT32. But you can only store files up to 4GB in size on this fs type. I would go for NTFS or exFAT instead, but this depends on the compatibility of your devices.
The accepted answer really didn't help me that much. I finally found out a way by probing the idProduct and idVendor if they exist. Here's a shell script
for i in *; do
[ -e $i/idProduct ] && echo $(cat $i/idVendor $i/idProduct) $i
Here's what I get on my system.
0424 2514 1-3
Thanks to all the comments. The main takeaways for me were:
Do not use ls /dev for checking which devices are on the system, but use dmesg instead (and in the particular case of sound cards, 7.2.2 Testing Sound is really useful)
devfs has the ability to create device nodes on demand (when they are first accessed)
The mentioned sound(4) manpage says:
The examples given in the question are not block devices, but the question is asked generically, so if yours is a block device, use:
badblocks -n -c1 /dev/device-name 0 0
This will try to do a non-destructive re-write of the first 1024 bytes of the device
If it's in use, you'll see:
/dev/device-name is apparently in use by the system; it's ...
Even better than /tmp are the tmpfs volumes. These behave like real filesystems but are actually "RAM drives". They offer :
read, write and delete is really fast
purged at power off and unmount
Distributions (at least Debian does it) usually set up one (or more) for you. List them with :
mount | grep tmpfs
df -h | grep tmpfs
which also shows the ...
In NVM Express and related standards, controllers give access to storage divided into one or more namespaces. Namespaces can be created and deleted via the controller, as long as there is room for them (or the underlying storage supports thin provisioning), and multiple controllers can provide access to a shared namespace. How the underlying storage is ...