Hello, I asked this question last week on zfs-de...@list.zfsonlinux.org without any reply yet.
Possibly it is here where it is more appropriate to ask, even though this looks like a platform-specific issue. Hope somebody would be willing to describe the details of what will break on a 32-bit linux platform with the .zfs ctldir support enabled. A brief reading of the code did not reveal to me anything that apparently would become wrong, even though the comment in the file says that the ctldir must be disabled on 32-bit. Nor does a 32-bit build with ctldir enabled readily crash or corrupt data. Would anybody who is familiar with the underlying structures explain why it would be hard (or what is needed) to enable the functionality for a 32-bit linux environment? If this is a choice, e.g. between NFS-exports and the presence of .zfs, it could be possibly documented as one, namely what is to be sacrificed if one wishes the transparent access to the snapshots. I would be thankful for a comment from the developers. Regards, Rune ------------------------------------------- openzfs-developer Archives: https://www.listbox.com/member/archive/274414/=now RSS Feed: https://www.listbox.com/member/archive/rss/274414/28015062-cce53afa Modify Your Subscription: https://www.listbox.com/member/?member_id=28015062&id_secret=28015062-f966d51c Powered by Listbox: http://www.listbox.com
