diff options
author | Brian Behlendorf <[email protected]> | 2012-07-19 14:50:25 -0700 |
---|---|---|
committer | Brian Behlendorf <[email protected]> | 2012-07-20 12:20:57 -0700 |
commit | fc173c85892841c283aac4e5174d6d8762463062 (patch) | |
tree | e6ebd29eb87d4b03804b8e8a1398ed3c4c1ceaa4 /module/zfs/zrlock.c | |
parent | 2a4a9dc2f09d7672268af4a4f70e1a26b481b5e9 (diff) |
Disable .zfs directory on 32-bit systems
The .zfs control directory implementation currently relies on
the fact that there is a direct 1:1 mapping from an object id
to its inode number. This works well as long as the system
uses a 64-bit value to store the inode number.
Unfortunately, the Linux kernel defines the inode number as
an 'unsigned long' type. This means that for 32-bit systems
will only have 32-bit inode numbers but we still have 64-bit
object ids.
This problem is particularly acute for the .zfs directories
which leverage those upper 32-bits. This is done to avoid
conflicting with object ids which are allocated monotonically
starting from 0. This is likely to also be a problem for
datasets on 32-bit systems with more than ~2 billion files.
The right long term fix must remove the simple 1:1 mapping.
Until that's done the only safe thing to do is to disable the
.zfs directory on 32-bit systems.
Signed-off-by: Brian Behlendorf <[email protected]>
Diffstat (limited to 'module/zfs/zrlock.c')
0 files changed, 0 insertions, 0 deletions