]> git.proxmox.com Git - mirror_zfs.git/commit - module/zfs/zfs_vnops.c
Illumos 4950 - files sometimes can't be removed from a full filesystem
authorMatthew Ahrens <mahrens@delphix.com>
Mon, 7 Jul 2014 19:49:36 +0000 (11:49 -0800)
committerBrian Behlendorf <behlendorf1@llnl.gov>
Fri, 22 Jan 2016 00:59:30 +0000 (16:59 -0800)
commit19d55079aecb5c022c1c09e0eace4f7da7381a62
treed22e2fb923c8d11af9429346e69729ac98701eb9
parentdfe0d027344b8534c69cc902c71ae912d8759e12
Illumos 4950 - files sometimes can't be removed from a full filesystem

4950 files sometimes can't be removed from a full filesystem
Reviewed by: Adam Leventhal <adam.leventhal@delphix.com>
Reviewed by: George Wilson <george.wilson@delphix.com>
Reviewed by: Sebastien Roy <sebastien.roy@delphix.com>
Reviewed by: Boris Protopopov <bprotopopov@hotmail.com>
Approved by: Dan McDonald <danmcd@omniti.com>

References:
  https://www.illumos.org/issues/4950
  https://github.com/illumos/illumos-gate/commit/4bb7380

Porting notes:
- ZoL currently does not log discards to zvols, so the portion of
  this patch that modifies the discard logging to mark it as
  freeing space has been discarded.

2. may_delete_now had been removed from zfs_remove() in ZoL.
   It has been reintroduced.

3. We do not try to emulate vnodes, so the following lines are
   not valid on Linux:

mutex_enter(&vp->v_lock);
may_delete_now = vp->v_count == 1 && !vn_has_cached_data(vp);
mutex_exit(&vp->v_lock);

  This has been replaced with:

mutex_enter(&zp->z_lock);
may_delete_now = atomic_read(&ip->i_count) == 1 && !(zp->z_is_mapped);
mutex_exit(&zp->z_lock);

Ported-by: Richard Yao <richard.yao@clusterhq.com>
Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov>
include/sys/dmu.h
module/zfs/dmu.c
module/zfs/dmu_tx.c
module/zfs/zfs_dir.c
module/zfs/zfs_vnops.c
module/zfs/zfs_znode.c
module/zfs/zvol.c