aboutsummaryrefslogtreecommitdiff
path: root/sys/kern/sys_pipe.c
diff options
context:
space:
mode:
authorXin LI <delphij@FreeBSD.org>2014-05-27 19:46:11 +0000
committerXin LI <delphij@FreeBSD.org>2014-05-27 19:46:11 +0000
commit2bdf7f79bcda8d2eaff1c659e63f73f9ad34f3d8 (patch)
treea60d21795e1835a4decb1b4799c78d83e5af089c /sys/kern/sys_pipe.c
parenta94ec03f8f3c83b4649ff63bed8b8f26b8f1363f (diff)
parentbec2af9b627e6629bbad099a7bbfaeff24de3cea (diff)
downloadsrc-2bdf7f79bcda8d2eaff1c659e63f73f9ad34f3d8.tar.gz
src-2bdf7f79bcda8d2eaff1c659e63f73f9ad34f3d8.zip
MFV r266766:
Add a new zfs property, "redundant_metadata" which can have values "all" or "most". The default will be "all", which is the current behavior. When set to all, ZFS stores an extra copy of all metadata. If a single on-disk block is corrupt, at worst a single block of user data (which is recordsize bytes long) can be lost. Setting to "most" will cause us to only store 1 copy of level-1 indirect blocks of user data files. This can improve performance of random writes, because less metadata has to be written. In practice, at worst about 100 blocks (of recordsize bytes each) of user data can be lost if a single on-disk block is corrupt. The exact behavior of which metadata blocks are stored redundantly may change in future releases. Illumos issue: 3835 zfs need not store 2 copies of all metadata MFC after: 2 weeks
Notes
Notes: svn path=/head/; revision=266771
Diffstat (limited to 'sys/kern/sys_pipe.c')
0 files changed, 0 insertions, 0 deletions