Bug #4951
ZFS administrative commands should use reserved space, not fail with ENOSPC
| Status: | Closed | Start date: | 2014-07-01 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Matthew Ahrens | % Done: | 100% | |
| Category: | zfs - Zettabyte File System | |||
| Target version: | - | |||
| Difficulty: | Medium | Tags: | needs-triage |
Description
We should allow rollbacks when we have less than the 1.6% reserved
"slop" space, but not when we have less than 0.8% "super
reserved" space. On reasonable sized pools, this should allow enough rollbacks
before the stack gets to deleting/rolling back something big that results in
substantially more free space.
We will apply this "super reserved" space for all
administrative actions. I.e. ZPL/zvol access (e.g. write() system calls) would
get ENOSPC when the pool has <1.6% free space, but administrative commands
(e.g. rollback, zfs set, etc) would not get ENOSPC until there is <0.8% free
space.
History
#1
Updated by Electric Monk about 2 years ago
- % Done changed from 0 to 100
- Status changed from New to Closed
git commit 7d46dc6ca63a6f3f0d51aa655bfcf10cf2405a9e
commit 7d46dc6ca63a6f3f0d51aa655bfcf10cf2405a9e
Author: Matthew Ahrens <mahrens@delphix.com>
Date: 2014-07-09T04:49:57.000Z
4951 ZFS administrative commands should use reserved space, not fail with ENOSPC
Reviewed by: John Kennedy <john.kennedy@delphix.com>
Reviewed by: George Wilson <george.wilson@delphix.com>
Reviewed by: Christopher Siden <christopher.siden@delphix.com>
Reviewed by: Dan McDonald <danmcd@omniti.com>
Approved by: Garrett D'Amore <garrett@damore.org>
#2
Updated by Electric Monk about 2 years ago
git commit c39f2c8cacf297ec37acd421f4c4fec127991995
commit c39f2c8cacf297ec37acd421f4c4fec127991995
Author: Christopher Siden <chris@delphix.com>
Date: 2014-07-11T02:57:59.000Z
4951 ZFS administrative commands should use reserved space, not fail with ENOSPC (fix call)
Approved by: Christopher Siden <christopher.siden@delphix.com>
Also available in: Atom