Archive-Team
/
zfs
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases 103 Wiki Activity
zfs/AUTHORS

96 lines
3.6 KiB
Plaintext
Raw Normal View History

Update AUTHORS file This file has gotten stale and needed to be updated. There are individuals who deserve to be recognized for their contributions to the project. I've done my best to assemble names from the commit logs of those who have submitted patches. This list may not be comprehensive, if you feel I've overlooked your contribution please let me know and we can get your name added.
2011-02-08 23:40:52 +00:00
Brian Behlendorf is the principle developer of the ZFS on Linux port.
He works full time as a computer scientist at Lawrence Livermore
National Laboratory on the ZFS and Lustre filesystems. However,
this port would not have been possible without the help of many
others who have contributed their time, effort, and insight.
Brian Behlendorf <behlendorf1@llnl.gov>
First and foremost the hard working ZFS developers at Sun/Oracle.
They are responsible for the bulk of the code in this project and
without their efforts there never would have been a ZFS filesystem.
The ZFS Development Team at Sun/Oracle
Refresh AUTHORS The AUTHORS file was getting stale. Refresh its contents using the authors listed in the git commit logs. Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov>
2012-12-19 17:47:25 +00:00
Next all the developers at KQ Infotech who implemented a prototype
ZFS Posix Layer (ZPL). Their implementation provided an excellent
reference for adding the ZPL functionality.
Update AUTHORS file This file has gotten stale and needed to be updated. There are individuals who deserve to be recognized for their contributions to the project. I've done my best to assemble names from the commit logs of those who have submitted patches. This list may not be comprehensive, if you feel I've overlooked your contribution please let me know and we can get your name added.
2011-02-08 23:40:52 +00:00
Anand Mitra <mitra@kqinfotech.com>
Anurag Agarwal <anurag@kqinfotech.com>
Neependra Khare <neependra@kqinfotech.com>
Prasad Joshi <prasad@kqinfotech.com>
Rohan Puri <rohan@kqinfotech.com>
Sandip Divekar <sandipd@kqinfotech.com>
Shoaib <shoaib@kqinfotech.com>
Shrirang <shrirang@kqinfotech.com>
Additionally the following individuals have all made contributions
to the project and deserve to be acknowledged.
Refresh AUTHORS The AUTHORS file was getting stale. Refresh its contents using the authors listed in the git commit logs. Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov>
2012-12-19 17:47:25 +00:00
Albert Lee <trisk@nexenta.com>
Alejandro R. Sedeño <asedeno@mit.edu>
Alex Zhuravlev <bzzz@whamcloud.com>
Alexander Eremin <a.eremin@nexenta.com>
Alexander Stetsenko <ams@nexenta.com>
Alexey Shvetsov <alexxy@gentoo.org>
Andreas Dilger <adilger@whamcloud.com>
Andrew Reid <ColdCanuck@nailedtotheperch.com>
Andrew Stormont <andrew.stormont@nexenta.com>
Andrew Tselischev <andrewtselischev@gmail.com>
Andriy Gapon <avg@FreeBSD.org>
Aniruddha Shankar <k@191a.net>
Bill Pijewski <wdp@joyent.com>
Chris Dunlap <cdunlap@llnl.gov
Chris Dunlop <chris@onthe.net.au>
Chris Siden <chris.siden@delphix.com>
Chris Wedgwood <cw@f00f.org>
Christian Kohlschütter <christian@kohlschutter.com>
Christopher Siden <chris.siden@delphix.com>
Craig Sanders <github@taz.net.au>
Cyril Plisko <cyril.plisko@mountall.com>
Dan McDonald <danmcd@nexenta.com>
Daniel Verite <daniel@verite.pro>
Add "ashift" property to zpool create Some disks with internal sectors larger than 512 bytes (e.g., 4k) can suffer from bad write performance when ashift is not configured correctly. This is caused by the disk not reporting its actual sector size, but a sector size of 512 bytes. The drive may behave this way for compatibility reasons. For example, the WDC WD20EARS disks are known to exhibit this behavior. When creating a zpool, ZFS takes that wrong sector size and sets the "ashift" property accordingly (to 9: 1<<9=512), whereas it should be set to 12 for 4k sectors (1<<12=4096). This patch allows an adminstrator to manual specify the known correct ashift size at 'zpool create' time. This can significantly improve performance in certain cases. However, it will have an impact on your total pool capacity. See the updated ashift property description in the zpool.8 man page for additional details. Valid values for the ashift property range from 9 to 17 (512B-128KB). Additionally, you may set the ashift to 0 if you wish to auto-detect the sector size based on what the disk reports, this is the default behavior. The most common ashift values are 9 and 12. Example: zpool create -o ashift=12 tank raidz2 sda sdb sdc sdd Closes #280 Original-patch-by: Richard Laager <rlaager@wiktel.com> Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov>
2011-06-16 19:56:38 +00:00
Darik Horn <dajhorn@vanadac.com>
Refresh AUTHORS The AUTHORS file was getting stale. Refresh its contents using the authors listed in the git commit logs. Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov>
2012-12-19 17:47:25 +00:00
Eric Schrock <Eric.Schrock@delphix.com>
Etienne Dechamps <etienne.dechamps@ovh.net>
Fajar A. Nugraha <github@fajar.net>
Frederik Wessels <wessels147@gmail.com>
Garrett D'Amore <garrett@nexenta.com>
George Wilson <george.wilson@delphix.com>
Gordon Ross <gwr@nexenta.com>
Gregor Kopka <mailfrom-github.com@kopka.net>
Gunnar Beutner <gunnar@beutner.name>
James H <james@kagisoft.co.uk>
Javen Wu <wu.javen@gmail.com>
Jeremy Gill <jgill@parallax-innovations.com>
Jorgen Lundman <lundman@lundman.net>
KORN Andras <korn@elan.rulez.org>
Kyle Fuller <inbox@kylefuller.co.uk>
Manuel Amador (Rudd-O) <rudd-o@rudd-o.com>
Martin Matuska <mm@FreeBSD.org>
Massimo Maggi <massimo@mmmm.it>
Matthew Ahrens <mahrens@delphix.com>
Michael Martin <mgmartin.mgm@gmail.com>
Mike Harsch <mike@harschsystems.com>
Ned Bass <bass6@llnl.gov>
Oleg Stepura <oleg@stepura.com>
P.SCH <p88@yahoo.com>
Pawel Jakub Dawidek <pawel@dawidek.net>
Prakash Surya <surya1@llnl.gov>
Prasad Joshi <pjoshi@stec-inc.com>
Ricardo M. Correia <Ricardo.M.Correia@Sun.COM>
Add "ashift" property to zpool create Some disks with internal sectors larger than 512 bytes (e.g., 4k) can suffer from bad write performance when ashift is not configured correctly. This is caused by the disk not reporting its actual sector size, but a sector size of 512 bytes. The drive may behave this way for compatibility reasons. For example, the WDC WD20EARS disks are known to exhibit this behavior. When creating a zpool, ZFS takes that wrong sector size and sets the "ashift" property accordingly (to 9: 1<<9=512), whereas it should be set to 12 for 4k sectors (1<<12=4096). This patch allows an adminstrator to manual specify the known correct ashift size at 'zpool create' time. This can significantly improve performance in certain cases. However, it will have an impact on your total pool capacity. See the updated ashift property description in the zpool.8 man page for additional details. Valid values for the ashift property range from 9 to 17 (512B-128KB). Additionally, you may set the ashift to 0 if you wish to auto-detect the sector size based on what the disk reports, this is the default behavior. The most common ashift values are 9 and 12. Example: zpool create -o ashift=12 tank raidz2 sda sdb sdc sdd Closes #280 Original-patch-by: Richard Laager <rlaager@wiktel.com> Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov>
2011-06-16 19:56:38 +00:00
Richard Laager <rlaager@wiktel.com>
Refresh AUTHORS The AUTHORS file was getting stale. Refresh its contents using the authors listed in the git commit logs. Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov>
2012-12-19 17:47:25 +00:00
Richard Lowe <richlowe@richlowe.net>
Richard Yao <ryao@cs.stonybrook.edu>
Rohan Puri <rohan.puri15@gmail.com>
Shampavman <sham.pavman@nexenta.com>
Simon Klinkert <klinkert@webgods.de>
Suman Chakravartula <suman@gogrid.com>
Tim Haley <Tim.Haley@Sun.COM>
Turbo Fredriksson <turbo@bayour.com>
Xin Li <delphij@FreeBSD.org>
Yuxuan Shui <yshuiv7@gmail.com>
Zachary Bedell <zac@thebedells.org>
nordaux <nordaux@gmail.com>