Also suggest against creating a generic label on a device which already
contains a filesystem.
PR: 264166
Differential D35326
glabel.8: Warn against using generic labels on a shared device markj on May 26 2022, 1:55 PM. Authored by Tags None Referenced Files
Details
Also suggest against creating a generic label on a device which already PR: 264166
Diff Detail
Event Timeline
Comment Actions "You should not use glabel with any device you plan on putting a filesystem on" might be better advise. Comment Actions And I think I'll retract the prior 'advise'.
Comment Actions Huh? Did you mean "If glabel is used, the filesystem should be put on the glabel device, rather than both label and filesystem put on a the same underlying device." (Or are you commenting on the quality or usefulness of glabel?) Comment Actions I was being catty.... But your advise is much better. glabel steals a sector or two for it's labeling info, and so you need to use the glabel device. It's also why you can't usually label something after the filesystem is on there: these stolen sector will be fought over potentially. What's confusing, though, is that things like /dev/ufs or /dev/gpt can be added later because those labels are integrated into either the partitioning or the filesystem superblock. not so with 'glabel label' command... Comment Actions mdoc(7) syntax looks good to me, so once the other issues pointed out with the manual page have been fixed, I'm happy to accept it.
Comment Actions This problem exists with any GEOM class that steals a sector or two for metadata. I had to fix an identical issue with a script at old $JOB where a gmirror would be created on a partition already containing a filesystem. And most of the time it worked fine.
Comment Actions I don't think there's anything to discuss currently? If there are no objections I'll commit in a couple of days. Comment Actions Seems a bit wordy for a man page, but this manual page is chattier than most. The information is correct, however. |