setting a volsize larger than the space available sometimes succeeds
If you try to set the volsize of a non-sparse zvol larger than the space available the system should return ENOSPC. However, some of the calculations in this code path are always done with the default block size (8k) rather than the zvol's actual block size, which causes ZFS to believe that the zvol is a sparse zvol and allowing you to set the volsize to any value, regardless of the space available in the pool.
Updated by Christopher Siden almost 9 years ago
- Status changed from In Progress to Closed
commit c61ea56 Author: George Wilson <email@example.com> Date: Wed Feb 20 22:50:16 2013 3557 dumpvp_size is not updated correctly when a dump zvol's size is changed 3558 setting the volsize on a dump device does not return back ENOSPC 3559 setting a volsize larger than the space available sometimes succeeds 3560 dumpadm should be able to remove a dump device Reviewed by: Adam Leventhal <firstname.lastname@example.org> Reviewed by: Matthew Ahrens <email@example.com> Reviewed by: Christopher Siden <firstname.lastname@example.org> Approved by: Albert Lee <email@example.com>