Chris Murphy posted on Sun, 12 Jan 2014 14:50:03 -0700 as excerpted: > This change in block device designation is why using /dev/X in fstab is > not a good idea, it's an ambiguous entry. I don't know what file system > was actually mounted by fstab, and to what volume sdc was added. I > suggest changing fstab to use fs UUID from blkid. FWIW, I use labels here. They work as well (as long as you don't duplicate them) and are much more human-friendly than UUIDs. I have a particular labeling scheme that guarantees they're unique within my setup, and are extremely likely to be unique with the set of any other hardware I'd use, as well. I use GPT partitioning (instead of MBR) for better fault tolerance and flexibility here, too, and it has partition names/labels which can be used in fstab, too. I use the same label and partlabel scheme, with the filesystem label generally reflecting the partlabel(s) it's created on, however, so it doesn't really matter which I use, except that PARTLABEL= is longer in fstab, so I use the shorter LABEL=, instead. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
