Adopt pyzfs from ClusterHQ
This commit introduces several changes:
* Update LICENSE and project information
* Give a good PEP8 talk to existing Python source code
* Add RPM/DEB packaging for pyzfs
* Fix some outstanding issues with the existing pyzfs code caused by
changes in the ABI since the last time the code was updated
* Integrate pyzfs Python unittest with the ZFS Test Suite
* Add missing libzfs_core functions: lzc_change_key,
lzc_channel_program, lzc_channel_program_nosync, lzc_load_key,
lzc_receive_one, lzc_receive_resumable, lzc_receive_with_cmdprops,
lzc_receive_with_header, lzc_reopen, lzc_send_resume, lzc_sync,
lzc_unload_key, lzc_remap
Note: this commit slightly changes zfs_ioc_unload_key() ABI. This allow
to differentiate the case where we tried to unload a key on a
non-existing dataset (ENOENT) from the situation where a dataset has
no key loaded: this is consistent with the "change" case where trying
to zfs_ioc_change_key() from a dataset with no key results in EACCES.
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: loli10K <ezomori.nozomu@gmail.com>
Closes #7230
2018-03-18 08:34:45 +00:00
|
|
|
#
|
|
|
|
# Copyright 2015 ClusterHQ
|
|
|
|
#
|
|
|
|
# Licensed under the Apache License, Version 2.0 (the "License");
|
|
|
|
# you may not use this file except in compliance with the License.
|
|
|
|
# You may obtain a copy of the License at
|
|
|
|
#
|
|
|
|
# http://www.apache.org/licenses/LICENSE-2.0
|
|
|
|
#
|
|
|
|
# Unless required by applicable law or agreed to in writing, software
|
|
|
|
# distributed under the License is distributed on an "AS IS" BASIS,
|
|
|
|
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
|
|
# See the License for the specific language governing permissions and
|
|
|
|
# limitations under the License.
|
|
|
|
#
|
2018-03-03 10:10:34 +00:00
|
|
|
|
|
|
|
"""
|
|
|
|
Exceptions that can be raised by libzfs_core operations.
|
|
|
|
"""
|
2018-08-22 10:59:51 +00:00
|
|
|
from __future__ import absolute_import, division, print_function
|
2018-03-03 10:10:34 +00:00
|
|
|
|
|
|
|
import errno
|
2018-08-20 17:11:52 +00:00
|
|
|
from ._constants import (
|
2020-02-28 01:14:21 +00:00
|
|
|
ECHRNG,
|
|
|
|
ECKSUM,
|
|
|
|
ETIME,
|
2018-08-20 17:11:52 +00:00
|
|
|
ZFS_ERR_CHECKPOINT_EXISTS,
|
|
|
|
ZFS_ERR_DISCARDING_CHECKPOINT,
|
|
|
|
ZFS_ERR_NO_CHECKPOINT,
|
|
|
|
ZFS_ERR_DEVRM_IN_PROGRESS,
|
2019-02-08 23:44:15 +00:00
|
|
|
ZFS_ERR_VDEV_TOO_BIG,
|
2020-03-17 17:30:33 +00:00
|
|
|
ZFS_ERR_WRONG_PARENT,
|
RAID-Z expansion feature
This feature allows disks to be added one at a time to a RAID-Z group,
expanding its capacity incrementally. This feature is especially useful
for small pools (typically with only one RAID-Z group), where there
isn't sufficient hardware to add capacity by adding a whole new RAID-Z
group (typically doubling the number of disks).
== Initiating expansion ==
A new device (disk) can be attached to an existing RAIDZ vdev, by
running `zpool attach POOL raidzP-N NEW_DEVICE`, e.g. `zpool attach tank
raidz2-0 sda`. The new device will become part of the RAIDZ group. A
"raidz expansion" will be initiated, and the new device will contribute
additional space to the RAIDZ group once the expansion completes.
The `feature@raidz_expansion` on-disk feature flag must be `enabled` to
initiate an expansion, and it remains `active` for the life of the pool.
In other words, pools with expanded RAIDZ vdevs can not be imported by
older releases of the ZFS software.
== During expansion ==
The expansion entails reading all allocated space from existing disks in
the RAIDZ group, and rewriting it to the new disks in the RAIDZ group
(including the newly added device).
The expansion progress can be monitored with `zpool status`.
Data redundancy is maintained during (and after) the expansion. If a
disk fails while the expansion is in progress, the expansion pauses
until the health of the RAIDZ vdev is restored (e.g. by replacing the
failed disk and waiting for reconstruction to complete).
The pool remains accessible during expansion. Following a reboot or
export/import, the expansion resumes where it left off.
== After expansion ==
When the expansion completes, the additional space is available for use,
and is reflected in the `available` zfs property (as seen in `zfs list`,
`df`, etc).
Expansion does not change the number of failures that can be tolerated
without data loss (e.g. a RAIDZ2 is still a RAIDZ2 even after
expansion).
A RAIDZ vdev can be expanded multiple times.
After the expansion completes, old blocks remain with their old
data-to-parity ratio (e.g. 5-wide RAIDZ2, has 3 data to 2 parity), but
distributed among the larger set of disks. New blocks will be written
with the new data-to-parity ratio (e.g. a 5-wide RAIDZ2 which has been
expanded once to 6-wide, has 4 data to 2 parity). However, the RAIDZ
vdev's "assumed parity ratio" does not change, so slightly less space
than is expected may be reported for newly-written blocks, according to
`zfs list`, `df`, `ls -s`, and similar tools.
Sponsored-by: The FreeBSD Foundation
Sponsored-by: iXsystems, Inc.
Sponsored-by: vStack
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Reviewed-by: Mark Maybee <mark.maybee@delphix.com>
Authored-by: Matthew Ahrens <mahrens@delphix.com>
Contributions-by: Fedor Uporov <fuporov.vstack@gmail.com>
Contributions-by: Stuart Maybee <stuart.maybee@comcast.net>
Contributions-by: Thorsten Behrens <tbehrens@outlook.com>
Contributions-by: Fmstrat <nospam@nowsci.com>
Contributions-by: Don Brady <dev.fs.zfs@gmail.com>
Signed-off-by: Don Brady <dev.fs.zfs@gmail.com>
Closes #15022
2023-11-08 18:19:41 +00:00
|
|
|
ZFS_ERR_RAIDZ_EXPAND_IN_PROGRESS,
|
2020-03-17 17:30:33 +00:00
|
|
|
zfs_errno
|
2018-08-20 17:11:52 +00:00
|
|
|
)
|
2018-03-03 10:10:34 +00:00
|
|
|
|
|
|
|
|
|
|
|
class ZFSError(Exception):
|
|
|
|
errno = None
|
|
|
|
message = None
|
|
|
|
name = None
|
|
|
|
|
|
|
|
def __str__(self):
|
|
|
|
if self.name is not None:
|
Adopt pyzfs from ClusterHQ
This commit introduces several changes:
* Update LICENSE and project information
* Give a good PEP8 talk to existing Python source code
* Add RPM/DEB packaging for pyzfs
* Fix some outstanding issues with the existing pyzfs code caused by
changes in the ABI since the last time the code was updated
* Integrate pyzfs Python unittest with the ZFS Test Suite
* Add missing libzfs_core functions: lzc_change_key,
lzc_channel_program, lzc_channel_program_nosync, lzc_load_key,
lzc_receive_one, lzc_receive_resumable, lzc_receive_with_cmdprops,
lzc_receive_with_header, lzc_reopen, lzc_send_resume, lzc_sync,
lzc_unload_key, lzc_remap
Note: this commit slightly changes zfs_ioc_unload_key() ABI. This allow
to differentiate the case where we tried to unload a key on a
non-existing dataset (ENOENT) from the situation where a dataset has
no key loaded: this is consistent with the "change" case where trying
to zfs_ioc_change_key() from a dataset with no key results in EACCES.
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: loli10K <ezomori.nozomu@gmail.com>
Closes #7230
2018-03-18 08:34:45 +00:00
|
|
|
return "[Errno %d] %s: '%s'" % (
|
|
|
|
self.errno, self.message, self.name)
|
2018-03-03 10:10:34 +00:00
|
|
|
else:
|
|
|
|
return "[Errno %d] %s" % (self.errno, self.message)
|
|
|
|
|
|
|
|
def __repr__(self):
|
Adopt pyzfs from ClusterHQ
This commit introduces several changes:
* Update LICENSE and project information
* Give a good PEP8 talk to existing Python source code
* Add RPM/DEB packaging for pyzfs
* Fix some outstanding issues with the existing pyzfs code caused by
changes in the ABI since the last time the code was updated
* Integrate pyzfs Python unittest with the ZFS Test Suite
* Add missing libzfs_core functions: lzc_change_key,
lzc_channel_program, lzc_channel_program_nosync, lzc_load_key,
lzc_receive_one, lzc_receive_resumable, lzc_receive_with_cmdprops,
lzc_receive_with_header, lzc_reopen, lzc_send_resume, lzc_sync,
lzc_unload_key, lzc_remap
Note: this commit slightly changes zfs_ioc_unload_key() ABI. This allow
to differentiate the case where we tried to unload a key on a
non-existing dataset (ENOENT) from the situation where a dataset has
no key loaded: this is consistent with the "change" case where trying
to zfs_ioc_change_key() from a dataset with no key results in EACCES.
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: loli10K <ezomori.nozomu@gmail.com>
Closes #7230
2018-03-18 08:34:45 +00:00
|
|
|
return "%s(%r, %r)" % (
|
|
|
|
self.__class__.__name__, self.errno, self.message)
|
2018-03-03 10:10:34 +00:00
|
|
|
|
|
|
|
|
|
|
|
class ZFSGenericError(ZFSError):
|
|
|
|
|
|
|
|
def __init__(self, errno, name, message):
|
|
|
|
self.errno = errno
|
|
|
|
self.message = message
|
|
|
|
self.name = name
|
|
|
|
|
|
|
|
|
|
|
|
class ZFSInitializationFailed(ZFSError):
|
|
|
|
message = "Failed to initialize libzfs_core"
|
|
|
|
|
|
|
|
def __init__(self, errno):
|
|
|
|
self.errno = errno
|
|
|
|
|
|
|
|
|
|
|
|
class MultipleOperationsFailure(ZFSError):
|
|
|
|
|
|
|
|
def __init__(self, errors, suppressed_count):
|
|
|
|
# Use first of the individual error codes
|
|
|
|
# as an overall error code. This is more consistent.
|
|
|
|
self.errno = errors[0].errno
|
|
|
|
self.errors = errors
|
Adopt pyzfs from ClusterHQ
This commit introduces several changes:
* Update LICENSE and project information
* Give a good PEP8 talk to existing Python source code
* Add RPM/DEB packaging for pyzfs
* Fix some outstanding issues with the existing pyzfs code caused by
changes in the ABI since the last time the code was updated
* Integrate pyzfs Python unittest with the ZFS Test Suite
* Add missing libzfs_core functions: lzc_change_key,
lzc_channel_program, lzc_channel_program_nosync, lzc_load_key,
lzc_receive_one, lzc_receive_resumable, lzc_receive_with_cmdprops,
lzc_receive_with_header, lzc_reopen, lzc_send_resume, lzc_sync,
lzc_unload_key, lzc_remap
Note: this commit slightly changes zfs_ioc_unload_key() ABI. This allow
to differentiate the case where we tried to unload a key on a
non-existing dataset (ENOENT) from the situation where a dataset has
no key loaded: this is consistent with the "change" case where trying
to zfs_ioc_change_key() from a dataset with no key results in EACCES.
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: loli10K <ezomori.nozomu@gmail.com>
Closes #7230
2018-03-18 08:34:45 +00:00
|
|
|
# this many errors were encountered but not placed on the `errors` list
|
2018-03-03 10:10:34 +00:00
|
|
|
self.suppressed_count = suppressed_count
|
|
|
|
|
|
|
|
def __str__(self):
|
Adopt pyzfs from ClusterHQ
This commit introduces several changes:
* Update LICENSE and project information
* Give a good PEP8 talk to existing Python source code
* Add RPM/DEB packaging for pyzfs
* Fix some outstanding issues with the existing pyzfs code caused by
changes in the ABI since the last time the code was updated
* Integrate pyzfs Python unittest with the ZFS Test Suite
* Add missing libzfs_core functions: lzc_change_key,
lzc_channel_program, lzc_channel_program_nosync, lzc_load_key,
lzc_receive_one, lzc_receive_resumable, lzc_receive_with_cmdprops,
lzc_receive_with_header, lzc_reopen, lzc_send_resume, lzc_sync,
lzc_unload_key, lzc_remap
Note: this commit slightly changes zfs_ioc_unload_key() ABI. This allow
to differentiate the case where we tried to unload a key on a
non-existing dataset (ENOENT) from the situation where a dataset has
no key loaded: this is consistent with the "change" case where trying
to zfs_ioc_change_key() from a dataset with no key results in EACCES.
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: loli10K <ezomori.nozomu@gmail.com>
Closes #7230
2018-03-18 08:34:45 +00:00
|
|
|
return "%s, %d errors included, %d suppressed" % (
|
|
|
|
ZFSError.__str__(self), len(self.errors), self.suppressed_count)
|
2018-03-03 10:10:34 +00:00
|
|
|
|
|
|
|
def __repr__(self):
|
2019-08-30 16:44:43 +00:00
|
|
|
return "%s(%r, %r, errors=%r, suppressed=%r)" % (
|
Adopt pyzfs from ClusterHQ
This commit introduces several changes:
* Update LICENSE and project information
* Give a good PEP8 talk to existing Python source code
* Add RPM/DEB packaging for pyzfs
* Fix some outstanding issues with the existing pyzfs code caused by
changes in the ABI since the last time the code was updated
* Integrate pyzfs Python unittest with the ZFS Test Suite
* Add missing libzfs_core functions: lzc_change_key,
lzc_channel_program, lzc_channel_program_nosync, lzc_load_key,
lzc_receive_one, lzc_receive_resumable, lzc_receive_with_cmdprops,
lzc_receive_with_header, lzc_reopen, lzc_send_resume, lzc_sync,
lzc_unload_key, lzc_remap
Note: this commit slightly changes zfs_ioc_unload_key() ABI. This allow
to differentiate the case where we tried to unload a key on a
non-existing dataset (ENOENT) from the situation where a dataset has
no key loaded: this is consistent with the "change" case where trying
to zfs_ioc_change_key() from a dataset with no key results in EACCES.
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: loli10K <ezomori.nozomu@gmail.com>
Closes #7230
2018-03-18 08:34:45 +00:00
|
|
|
self.__class__.__name__, self.errno, self.message, self.errors,
|
|
|
|
self.suppressed_count)
|
2018-03-03 10:10:34 +00:00
|
|
|
|
|
|
|
|
|
|
|
class DatasetNotFound(ZFSError):
|
|
|
|
|
|
|
|
"""
|
Adopt pyzfs from ClusterHQ
This commit introduces several changes:
* Update LICENSE and project information
* Give a good PEP8 talk to existing Python source code
* Add RPM/DEB packaging for pyzfs
* Fix some outstanding issues with the existing pyzfs code caused by
changes in the ABI since the last time the code was updated
* Integrate pyzfs Python unittest with the ZFS Test Suite
* Add missing libzfs_core functions: lzc_change_key,
lzc_channel_program, lzc_channel_program_nosync, lzc_load_key,
lzc_receive_one, lzc_receive_resumable, lzc_receive_with_cmdprops,
lzc_receive_with_header, lzc_reopen, lzc_send_resume, lzc_sync,
lzc_unload_key, lzc_remap
Note: this commit slightly changes zfs_ioc_unload_key() ABI. This allow
to differentiate the case where we tried to unload a key on a
non-existing dataset (ENOENT) from the situation where a dataset has
no key loaded: this is consistent with the "change" case where trying
to zfs_ioc_change_key() from a dataset with no key results in EACCES.
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: loli10K <ezomori.nozomu@gmail.com>
Closes #7230
2018-03-18 08:34:45 +00:00
|
|
|
This exception is raised when an operation failure can be caused by a
|
|
|
|
missing snapshot or a missing filesystem and it is impossible to
|
|
|
|
distinguish between the causes.
|
2018-03-03 10:10:34 +00:00
|
|
|
"""
|
|
|
|
errno = errno.ENOENT
|
|
|
|
message = "Dataset not found"
|
|
|
|
|
|
|
|
def __init__(self, name):
|
|
|
|
self.name = name
|
|
|
|
|
|
|
|
|
|
|
|
class DatasetExists(ZFSError):
|
|
|
|
|
|
|
|
"""
|
Adopt pyzfs from ClusterHQ
This commit introduces several changes:
* Update LICENSE and project information
* Give a good PEP8 talk to existing Python source code
* Add RPM/DEB packaging for pyzfs
* Fix some outstanding issues with the existing pyzfs code caused by
changes in the ABI since the last time the code was updated
* Integrate pyzfs Python unittest with the ZFS Test Suite
* Add missing libzfs_core functions: lzc_change_key,
lzc_channel_program, lzc_channel_program_nosync, lzc_load_key,
lzc_receive_one, lzc_receive_resumable, lzc_receive_with_cmdprops,
lzc_receive_with_header, lzc_reopen, lzc_send_resume, lzc_sync,
lzc_unload_key, lzc_remap
Note: this commit slightly changes zfs_ioc_unload_key() ABI. This allow
to differentiate the case where we tried to unload a key on a
non-existing dataset (ENOENT) from the situation where a dataset has
no key loaded: this is consistent with the "change" case where trying
to zfs_ioc_change_key() from a dataset with no key results in EACCES.
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: loli10K <ezomori.nozomu@gmail.com>
Closes #7230
2018-03-18 08:34:45 +00:00
|
|
|
This exception is raised when an operation failure can be caused by an
|
|
|
|
existing snapshot or filesystem and it is impossible to distinguish between
|
2018-03-03 10:10:34 +00:00
|
|
|
the causes.
|
|
|
|
"""
|
|
|
|
errno = errno.EEXIST
|
|
|
|
message = "Dataset already exists"
|
|
|
|
|
|
|
|
def __init__(self, name):
|
|
|
|
self.name = name
|
|
|
|
|
|
|
|
|
|
|
|
class NotClone(ZFSError):
|
|
|
|
errno = errno.EINVAL
|
|
|
|
message = "Filesystem is not a clone, can not promote"
|
|
|
|
|
|
|
|
def __init__(self, name):
|
|
|
|
self.name = name
|
|
|
|
|
|
|
|
|
|
|
|
class FilesystemExists(DatasetExists):
|
|
|
|
message = "Filesystem already exists"
|
|
|
|
|
|
|
|
def __init__(self, name):
|
|
|
|
self.name = name
|
|
|
|
|
|
|
|
|
|
|
|
class FilesystemNotFound(DatasetNotFound):
|
|
|
|
message = "Filesystem not found"
|
|
|
|
|
|
|
|
def __init__(self, name):
|
|
|
|
self.name = name
|
|
|
|
|
|
|
|
|
|
|
|
class ParentNotFound(ZFSError):
|
|
|
|
errno = errno.ENOENT
|
|
|
|
message = "Parent not found"
|
|
|
|
|
|
|
|
def __init__(self, name):
|
|
|
|
self.name = name
|
|
|
|
|
|
|
|
|
|
|
|
class WrongParent(ZFSError):
|
2019-02-08 23:44:15 +00:00
|
|
|
errno = ZFS_ERR_WRONG_PARENT
|
2018-03-03 10:10:34 +00:00
|
|
|
message = "Parent dataset is not a filesystem"
|
|
|
|
|
|
|
|
def __init__(self, name):
|
|
|
|
self.name = name
|
|
|
|
|
|
|
|
|
|
|
|
class SnapshotExists(DatasetExists):
|
|
|
|
message = "Snapshot already exists"
|
|
|
|
|
|
|
|
def __init__(self, name):
|
|
|
|
self.name = name
|
|
|
|
|
|
|
|
|
|
|
|
class SnapshotNotFound(DatasetNotFound):
|
|
|
|
message = "Snapshot not found"
|
|
|
|
|
|
|
|
def __init__(self, name):
|
|
|
|
self.name = name
|
|
|
|
|
Adopt pyzfs from ClusterHQ
This commit introduces several changes:
* Update LICENSE and project information
* Give a good PEP8 talk to existing Python source code
* Add RPM/DEB packaging for pyzfs
* Fix some outstanding issues with the existing pyzfs code caused by
changes in the ABI since the last time the code was updated
* Integrate pyzfs Python unittest with the ZFS Test Suite
* Add missing libzfs_core functions: lzc_change_key,
lzc_channel_program, lzc_channel_program_nosync, lzc_load_key,
lzc_receive_one, lzc_receive_resumable, lzc_receive_with_cmdprops,
lzc_receive_with_header, lzc_reopen, lzc_send_resume, lzc_sync,
lzc_unload_key, lzc_remap
Note: this commit slightly changes zfs_ioc_unload_key() ABI. This allow
to differentiate the case where we tried to unload a key on a
non-existing dataset (ENOENT) from the situation where a dataset has
no key loaded: this is consistent with the "change" case where trying
to zfs_ioc_change_key() from a dataset with no key results in EACCES.
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: loli10K <ezomori.nozomu@gmail.com>
Closes #7230
2018-03-18 08:34:45 +00:00
|
|
|
|
2018-03-03 10:10:34 +00:00
|
|
|
class SnapshotNotLatest(ZFSError):
|
|
|
|
errno = errno.EEXIST
|
|
|
|
message = "Snapshot is not the latest"
|
|
|
|
|
|
|
|
def __init__(self, name):
|
|
|
|
self.name = name
|
|
|
|
|
Adopt pyzfs from ClusterHQ
This commit introduces several changes:
* Update LICENSE and project information
* Give a good PEP8 talk to existing Python source code
* Add RPM/DEB packaging for pyzfs
* Fix some outstanding issues with the existing pyzfs code caused by
changes in the ABI since the last time the code was updated
* Integrate pyzfs Python unittest with the ZFS Test Suite
* Add missing libzfs_core functions: lzc_change_key,
lzc_channel_program, lzc_channel_program_nosync, lzc_load_key,
lzc_receive_one, lzc_receive_resumable, lzc_receive_with_cmdprops,
lzc_receive_with_header, lzc_reopen, lzc_send_resume, lzc_sync,
lzc_unload_key, lzc_remap
Note: this commit slightly changes zfs_ioc_unload_key() ABI. This allow
to differentiate the case where we tried to unload a key on a
non-existing dataset (ENOENT) from the situation where a dataset has
no key loaded: this is consistent with the "change" case where trying
to zfs_ioc_change_key() from a dataset with no key results in EACCES.
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: loli10K <ezomori.nozomu@gmail.com>
Closes #7230
2018-03-18 08:34:45 +00:00
|
|
|
|
2018-03-03 10:10:34 +00:00
|
|
|
class SnapshotIsCloned(ZFSError):
|
|
|
|
errno = errno.EEXIST
|
|
|
|
message = "Snapshot is cloned"
|
|
|
|
|
|
|
|
def __init__(self, name):
|
|
|
|
self.name = name
|
|
|
|
|
|
|
|
|
|
|
|
class SnapshotIsHeld(ZFSError):
|
|
|
|
errno = errno.EBUSY
|
|
|
|
message = "Snapshot is held"
|
|
|
|
|
|
|
|
def __init__(self, name):
|
|
|
|
self.name = name
|
|
|
|
|
|
|
|
|
|
|
|
class DuplicateSnapshots(ZFSError):
|
|
|
|
errno = errno.EXDEV
|
|
|
|
message = "Requested multiple snapshots of the same filesystem"
|
|
|
|
|
|
|
|
def __init__(self, name):
|
|
|
|
self.name = name
|
|
|
|
|
|
|
|
|
|
|
|
class SnapshotFailure(MultipleOperationsFailure):
|
|
|
|
message = "Creation of snapshot(s) failed for one or more reasons"
|
|
|
|
|
|
|
|
def __init__(self, errors, suppressed_count):
|
|
|
|
super(SnapshotFailure, self).__init__(errors, suppressed_count)
|
|
|
|
|
|
|
|
|
|
|
|
class SnapshotDestructionFailure(MultipleOperationsFailure):
|
|
|
|
message = "Destruction of snapshot(s) failed for one or more reasons"
|
|
|
|
|
|
|
|
def __init__(self, errors, suppressed_count):
|
Adopt pyzfs from ClusterHQ
This commit introduces several changes:
* Update LICENSE and project information
* Give a good PEP8 talk to existing Python source code
* Add RPM/DEB packaging for pyzfs
* Fix some outstanding issues with the existing pyzfs code caused by
changes in the ABI since the last time the code was updated
* Integrate pyzfs Python unittest with the ZFS Test Suite
* Add missing libzfs_core functions: lzc_change_key,
lzc_channel_program, lzc_channel_program_nosync, lzc_load_key,
lzc_receive_one, lzc_receive_resumable, lzc_receive_with_cmdprops,
lzc_receive_with_header, lzc_reopen, lzc_send_resume, lzc_sync,
lzc_unload_key, lzc_remap
Note: this commit slightly changes zfs_ioc_unload_key() ABI. This allow
to differentiate the case where we tried to unload a key on a
non-existing dataset (ENOENT) from the situation where a dataset has
no key loaded: this is consistent with the "change" case where trying
to zfs_ioc_change_key() from a dataset with no key results in EACCES.
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: loli10K <ezomori.nozomu@gmail.com>
Closes #7230
2018-03-18 08:34:45 +00:00
|
|
|
super(SnapshotDestructionFailure, self).__init__(
|
|
|
|
errors, suppressed_count)
|
2018-03-03 10:10:34 +00:00
|
|
|
|
|
|
|
|
|
|
|
class BookmarkExists(ZFSError):
|
|
|
|
errno = errno.EEXIST
|
|
|
|
message = "Bookmark already exists"
|
|
|
|
|
|
|
|
def __init__(self, name):
|
|
|
|
self.name = name
|
|
|
|
|
|
|
|
|
|
|
|
class BookmarkNotFound(ZFSError):
|
|
|
|
errno = errno.ENOENT
|
|
|
|
message = "Bookmark not found"
|
|
|
|
|
|
|
|
def __init__(self, name):
|
|
|
|
self.name = name
|
|
|
|
|
|
|
|
|
|
|
|
class BookmarkMismatch(ZFSError):
|
|
|
|
errno = errno.EINVAL
|
2019-11-11 07:24:14 +00:00
|
|
|
message = "source is not an ancestor of the new bookmark's dataset"
|
|
|
|
|
|
|
|
def __init__(self, name):
|
|
|
|
self.name = name
|
|
|
|
|
|
|
|
|
|
|
|
class BookmarkSourceInvalid(ZFSError):
|
|
|
|
errno = errno.EINVAL
|
|
|
|
message = "Bookmark source is not a valid snapshot or existing bookmark"
|
2018-03-03 10:10:34 +00:00
|
|
|
|
|
|
|
def __init__(self, name):
|
|
|
|
self.name = name
|
|
|
|
|
|
|
|
|
|
|
|
class BookmarkNotSupported(ZFSError):
|
|
|
|
errno = errno.ENOTSUP
|
|
|
|
message = "Bookmark feature is not supported"
|
|
|
|
|
|
|
|
def __init__(self, name):
|
|
|
|
self.name = name
|
|
|
|
|
|
|
|
|
|
|
|
class BookmarkFailure(MultipleOperationsFailure):
|
|
|
|
message = "Creation of bookmark(s) failed for one or more reasons"
|
|
|
|
|
|
|
|
def __init__(self, errors, suppressed_count):
|
|
|
|
super(BookmarkFailure, self).__init__(errors, suppressed_count)
|
|
|
|
|
|
|
|
|
|
|
|
class BookmarkDestructionFailure(MultipleOperationsFailure):
|
|
|
|
message = "Destruction of bookmark(s) failed for one or more reasons"
|
|
|
|
|
|
|
|
def __init__(self, errors, suppressed_count):
|
Adopt pyzfs from ClusterHQ
This commit introduces several changes:
* Update LICENSE and project information
* Give a good PEP8 talk to existing Python source code
* Add RPM/DEB packaging for pyzfs
* Fix some outstanding issues with the existing pyzfs code caused by
changes in the ABI since the last time the code was updated
* Integrate pyzfs Python unittest with the ZFS Test Suite
* Add missing libzfs_core functions: lzc_change_key,
lzc_channel_program, lzc_channel_program_nosync, lzc_load_key,
lzc_receive_one, lzc_receive_resumable, lzc_receive_with_cmdprops,
lzc_receive_with_header, lzc_reopen, lzc_send_resume, lzc_sync,
lzc_unload_key, lzc_remap
Note: this commit slightly changes zfs_ioc_unload_key() ABI. This allow
to differentiate the case where we tried to unload a key on a
non-existing dataset (ENOENT) from the situation where a dataset has
no key loaded: this is consistent with the "change" case where trying
to zfs_ioc_change_key() from a dataset with no key results in EACCES.
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: loli10K <ezomori.nozomu@gmail.com>
Closes #7230
2018-03-18 08:34:45 +00:00
|
|
|
super(BookmarkDestructionFailure, self).__init__(
|
|
|
|
errors, suppressed_count)
|
2018-03-03 10:10:34 +00:00
|
|
|
|
|
|
|
|
|
|
|
class BadHoldCleanupFD(ZFSError):
|
|
|
|
errno = errno.EBADF
|
|
|
|
message = "Bad file descriptor as cleanup file descriptor"
|
|
|
|
|
|
|
|
|
|
|
|
class HoldExists(ZFSError):
|
|
|
|
errno = errno.EEXIST
|
|
|
|
message = "Hold with a given tag already exists on snapshot"
|
|
|
|
|
|
|
|
def __init__(self, name):
|
|
|
|
self.name = name
|
|
|
|
|
|
|
|
|
|
|
|
class HoldNotFound(ZFSError):
|
|
|
|
errno = errno.ENOENT
|
|
|
|
message = "Hold with a given tag does not exist on snapshot"
|
|
|
|
|
|
|
|
def __init__(self, name):
|
|
|
|
self.name = name
|
|
|
|
|
|
|
|
|
|
|
|
class HoldFailure(MultipleOperationsFailure):
|
|
|
|
message = "Placement of hold(s) failed for one or more reasons"
|
|
|
|
|
|
|
|
def __init__(self, errors, suppressed_count):
|
|
|
|
super(HoldFailure, self).__init__(errors, suppressed_count)
|
|
|
|
|
|
|
|
|
|
|
|
class HoldReleaseFailure(MultipleOperationsFailure):
|
|
|
|
message = "Release of hold(s) failed for one or more reasons"
|
|
|
|
|
|
|
|
def __init__(self, errors, suppressed_count):
|
|
|
|
super(HoldReleaseFailure, self).__init__(errors, suppressed_count)
|
|
|
|
|
|
|
|
|
|
|
|
class SnapshotMismatch(ZFSError):
|
|
|
|
errno = errno.ENODEV
|
|
|
|
message = "Snapshot is not descendant of source snapshot"
|
|
|
|
|
|
|
|
def __init__(self, name):
|
|
|
|
self.name = name
|
|
|
|
|
|
|
|
|
|
|
|
class StreamMismatch(ZFSError):
|
|
|
|
errno = errno.ENODEV
|
|
|
|
message = "Stream is not applicable to destination dataset"
|
|
|
|
|
|
|
|
def __init__(self, name):
|
|
|
|
self.name = name
|
|
|
|
|
|
|
|
|
|
|
|
class DestinationModified(ZFSError):
|
|
|
|
errno = errno.ETXTBSY
|
|
|
|
message = "Destination dataset has modifications that can not be undone"
|
|
|
|
|
|
|
|
def __init__(self, name):
|
|
|
|
self.name = name
|
|
|
|
|
|
|
|
|
|
|
|
class BadStream(ZFSError):
|
2020-02-28 01:14:21 +00:00
|
|
|
errno = ECKSUM
|
2018-03-03 10:10:34 +00:00
|
|
|
message = "Bad backup stream"
|
|
|
|
|
|
|
|
|
|
|
|
class StreamFeatureNotSupported(ZFSError):
|
|
|
|
errno = errno.ENOTSUP
|
|
|
|
message = "Stream contains unsupported feature"
|
|
|
|
|
|
|
|
|
|
|
|
class UnknownStreamFeature(ZFSError):
|
|
|
|
errno = errno.ENOTSUP
|
|
|
|
message = "Unknown feature requested for stream"
|
|
|
|
|
|
|
|
|
Adopt pyzfs from ClusterHQ
This commit introduces several changes:
* Update LICENSE and project information
* Give a good PEP8 talk to existing Python source code
* Add RPM/DEB packaging for pyzfs
* Fix some outstanding issues with the existing pyzfs code caused by
changes in the ABI since the last time the code was updated
* Integrate pyzfs Python unittest with the ZFS Test Suite
* Add missing libzfs_core functions: lzc_change_key,
lzc_channel_program, lzc_channel_program_nosync, lzc_load_key,
lzc_receive_one, lzc_receive_resumable, lzc_receive_with_cmdprops,
lzc_receive_with_header, lzc_reopen, lzc_send_resume, lzc_sync,
lzc_unload_key, lzc_remap
Note: this commit slightly changes zfs_ioc_unload_key() ABI. This allow
to differentiate the case where we tried to unload a key on a
non-existing dataset (ENOENT) from the situation where a dataset has
no key loaded: this is consistent with the "change" case where trying
to zfs_ioc_change_key() from a dataset with no key results in EACCES.
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: loli10K <ezomori.nozomu@gmail.com>
Closes #7230
2018-03-18 08:34:45 +00:00
|
|
|
class StreamFeatureInvalid(ZFSError):
|
|
|
|
errno = errno.EINVAL
|
|
|
|
message = "Kernel modules must be upgraded to receive this stream"
|
|
|
|
|
|
|
|
|
|
|
|
class StreamFeatureIncompatible(ZFSError):
|
|
|
|
errno = errno.EINVAL
|
|
|
|
message = "Incompatible embedded feature with encrypted receive"
|
|
|
|
|
|
|
|
|
2020-03-17 17:30:33 +00:00
|
|
|
class StreamTruncated(ZFSError):
|
|
|
|
errno = zfs_errno.ZFS_ERR_STREAM_TRUNCATED
|
|
|
|
message = "incomplete stream"
|
2020-03-17 22:42:27 +00:00
|
|
|
|
2020-03-17 17:30:33 +00:00
|
|
|
|
Adopt pyzfs from ClusterHQ
This commit introduces several changes:
* Update LICENSE and project information
* Give a good PEP8 talk to existing Python source code
* Add RPM/DEB packaging for pyzfs
* Fix some outstanding issues with the existing pyzfs code caused by
changes in the ABI since the last time the code was updated
* Integrate pyzfs Python unittest with the ZFS Test Suite
* Add missing libzfs_core functions: lzc_change_key,
lzc_channel_program, lzc_channel_program_nosync, lzc_load_key,
lzc_receive_one, lzc_receive_resumable, lzc_receive_with_cmdprops,
lzc_receive_with_header, lzc_reopen, lzc_send_resume, lzc_sync,
lzc_unload_key, lzc_remap
Note: this commit slightly changes zfs_ioc_unload_key() ABI. This allow
to differentiate the case where we tried to unload a key on a
non-existing dataset (ENOENT) from the situation where a dataset has
no key loaded: this is consistent with the "change" case where trying
to zfs_ioc_change_key() from a dataset with no key results in EACCES.
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: loli10K <ezomori.nozomu@gmail.com>
Closes #7230
2018-03-18 08:34:45 +00:00
|
|
|
class ReceivePropertyFailure(MultipleOperationsFailure):
|
|
|
|
message = "Receiving of properties failed for one or more reasons"
|
|
|
|
|
|
|
|
def __init__(self, errors, suppressed_count):
|
|
|
|
super(ReceivePropertyFailure, self).__init__(errors, suppressed_count)
|
|
|
|
|
|
|
|
|
2018-03-03 10:10:34 +00:00
|
|
|
class StreamIOError(ZFSError):
|
|
|
|
message = "I/O error while writing or reading stream"
|
|
|
|
|
|
|
|
def __init__(self, errno):
|
|
|
|
self.errno = errno
|
|
|
|
|
|
|
|
|
|
|
|
class ZIOError(ZFSError):
|
|
|
|
errno = errno.EIO
|
|
|
|
message = "I/O error"
|
|
|
|
|
|
|
|
def __init__(self, name):
|
|
|
|
self.name = name
|
|
|
|
|
|
|
|
|
|
|
|
class NoSpace(ZFSError):
|
|
|
|
errno = errno.ENOSPC
|
|
|
|
message = "No space left"
|
|
|
|
|
|
|
|
def __init__(self, name):
|
|
|
|
self.name = name
|
|
|
|
|
|
|
|
|
|
|
|
class QuotaExceeded(ZFSError):
|
|
|
|
errno = errno.EDQUOT
|
2019-08-30 16:44:43 +00:00
|
|
|
message = "Quota exceeded"
|
2018-03-03 10:10:34 +00:00
|
|
|
|
|
|
|
def __init__(self, name):
|
|
|
|
self.name = name
|
|
|
|
|
|
|
|
|
|
|
|
class DatasetBusy(ZFSError):
|
|
|
|
errno = errno.EBUSY
|
|
|
|
message = "Dataset is busy"
|
|
|
|
|
|
|
|
def __init__(self, name):
|
|
|
|
self.name = name
|
|
|
|
|
|
|
|
|
|
|
|
class NameTooLong(ZFSError):
|
|
|
|
errno = errno.ENAMETOOLONG
|
|
|
|
message = "Dataset name is too long"
|
|
|
|
|
|
|
|
def __init__(self, name):
|
|
|
|
self.name = name
|
|
|
|
|
|
|
|
|
|
|
|
class NameInvalid(ZFSError):
|
|
|
|
errno = errno.EINVAL
|
|
|
|
message = "Invalid name"
|
|
|
|
|
|
|
|
def __init__(self, name):
|
|
|
|
self.name = name
|
|
|
|
|
|
|
|
|
|
|
|
class SnapshotNameInvalid(NameInvalid):
|
|
|
|
message = "Invalid name for snapshot"
|
|
|
|
|
|
|
|
def __init__(self, name):
|
|
|
|
self.name = name
|
|
|
|
|
|
|
|
|
|
|
|
class FilesystemNameInvalid(NameInvalid):
|
|
|
|
message = "Invalid name for filesystem or volume"
|
|
|
|
|
|
|
|
def __init__(self, name):
|
|
|
|
self.name = name
|
|
|
|
|
|
|
|
|
|
|
|
class BookmarkNameInvalid(NameInvalid):
|
|
|
|
message = "Invalid name for bookmark"
|
|
|
|
|
|
|
|
def __init__(self, name):
|
|
|
|
self.name = name
|
|
|
|
|
|
|
|
|
|
|
|
class ReadOnlyPool(ZFSError):
|
|
|
|
errno = errno.EROFS
|
|
|
|
message = "Pool is read-only"
|
|
|
|
|
|
|
|
def __init__(self, name):
|
|
|
|
self.name = name
|
|
|
|
|
|
|
|
|
|
|
|
class SuspendedPool(ZFSError):
|
|
|
|
errno = errno.EAGAIN
|
|
|
|
message = "Pool is suspended"
|
|
|
|
|
|
|
|
def __init__(self, name):
|
|
|
|
self.name = name
|
|
|
|
|
|
|
|
|
|
|
|
class PoolNotFound(ZFSError):
|
|
|
|
errno = errno.EXDEV
|
|
|
|
message = "No such pool"
|
|
|
|
|
|
|
|
def __init__(self, name):
|
|
|
|
self.name = name
|
|
|
|
|
|
|
|
|
|
|
|
class PoolsDiffer(ZFSError):
|
|
|
|
errno = errno.EXDEV
|
|
|
|
message = "Source and target belong to different pools"
|
|
|
|
|
|
|
|
def __init__(self, name):
|
|
|
|
self.name = name
|
|
|
|
|
|
|
|
|
|
|
|
class FeatureNotSupported(ZFSError):
|
|
|
|
errno = errno.ENOTSUP
|
|
|
|
message = "Feature is not supported in this version"
|
|
|
|
|
|
|
|
def __init__(self, name):
|
|
|
|
self.name = name
|
|
|
|
|
|
|
|
|
|
|
|
class PropertyNotSupported(ZFSError):
|
|
|
|
errno = errno.ENOTSUP
|
|
|
|
message = "Property is not supported in this version"
|
|
|
|
|
|
|
|
def __init__(self, name):
|
|
|
|
self.name = name
|
|
|
|
|
|
|
|
|
|
|
|
class PropertyInvalid(ZFSError):
|
|
|
|
errno = errno.EINVAL
|
|
|
|
message = "Invalid property or property value"
|
|
|
|
|
|
|
|
def __init__(self, name):
|
|
|
|
self.name = name
|
|
|
|
|
|
|
|
|
|
|
|
class DatasetTypeInvalid(ZFSError):
|
|
|
|
errno = errno.EINVAL
|
|
|
|
message = "Specified dataset type is unknown"
|
|
|
|
|
|
|
|
def __init__(self, name):
|
|
|
|
self.name = name
|
|
|
|
|
|
|
|
|
Adopt pyzfs from ClusterHQ
This commit introduces several changes:
* Update LICENSE and project information
* Give a good PEP8 talk to existing Python source code
* Add RPM/DEB packaging for pyzfs
* Fix some outstanding issues with the existing pyzfs code caused by
changes in the ABI since the last time the code was updated
* Integrate pyzfs Python unittest with the ZFS Test Suite
* Add missing libzfs_core functions: lzc_change_key,
lzc_channel_program, lzc_channel_program_nosync, lzc_load_key,
lzc_receive_one, lzc_receive_resumable, lzc_receive_with_cmdprops,
lzc_receive_with_header, lzc_reopen, lzc_send_resume, lzc_sync,
lzc_unload_key, lzc_remap
Note: this commit slightly changes zfs_ioc_unload_key() ABI. This allow
to differentiate the case where we tried to unload a key on a
non-existing dataset (ENOENT) from the situation where a dataset has
no key loaded: this is consistent with the "change" case where trying
to zfs_ioc_change_key() from a dataset with no key results in EACCES.
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: loli10K <ezomori.nozomu@gmail.com>
Closes #7230
2018-03-18 08:34:45 +00:00
|
|
|
class UnknownCryptCommand(ZFSError):
|
|
|
|
errno = errno.EINVAL
|
|
|
|
message = "Specified crypt command is invalid"
|
|
|
|
|
|
|
|
def __init__(self, name):
|
|
|
|
self.name = name
|
|
|
|
|
|
|
|
|
|
|
|
class EncryptionKeyNotLoaded(ZFSError):
|
|
|
|
errno = errno.EACCES
|
|
|
|
message = "Encryption key is not currently loaded"
|
|
|
|
|
|
|
|
|
|
|
|
class EncryptionKeyAlreadyLoaded(ZFSError):
|
|
|
|
errno = errno.EEXIST
|
|
|
|
message = "Encryption key is already loaded"
|
|
|
|
|
|
|
|
|
|
|
|
class EncryptionKeyInvalid(ZFSError):
|
|
|
|
errno = errno.EACCES
|
|
|
|
message = "Incorrect encryption key provided"
|
|
|
|
|
|
|
|
|
|
|
|
class ZCPError(ZFSError):
|
|
|
|
errno = None
|
|
|
|
message = None
|
|
|
|
|
|
|
|
|
|
|
|
class ZCPSyntaxError(ZCPError):
|
|
|
|
errno = errno.EINVAL
|
|
|
|
message = "Channel program contains syntax errors"
|
|
|
|
|
|
|
|
def __init__(self, details):
|
|
|
|
self.details = details
|
|
|
|
|
|
|
|
|
|
|
|
class ZCPRuntimeError(ZCPError):
|
2020-02-28 01:14:21 +00:00
|
|
|
errno = ECHRNG
|
Adopt pyzfs from ClusterHQ
This commit introduces several changes:
* Update LICENSE and project information
* Give a good PEP8 talk to existing Python source code
* Add RPM/DEB packaging for pyzfs
* Fix some outstanding issues with the existing pyzfs code caused by
changes in the ABI since the last time the code was updated
* Integrate pyzfs Python unittest with the ZFS Test Suite
* Add missing libzfs_core functions: lzc_change_key,
lzc_channel_program, lzc_channel_program_nosync, lzc_load_key,
lzc_receive_one, lzc_receive_resumable, lzc_receive_with_cmdprops,
lzc_receive_with_header, lzc_reopen, lzc_send_resume, lzc_sync,
lzc_unload_key, lzc_remap
Note: this commit slightly changes zfs_ioc_unload_key() ABI. This allow
to differentiate the case where we tried to unload a key on a
non-existing dataset (ENOENT) from the situation where a dataset has
no key loaded: this is consistent with the "change" case where trying
to zfs_ioc_change_key() from a dataset with no key results in EACCES.
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: loli10K <ezomori.nozomu@gmail.com>
Closes #7230
2018-03-18 08:34:45 +00:00
|
|
|
message = "Channel programs encountered a runtime error"
|
|
|
|
|
|
|
|
def __init__(self, details):
|
|
|
|
self.details = details
|
|
|
|
|
|
|
|
|
|
|
|
class ZCPLimitInvalid(ZCPError):
|
|
|
|
errno = errno.EINVAL
|
|
|
|
message = "Channel program called with invalid limits"
|
|
|
|
|
|
|
|
|
|
|
|
class ZCPTimeout(ZCPError):
|
2020-02-28 01:14:21 +00:00
|
|
|
errno = ETIME
|
Adopt pyzfs from ClusterHQ
This commit introduces several changes:
* Update LICENSE and project information
* Give a good PEP8 talk to existing Python source code
* Add RPM/DEB packaging for pyzfs
* Fix some outstanding issues with the existing pyzfs code caused by
changes in the ABI since the last time the code was updated
* Integrate pyzfs Python unittest with the ZFS Test Suite
* Add missing libzfs_core functions: lzc_change_key,
lzc_channel_program, lzc_channel_program_nosync, lzc_load_key,
lzc_receive_one, lzc_receive_resumable, lzc_receive_with_cmdprops,
lzc_receive_with_header, lzc_reopen, lzc_send_resume, lzc_sync,
lzc_unload_key, lzc_remap
Note: this commit slightly changes zfs_ioc_unload_key() ABI. This allow
to differentiate the case where we tried to unload a key on a
non-existing dataset (ENOENT) from the situation where a dataset has
no key loaded: this is consistent with the "change" case where trying
to zfs_ioc_change_key() from a dataset with no key results in EACCES.
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: loli10K <ezomori.nozomu@gmail.com>
Closes #7230
2018-03-18 08:34:45 +00:00
|
|
|
message = "Channel program timed out"
|
|
|
|
|
|
|
|
|
|
|
|
class ZCPSpaceError(ZCPError):
|
|
|
|
errno = errno.ENOSPC
|
|
|
|
message = "Channel program exhausted the memory limit"
|
|
|
|
|
|
|
|
|
|
|
|
class ZCPMemoryError(ZCPError):
|
|
|
|
errno = errno.ENOMEM
|
|
|
|
message = "Channel program return value too large"
|
|
|
|
|
|
|
|
|
|
|
|
class ZCPPermissionError(ZCPError):
|
|
|
|
errno = errno.EPERM
|
|
|
|
message = "Channel programs must be run as root"
|
|
|
|
|
|
|
|
|
2018-08-20 17:11:52 +00:00
|
|
|
class CheckpointExists(ZFSError):
|
|
|
|
errno = ZFS_ERR_CHECKPOINT_EXISTS
|
|
|
|
message = "Pool already has a checkpoint"
|
|
|
|
|
|
|
|
|
|
|
|
class CheckpointNotFound(ZFSError):
|
|
|
|
errno = ZFS_ERR_NO_CHECKPOINT
|
|
|
|
message = "Pool does not have a checkpoint"
|
|
|
|
|
|
|
|
|
|
|
|
class CheckpointDiscarding(ZFSError):
|
|
|
|
errno = ZFS_ERR_DISCARDING_CHECKPOINT
|
|
|
|
message = "Pool checkpoint is being discarded"
|
|
|
|
|
|
|
|
|
|
|
|
class DeviceRemovalRunning(ZFSError):
|
|
|
|
errno = ZFS_ERR_DEVRM_IN_PROGRESS
|
|
|
|
message = "A vdev is currently being removed"
|
|
|
|
|
|
|
|
|
|
|
|
class DeviceTooBig(ZFSError):
|
|
|
|
errno = ZFS_ERR_VDEV_TOO_BIG
|
|
|
|
message = "One or more top-level vdevs exceed the maximum vdev size"
|
|
|
|
|
|
|
|
|
RAID-Z expansion feature
This feature allows disks to be added one at a time to a RAID-Z group,
expanding its capacity incrementally. This feature is especially useful
for small pools (typically with only one RAID-Z group), where there
isn't sufficient hardware to add capacity by adding a whole new RAID-Z
group (typically doubling the number of disks).
== Initiating expansion ==
A new device (disk) can be attached to an existing RAIDZ vdev, by
running `zpool attach POOL raidzP-N NEW_DEVICE`, e.g. `zpool attach tank
raidz2-0 sda`. The new device will become part of the RAIDZ group. A
"raidz expansion" will be initiated, and the new device will contribute
additional space to the RAIDZ group once the expansion completes.
The `feature@raidz_expansion` on-disk feature flag must be `enabled` to
initiate an expansion, and it remains `active` for the life of the pool.
In other words, pools with expanded RAIDZ vdevs can not be imported by
older releases of the ZFS software.
== During expansion ==
The expansion entails reading all allocated space from existing disks in
the RAIDZ group, and rewriting it to the new disks in the RAIDZ group
(including the newly added device).
The expansion progress can be monitored with `zpool status`.
Data redundancy is maintained during (and after) the expansion. If a
disk fails while the expansion is in progress, the expansion pauses
until the health of the RAIDZ vdev is restored (e.g. by replacing the
failed disk and waiting for reconstruction to complete).
The pool remains accessible during expansion. Following a reboot or
export/import, the expansion resumes where it left off.
== After expansion ==
When the expansion completes, the additional space is available for use,
and is reflected in the `available` zfs property (as seen in `zfs list`,
`df`, etc).
Expansion does not change the number of failures that can be tolerated
without data loss (e.g. a RAIDZ2 is still a RAIDZ2 even after
expansion).
A RAIDZ vdev can be expanded multiple times.
After the expansion completes, old blocks remain with their old
data-to-parity ratio (e.g. 5-wide RAIDZ2, has 3 data to 2 parity), but
distributed among the larger set of disks. New blocks will be written
with the new data-to-parity ratio (e.g. a 5-wide RAIDZ2 which has been
expanded once to 6-wide, has 4 data to 2 parity). However, the RAIDZ
vdev's "assumed parity ratio" does not change, so slightly less space
than is expected may be reported for newly-written blocks, according to
`zfs list`, `df`, `ls -s`, and similar tools.
Sponsored-by: The FreeBSD Foundation
Sponsored-by: iXsystems, Inc.
Sponsored-by: vStack
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Reviewed-by: Mark Maybee <mark.maybee@delphix.com>
Authored-by: Matthew Ahrens <mahrens@delphix.com>
Contributions-by: Fedor Uporov <fuporov.vstack@gmail.com>
Contributions-by: Stuart Maybee <stuart.maybee@comcast.net>
Contributions-by: Thorsten Behrens <tbehrens@outlook.com>
Contributions-by: Fmstrat <nospam@nowsci.com>
Contributions-by: Don Brady <dev.fs.zfs@gmail.com>
Signed-off-by: Don Brady <dev.fs.zfs@gmail.com>
Closes #15022
2023-11-08 18:19:41 +00:00
|
|
|
class RaidzExpansionRunning(ZFSError):
|
|
|
|
errno = ZFS_ERR_RAIDZ_EXPAND_IN_PROGRESS
|
|
|
|
message = "A raidz device is currently expanding"
|
|
|
|
|
|
|
|
|
2018-03-03 10:10:34 +00:00
|
|
|
# vim: softtabstop=4 tabstop=4 expandtab shiftwidth=4
|