<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in vdev_iterator.cc</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>9e5787d2 - Merge OpenZFS support in to HEAD.</title>
        <link>http://172.16.0.5:8080/history/freebsd-13.1/cddl/usr.sbin/zfsd/vdev_iterator.cc#9e5787d2</link>
        <description>Merge OpenZFS support in to HEAD.The primary benefit is maintaining a completely sharedcode base with the community allowing FreeBSD to receivenew features sooner and with less effort.I would advise against doing &apos;zpool upgrade&apos;or creating indispensable pools using newfeatures until this change has had a month+to soak.Work on merging FreeBSD support in to what wasat the time &quot;ZFS on Linux&quot; began in August 2018.I first publicly proposed transitioning FreeBSDto (new) OpenZFS on December 18th, 2018. FreeBSDsupport in OpenZFS was finally completed in December2019. A CFT for downstreaming OpenZFS support into FreeBSD was first issued on July 8th. All issuesthat were reported have been addressed or, fora couple of less critical matters there arepull requests in progress with OpenZFS. iXsystemshas tested and dogfooded extensively internally.The TrueNAS 12 release is based on OpenZFS withsome additional features that have not yet madeit upstream.Improvements include:  project quotas, encrypted datasets,  allocation classes, vectorized raidz,  vectorized checksums, various command line  improvements, zstd compression.Thanks to those who have helped along the way:Ryan Moeller, Allan Jude, Zack Welch, and manyothers.Sponsored by:	iXsystems, Inc.Differential Revision:	https://reviews.freebsd.org/D25872

            List of files:
            /freebsd-13.1/cddl/usr.sbin/zfsd/vdev_iterator.cc</description>
        <pubDate>Tue, 25 Aug 2020 02:21:27 +0000</pubDate>
        <dc:creator>Matt Macy &lt;mmacy@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>12a88a3d - zfsd should be able to online an L2ARC that disappears and returns</title>
        <link>http://172.16.0.5:8080/history/freebsd-13.1/cddl/usr.sbin/zfsd/vdev_iterator.cc#12a88a3d</link>
        <description>zfsd should be able to online an L2ARC that disappears and returnsPreviously, this didn&apos;t work because L2ARC devices&apos; labels don&apos;t containpool GUIDs.  Modify zfsd so that the pool GUID won&apos;t be required:lib/libdevdctl/guid.h	Change INVALID_GUID from a uint64_t constant to a function that	returns an invalid Guid object.  Remove the void constructor.	Nothing uses it, and it violates RAII.cddl/usr.sbin/zfsd/case_file.hcddl/usr.sbin/zfsd/case_file.cc	Allow CaseFile::Find to match a CaseFile based on Vdev GUID alone.	In CaseFile::ReEvaluate, attempt to online devices even if the newly	arrived device has no pool GUID.cddl/usr.sbin/zfsd/vdev_iterator.cc	Iterate through a pool&apos;s cache devices as well as its regular	devices.Reported by:	avgReviewed by:	avgMFC after:	3 weeksSponsored by:	Spectra Logic CorpDifferential Revision:	https://reviews.freebsd.org/D12791

            List of files:
            /freebsd-13.1/cddl/usr.sbin/zfsd/vdev_iterator.cc</description>
        <pubDate>Thu, 26 Oct 2017 15:28:18 +0000</pubDate>
        <dc:creator>Alan Somers &lt;asomers@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>0f2297b1 - zfsd: Remove a redundant semicolon,</title>
        <link>http://172.16.0.5:8080/history/freebsd-13.1/cddl/usr.sbin/zfsd/vdev_iterator.cc#0f2297b1</link>
        <description>zfsd: Remove a redundant semicolon,

            List of files:
            /freebsd-13.1/cddl/usr.sbin/zfsd/vdev_iterator.cc</description>
        <pubDate>Tue, 31 May 2016 21:23:57 +0000</pubDate>
        <dc:creator>Pedro F. Giffuni &lt;pfg@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>7a0c41d5 - zfsd(8), the ZFS fault management daemon</title>
        <link>http://172.16.0.5:8080/history/freebsd-13.1/cddl/usr.sbin/zfsd/vdev_iterator.cc#7a0c41d5</link>
        <description>zfsd(8), the ZFS fault management daemonAdd zfsd, which deals with hard drive faults in ZFS pools. It manageshotspares and replements in drive slots that publish physical paths.cddl/usr.sbin/zfsd	Add zfsd(8) and its unit testscddl/usr.sbin/Makefile	Add zfsd to the buildlib/libdevdctl	A C++ library that helps devd clients process eventslib/Makefileshare/mk/bsd.libnames.mkshare/mk/src.libnames.mk	Add libdevdctl to the build. It&apos;s a private library, unusable by	out-of-tree software.etc/defaults/rc.conf	By default, set zfsd_enable to NOetc/mtree/BSD.include.dist	Add a directory for libdevdctl&apos;s include filesetc/mtree/BSD.tests.dist	Add a directory for zfsd&apos;s unit testsetc/mtree/BSD.var.dist	Add /var/db/zfsd/cases, where zfsd stores case files while it&apos;s shut	down.etc/rc.d/Makefileetc/rc.d/zfsd	Add zfsd&apos;s rc scriptsys/cddl/contrib/opensolaris/uts/common/fs/zfs/vdev.c	Fix the resource.fs.zfs.statechange message. It had a number of	problems:	It was only being emitted on a transition to the HEALTHY state.	That made it impossible for zfsd to take actions based on drives	getting sicker.	It compared the new state to vdev_prevstate, which is the state that	the vdev had the last time it was opened.  That doesn&apos;t make sense,	because a vdev can change state multiple times without being	reopened.	vdev_set_state contains logic that will change the device&apos;s new	state based on various conditions.  However, the statechange event	was being posted _before_ that logic took effect.  Now it&apos;s being	posted after.Submitted by:	gibbs, asomers, mav, allanjudeReviewed by:	mav, delphijRelnotes:	yesSponsored by:	Spectra Logic Corp, iX SystemsDifferential Revision:	https://reviews.freebsd.org/D6564

            List of files:
            /freebsd-13.1/cddl/usr.sbin/zfsd/vdev_iterator.cc</description>
        <pubDate>Sat, 28 May 2016 17:43:40 +0000</pubDate>
        <dc:creator>Alan Somers &lt;asomers@FreeBSD.org&gt;</dc:creator>
    </item>
</channel>
</rss>
