forked from openzfs/zfs
-
Notifications
You must be signed in to change notification settings - Fork 5
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
This means in cases where a pool is not cleanly exported you may end up with loss of unflushed TX_RENAME_EXCHANGE and TX_RENAME_WHITEOUT transactions and all transactions that follow them in the ZIL for that dataset if the pool is then imported by a release build of ZFS that does not recognize the new TX types. A warning message is logged to dmesg and the pool is fully usable, just missing the last changes. Debug builds will panic when they fail to replay the full log. It's also possible a different new TX type might land upstream before this, in which case similar results are likely to be encountered. The alternative is a pool that cannot be imported on any version of ZFS lacking support for TX_RENAME_EXCHANGE and TX_RENAME_WHITEOUT replay when uncleanly exported. That prevents people from either upgrading their pool for the ability to use overlayfs features or going back to a previous boot environment after having upgraded the pool. Signed-off-by: Ryan Moeller <[email protected]>
- Loading branch information
Ryan Moeller
authored and
Ryan Moeller
committed
Oct 19, 2022
1 parent
0abd108
commit fbb9b45
Showing
11 changed files
with
0 additions
and
253 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.