summaryrefslogtreecommitdiffstats
path: root/sys/kern/subr_smp.c
diff options
context:
space:
mode:
authormckusick <mckusick@FreeBSD.org>2000-01-13 07:17:39 +0000
committermckusick <mckusick@FreeBSD.org>2000-01-13 07:17:39 +0000
commit28d13b9ecffd9565cf62780e302268170cb6fb75 (patch)
treea68ae3e316c47e097e73934c4c9eea5c8c12f70a /sys/kern/subr_smp.c
parent93d3303e02611de4dd3ea6d2ed1b44f55f354b03 (diff)
downloadFreeBSD-src-28d13b9ecffd9565cf62780e302268170cb6fb75.zip
FreeBSD-src-28d13b9ecffd9565cf62780e302268170cb6fb75.tar.gz
A panic occurs during an fsync when a dirty block associated with
a vnode has not been written (which would clear certain of its dependencies). The problems arises because fsync with MNT_NOWAIT no longer pushes all the dirty blocks associated with a vnode. It skips those that require rollbacks, since they will just get instantly dirty again. Such skipped blocks are marked so that they will not be skipped a second time (otherwise circular dependencies would never clear). So, we fsync twice to ensure that everything will be written at least once.
Diffstat (limited to 'sys/kern/subr_smp.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud