Re: Recognition Of Linux LVMs
On 8/8/23 05:17, Jay F. Shachter wrote: and I wonder, parenthetically, why FreeBSD and NetBSD are willing to support ZFS, but OpenBSD is not I think that is a question for the FreeBSD and NetBSD teams, why are they willing to spend the extra time in support, and face the potential legal risk in terms of patent lawsuit exposure, in supporting ZFS. While there are things I think would be "nice to haves" in the OpenBSD world, I can understand a small team deciding a particular feature is technically and/or legally, not worth the trouble. LVM is far from a trivial feature to add, and it's not like they can just copy the implementation from the Linux kernel -- not unless they wanted the resulting work to be GPL-licensed. I think it's time to recognise this particular horse is dead, and is no longer available for rides. -- Stuart Longland (aka Redhatter, VK4MSL) I haven't lost my mind... ...it's backed up on a tape somewhere.
Re: Recognition Of Linux LVMs
On 2023-08-07, Jay F. Shachter wrote: > I was asking whether Linux logical volumes can be recognized > as disk devices by the OpenBSD kernel, in the way that they can be > recognized in NetBSD, and in FreeBSD. AFAIK, not without a bunch of work. I suppose it could be done by extending softraid. But what will be the end result? People wanting to share filesystems between OS and wanting better support from the ext2fs layer? People asking for assistance with complicated multi boot installs? None of this really helps OpenBSD. > then create within that volume group a logical volume named "lvname", > then, on the NetBSD system, I can access this logical volume by using > the exact same names that are used on Linux: either /dev/vgname/lvname, > or /dev/mapper/vgname-lvname. On FreeBSD the device name is slightly > different, on FreeBSD you say /dev/linux_lvm/vgname-lvname, but in > either case the logical volume is visible. There's no devfs here so even if there were support, the most you'd be likely to get device nodes like /dev/sd2a etc. >My question for this > mailing list was: Are Linux logical volumes visible, or can they be > made visible, on an OpenBSD system? I suppose if a filesystem is on a single continuous chunk of disk and not using the fancier features, you /could/ try adding the location/size as a partition in OpenBSD's disklabel. It doesn't really seem like OpenBSD is a good fit for what you want to do, and that's fine, it is not expected to be useful for everyone.
Re: Recognition Of Linux LVMs
For the several wished-for things here to happen, primarily somebody would need to write the code (or port existing code) to support those features. The reasons why this has not been done for each of those differ, but generally boil down to (in no particular order) * No developer has been motivated to spend sufficient effort on the problem -- for example, anything that has to do with multibooting seems to be not really a priority. * a variation of previous, some features require a *lot* of work to go anywhere, so things that would be desirable in principle have not (yet) happened because getting them done would require more work than there are hands (and brains) available to get done to project quality standards. * Legal issues. For the ZFS case, the first hurdle is the CDDL (see https://en.wikipedia.org/wiki/Common_Development_and_Distribution_License), and if those complications were not enough, the code is affected by if I remember correctly at least a couple of dozen patent claims that have been subject to lawsuits and a few sealed settlements. And of course, some developer may well have started working on something but life happens (including some licensing kerfuffles, including IIRC one that lead to the abandonment of at least one attemtpt at supporting a certain class of BroadCom wifi parts). Generally, searching on the obvious keywords such as the device name and operating system name will give some clues. - Peter -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/ "Remember to set the evil bit on all malicious network traffic" delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
Re: Recognition Of Linux LVMs
Greg Thomas wrote: > > storage (and I wonder, parenthetically, why FreeBSD and NetBSD are > > willing to support ZFS, but OpenBSD is not). Why continue to wonder? Why not just sit down and figure out that they surrendered their ideals? I make vegeterian meals all the time, with a big slab of beef on the other half of the plate.
Re: Recognition Of Linux LVMs
On Mon, Aug 7, 2023 at 12:20 PM Jay F. Shachter wrote: > > > > > As the primary author of OpenBSD's current fdisk/disklabel/etc. I > > was intrigued by your recent email to misc@ [I]f you want > > disklabel(8) to say "Linux LVM" for sd0l you would need at a minimum > > a patch to /usr/src/sys/sys/disklabel.h to add an FS_LINUXLVM define > > and the string "Linux LVM" to the immediately following > > fstypenames[] array > > > > Please forgive me for being unclear. > > I was not asking whether my Linux volume group could be recognized by > the OpenBSD "disklabel" program as a Linux volume group, and correctly > identified as such. That would certainly be nice, and a welcome > improvement to the disklabel program, but it was not what I was > asking. I was asking whether Linux logical volumes can be recognized > as disk devices by the OpenBSD kernel, in the way that they can be > recognized in NetBSD, and in FreeBSD. Thus, if I have a multiboot > computer, on which Linux, FreeBSD, and NetBSD have been installed, and > if, on the Linux system, I create a volume group named "vgname", and I > then create within that volume group a logical volume named "lvname", > then, on the NetBSD system, I can access this logical volume by using > the exact same names that are used on Linux: either /dev/vgname/lvname, > or /dev/mapper/vgname-lvname. On FreeBSD the device name is slightly > different, on FreeBSD you say /dev/linux_lvm/vgname-lvname, but in > either case the logical volume is visible. My question for this > mailing list was: Are Linux logical volumes visible, or can they be > made visible, on an OpenBSD system? > > I have already remarked that my Solaris, Linux, FreeBSD, and NetBSD > systems can share disk storage (e.g., the /home/jay directory) by > means of a ZFS pool, but that OpenBSD cannot, because OpenBSD does not > support ZFS, and that, therefore, installing an OpenBSD system on the > same hardware will require some duplication of otherwise shared disk > storage (and I wonder, parenthetically, why FreeBSD and NetBSD are > willing to support ZFS, but OpenBSD is not). > Stuart already told you this: "Not likely to happen. Even if there was an implementation written, patents are involved (use is granted via the CDDL but that's not an acceptable license for OpenBSD)."
Re: Recognition Of Linux LVMs
> On Aug 7, 2023, at 12:20 PM, Jay F. Shachter wrote: > > Can OpenBSD be made to see Linux logical volumes? As I’ve often said at work, anything is possible with computers!
Recognition Of Linux LVMs
> > As the primary author of OpenBSD's current fdisk/disklabel/etc. I > was intrigued by your recent email to misc@ [I]f you want > disklabel(8) to say "Linux LVM" for sd0l you would need at a minimum > a patch to /usr/src/sys/sys/disklabel.h to add an FS_LINUXLVM define > and the string "Linux LVM" to the immediately following > fstypenames[] array > Please forgive me for being unclear. I was not asking whether my Linux volume group could be recognized by the OpenBSD "disklabel" program as a Linux volume group, and correctly identified as such. That would certainly be nice, and a welcome improvement to the disklabel program, but it was not what I was asking. I was asking whether Linux logical volumes can be recognized as disk devices by the OpenBSD kernel, in the way that they can be recognized in NetBSD, and in FreeBSD. Thus, if I have a multiboot computer, on which Linux, FreeBSD, and NetBSD have been installed, and if, on the Linux system, I create a volume group named "vgname", and I then create within that volume group a logical volume named "lvname", then, on the NetBSD system, I can access this logical volume by using the exact same names that are used on Linux: either /dev/vgname/lvname, or /dev/mapper/vgname-lvname. On FreeBSD the device name is slightly different, on FreeBSD you say /dev/linux_lvm/vgname-lvname, but in either case the logical volume is visible. My question for this mailing list was: Are Linux logical volumes visible, or can they be made visible, on an OpenBSD system? I have already remarked that my Solaris, Linux, FreeBSD, and NetBSD systems can share disk storage (e.g., the /home/jay directory) by means of a ZFS pool, but that OpenBSD cannot, because OpenBSD does not support ZFS, and that, therefore, installing an OpenBSD system on the same hardware will require some duplication of otherwise shared disk storage (and I wonder, parenthetically, why FreeBSD and NetBSD are willing to support ZFS, but OpenBSD is not). But if OpenBSD can see Linux volume groups, and the logical volumes that are carved out of them, then there can be shared disk storage among Linux, FreeBSD, NetBSD, and OpenBSD, and that would reduce somewhat the extent to which an OpenBSD system requires that disk storage be duplicated. Can OpenBSD be made to see Linux logical volumes? As always, thank you in advance for any and all replies. Jay F. Shachter 6424 North Whipple Street Chicago IL 60645-4111 (1-773)7613784 landline (1-410)9964737 GoogleVoice j...@m5.chicago.il.us http://m5.chicago.il.us "Quidquid latine dictum sit, altum videtur"