Hi, On Thu, Feb 15, 2024 at 03:59:30PM -0500, gene heskett wrote: > Now the question remains howinhell do I put a label on a drive > such that it does survive making a raid or lvm device with it? To > not have a way to id its the drive in slot n of a multislot rack > stops me in my tracks.
Given that an MD RAID array or a LVM Logical Volume may be spread across many different underlying storage devices, the question doesn't make sense. Due to the fact that filesystems go on block devices, and RAID arrays and LVM LVs can be block devices, a filesystem label in that instance would represent possibly multiple underlying storage devices. So step back and tell us what are you actually trying to achieve, rather than insisting on your X solution to your Y problem. Suppose you have the MD array /dev/md42. What are you conceptually wanting to do with that in relation to labels of some kind? What information is it that you want? Support you have LVM logical volume /dev/myvg/mylv. What are you conceptually wanting to do with that in relation to labels of some kind? What information is it that you want? > Particularly with these gigastones, I 5 of them but when all are plugged in > there are only 3 becauae there are 2 pairs of matching serial numbers in the > by-id output, by-id sees all 5 drives, but udev see's only the unique > serial numbers. gparted can change the devices blkid, getting a new one from > rng so while you all think that's the greatest thing since bottled beer, I > know better. Once you explain what information you're trying to get when you start with an LVM or MD device, I can probably advise how to get it, but just to make clear: I don't think it's a good idea to continue to use such broken devices. We don't need to debate that since I know you've been posting about that a lot and clearly have decided to push ahead. I just think you haven't seen the end of the problems with that issue. Regards, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
