On Thu, Apr 19, 2018 at 10:40:10AM -0700, Matthew Wilcox wrote: > With dm-removable: Nobody thought to set up dm-removable on the root > drive. Calamities still ensue, but now it's the BOFH's fault instead > of the PFY's fault. > > Built into the block layer: After a brief hiccup while we reattach the > drive to its block_device, the writes resume and nobody loses their job. What you're talking about is a deployment issue, though. Ultimately the distribution will set up dm-removable automatically if the user requests it, much like it sets up dm-crypt automatically for laptop users upon request. My concern is that not all removable devices have a globally unique id number available in hardware so the kernel can tell whether or not it's the same device that has been plugged in. There are hueristics you could use -- for example, you could look at the file system uuid plus the last fsck time. But they tend to be very file system specific, and not things we would want ot have in the kernel. - Ted
