xfs: rework log quiesce to cover the log
v2 cover xfs: rework log quiesce to cover the log
Hi all,
Here's a v2 of the log quiesce rework to introduce and reuse log covering. This only has a couple minor tweaks from v1. Note again that patch 1 is an isolated bug fix related to the lazy sb accounting bug generic/388 was recently enhanced to reproduce.
Brian
v2:
- Return bool from xfs_log_need_covered().
- Reword patch 1 commit log.
- Apply review tags.
v1: https://lore.kernel.org/linux-xfs/[email protected]/
Brian Foster (9):
xfs: sync lazy sb accounting on quiesce of read-only mounts
xfs: lift writable fs check up into log worker task
xfs: separate log cleaning from log quiesce
xfs: cover the log during log quiesce
xfs: don't reset log idle state on covering checkpoints
xfs: fold sbcount quiesce logging into log covering
xfs: remove duplicate wq cancel and log force from attr quiesce
xfs: remove xfs_quiesce_attr()
xfs: cover the log on freeze instead of cleaning it
fs/xfs/xfs_log.c | 128 ++++++++++++++++++++++++++++++++++++--------- fs/xfs/xfs_log.h | 4 +- fs/xfs/xfs_mount.c | 34 +----------- fs/xfs/xfs_mount.h | 1 - fs/xfs/xfs_super.c | 38 +------------- 5 files changed, 109 insertions(+), 96 deletions(-)
Signature · 1 line
2.26.2
PATCH v2 1/9 xfs: sync lazy sb accounting on quiesce of read-only mounts
xfs_log_sbcount() syncs the superblock specifically to accumulate the in-core percpu superblock counters and commit them to disk. This is required to maintain filesystem consistency across quiesce (freeze, read-only mount/remount) or unmount when lazy superblock accounting is enabled because individual transactions do not update the superblock directly.
This mechanism works as expected for writable mounts, but xfs_log_sbcount() skips the update for read-only mounts. Read-only mounts otherwise still allow log recovery and write out an unmount record during log quiesce. If a read-only mount performs log recovery, it can modify the in-core superblock counters and write an unmount record when the filesystem unmounts without ever syncing the in-core counters. This leaves the filesystem with a clean log but in an inconsistent state with regard to lazy sb counters.
Update xfs_log_sbcount() to use the same logic xfs_log_unmount_write() uses to determine when to write an unmount record. This ensures that lazy accounting is always synced before the log is cleaned. Refactor this logic into a new helper to distinguish between a writable filesystem and a writable log. Specifically, the log is writable unless the filesystem is mounted with the norecovery mount option, the underlying log device is read-only, or the filesystem is shutdown. Drop the freeze state check because the update is already allowed during the freezing process and no context calls this function on an already frozen fs. Also, retain the shutdown check in xfs_log_unmount_write() to catch the case where the preceding log force might have triggered a shutdown.
--- fs/xfs/xfs_log.c | 28 ++++++++++++++++++++-------- fs/xfs/xfs_log.h | 1 + fs/xfs/xfs_mount.c | 3 +-- 3 files changed, 22 insertions(+), 10 deletions(-)
fs/xfs/xfs_log.c +20 -8
@@ -347,6 +347,25 @@ xlog_tic_add_region(xlog_ticket_t *tic, uint len, uint type) tic->t_res_num++; } +bool +xfs_log_writable ( +struct xfs_mount *mp) +{ +/* +* Never write to the log on norecovery mounts, if the block device is +* read-only, or if the filesystem is shutdown. Read-only mounts still +* allow internal writes for log recovery and unmount purposes, so don't +* restrict that case here. +*/ +if (mp->m_flags &XFS_MOUNT_NORECOVERY ) +return false; +if (xfs_readonly_buftarg (mp->m_log->l_targ)) +return false; +if (XFS_FORCED_SHUTDOWN (mp)) +return false; +return true; +} +/* * Replenish the byte reservation required by moving the grant write head. */
@@ -886,15 +905,8 @@ xfs_log_unmount_write( {struct xlog *log = mp->m_log; -/* -* Don't write out unmount record on norecovery mounts or ro devices. -* Or, if we are doing a forced umount (typically because of IO errors). -*/ -if (mp->m_flags &XFS_MOUNT_NORECOVERY || -xfs_readonly_buftarg (log->l_targ)) { -ASSERT (mp->m_flags &XFS_MOUNT_RDONLY ); +if (!xfs_log_writable (mp))return ; - }xfs_log_force (mp,XFS_LOG_SYNC );
fs/xfs/xfs_log.h +1 -0
@@ -127,6 +127,7 @@ int xfs_log_reserve(struct xfs_mount *mp,int xfs_log_regrant (struct xfs_mount *mp,struct xlog_ticket *tic);void xfs_log_unmount (struct xfs_mount *mp);int xfs_log_force_umount (struct xfs_mount *mp,int logerror); +bool xfs_log_writable (struct xfs_mount *mp);struct xlog_ticket *xfs_log_ticket_get (struct xlog_ticket *ticket);void xfs_log_ticket_put (struct xlog_ticket *ticket);
fs/xfs/xfs_mount.c +1 -2
@@ -1176,8 +1176,7 @@ xfs_fs_writable(int xfs_log_sbcount (xfs_mount_t *mp) { -/* allow this to proceed during the freeze sequence... */ -if (!xfs_fs_writable (mp,SB_FREEZE_COMPLETE )) +if (!xfs_log_writable (mp))return 0 ;/*
Signature · 1 line
2.26.2
PATCH v2 2/9 xfs: lift writable fs check up into log worker task
In reply to Brian FosterThe log covering helper checks whether the filesystem is writable to determine whether to cover the log. The helper is currently only called from the background log worker. In preparation to reuse the helper from freezing contexts, lift the check into xfs_log_worker().
--- fs/xfs/xfs_log.c | 18 ++++++++---------- 1 file changed, 8 insertions(+), 10 deletions(-)
fs/xfs/xfs_log.c +8 -10
@@ -1049,14 +1049,12 @@ xfs_log_space_wake(* there's no point in running a dummy transaction at this point because we * can't start trying to idle the log until both the CIL and AIL are empty. */ -static int -xfs_log_need_covered (xfs_mount_t *mp) +static bool +xfs_log_need_covered ( +struct xfs_mount *mp) { -struct xlog *log = mp->m_log; -int needed =0 ; - -if (!xfs_fs_writable (mp,SB_FREEZE_WRITE )) -return 0 ; +struct xlog *log = mp->m_log; +bool needed = false;if (!xlog_cil_empty (log))return 0 ;
@@ -1074,14 +1072,14 @@ xfs_log_need_covered(xfs_mount_t *mp)if (!xlog_iclogs_empty (log))break ; - needed =1 ; + needed = true;if (log->l_covered_state ==XLOG_STATE_COVER_NEED ) log->l_covered_state =XLOG_STATE_COVER_DONE ;else log->l_covered_state =XLOG_STATE_COVER_DONE2 ;break ;default : - needed =1 ; + needed = true;break ; }spin_unlock (&log->l_icloglock);
@@ -1271,7 +1269,7 @@ xfs_log_worker(struct xfs_mount *mp = log->l_mp;/* dgc: errors ignored - not fatal and nowhere to report them */ -if (xfs_log_need_covered (mp)) { +if (xfs_fs_writable (mp,SB_FREEZE_WRITE ) &&xfs_log_need_covered (mp)) {/* * Dump a transaction into the log that contains no real change. * This is needed to stamp the current tail LSN into the log
Signature · 1 line
2.26.2
Re: [PATCH v2 2/9] xfs: lift writable fs check up into log worker task
Quoted 8 lines · Brian Foster
The log covering helper checks whether the filesystem is writable to determine whether to cover the log. The helper is currently only called from the background log worker. In preparation to reuse the helper from freezing contexts, lift the check into
xfs_log_worker().Signed-off-by Brian Foster <[email protected]>Reviewed-by Allison Henderson <[email protected]>Reviewed-by Christoph Hellwig <[email protected]>
Looks good to me,
--D
Quoted 57 lines
--- fs/xfs/xfs_log.c | 18 ++++++++---------- 1 file changed, 8 insertions(+), 10 deletions(-)fs/xfs/xfs_log.c +8
-10@@ -1049,14 +1049,12 @@ xfs_log_space_wake(* there's no point in running a dummy transaction at this point because we * can't start trying to idle the log until both the CIL and AIL are empty. */ -static int -xfs_log_need_covered (xfs_mount_t *mp) +static bool +xfs_log_need_covered ( +struct xfs_mount *mp) { -struct xlog *log = mp->m_log; -int needed =0 ; - -if (!xfs_fs_writable (mp,SB_FREEZE_WRITE )) -return 0 ; +struct xlog *log = mp->m_log; +bool needed = false;if (!xlog_cil_empty (log))return 0 ;@@ -1074,14 +1072,14 @@ xfs_log_need_covered(xfs_mount_t *mp)if (!xlog_iclogs_empty (log))break ; - needed =1 ; + needed = true;if (log->l_covered_state ==XLOG_STATE_COVER_NEED ) log->l_covered_state =XLOG_STATE_COVER_DONE ;else log->l_covered_state =XLOG_STATE_COVER_DONE2 ;break ;default : - needed =1 ; + needed = true;break ; }spin_unlock (&log->l_icloglock);@@ -1271,7 +1269,7 @@ xfs_log_worker(struct xfs_mount *mp = log->l_mp;/* dgc: errors ignored - not fatal and nowhere to report them */ -if (xfs_log_need_covered (mp)) { +if (xfs_fs_writable (mp,SB_FREEZE_WRITE ) &&xfs_log_need_covered (mp)) {/* * Dump a transaction into the log that contains no real change. * This is needed to stamp the current tail LSN into the log Signature · 1 line
2.26.2
PATCH v2 3/9 xfs: separate log cleaning from log quiesce
In reply to Brian FosterLog quiesce is currently associated with cleaning the log, which is accomplished by writing an unmount record as the last step of the quiesce sequence. The quiesce codepath is a bit convoluted in this regard due to how it is reused from various contexts. In preparation to create separate log cleaning and log covering interfaces, lift the write of the unmount record into a new cleaning helper and call that wherever xfs_log_quiesce() is currently invoked. No functional changes.
--- fs/xfs/xfs_log.c | 8 +++++++- fs/xfs/xfs_log.h | 1 + fs/xfs/xfs_super.c | 2 +- 3 files changed, 9 insertions(+), 2 deletions(-)
fs/xfs/xfs_log.c +7 -1
@@ -957,7 +957,13 @@ xfs_log_quiesce(xfs_wait_buftarg (mp->m_ddev_targp);xfs_buf_lock (mp->m_sb_bp);xfs_buf_unlock (mp->m_sb_bp); +} +void +xfs_log_clean ( +struct xfs_mount *mp) +{ +xfs_log_quiesce (mp);xfs_log_unmount_write (mp); }
@@ -972,7 +978,7 @@ voidxfs_log_unmount ( struct xfs_mount *mp) { -xfs_log_quiesce (mp); +xfs_log_clean (mp);xfs_trans_ail_destroy (mp);
fs/xfs/xfs_log.h +1 -0
@@ -139,6 +139,7 @@ bool xfs_log_item_in_current_chkpt(struct xfs_log_item *lip);void xfs_log_work_queue (struct xfs_mount *mp);void xfs_log_quiesce (struct xfs_mount *mp); +void xfs_log_clean (struct xfs_mount *mp);bool xfs_log_check_lsn (struct xfs_mount *,xfs_lsn_t );bool xfs_log_in_recovery (struct xfs_mount *);
fs/xfs/xfs_super.c +1 -1
@@ -897,7 +897,7 @@ xfs_quiesce_attr(if (error)xfs_warn (mp,"xfs_attr_quiesce: failed to log sb changes. " "Frozen image may not be consistent." ); -xfs_log_quiesce (mp); +xfs_log_clean (mp); }/*
Signature · 1 line
2.26.2
PATCH v2 4/9 xfs: cover the log during log quiesce
In reply to Brian FosterThe log quiesce mechanism historically terminates by marking the log clean with an unmount record. The primary objective is to indicate that log recovery is no longer required after the quiesce has flushed all in-core changes and written back filesystem metadata. While this is perfectly fine, it is somewhat hacky as currently used in certain contexts. For example, filesystem freeze quiesces (i.e. cleans) the log and immediately redirties it with a dummy superblock transaction to ensure that log recovery runs in the event of a crash.
While this functions correctly, cleaning the log from freeze context is clearly superfluous given the current redirtying behavior. Instead, the desired behavior can be achieved by simply covering the log. This effectively retires all on-disk log items from the active range of the log by issuing two synchronous and sequential dummy superblock update transactions that serve to update the on-disk log head and tail. The subtle difference is that the log technically remains dirty due to the lack of an unmount record, though recovery is effectively a no-op due to the content of the checkpoints being clean (i.e. the unmodified on-disk superblock).
Log covering currently runs in the background and only triggers once the filesystem and log has idled. The purpose of the background mechanism is to prevent log recovery from replaying the most recently logged items long after those items may have been written back. In the quiesce path, the log has been deliberately idled by forcing the log and pushing the AIL until empty in a context where no further mutable filesystem operations are allowed. Therefore, we can cover the log as the final step in the log quiesce codepath to reflect that all previously active items have been successfully written back.
This facilitates selective log covering from certain contexts (i.e. freeze) that only seek to quiesce, but not necessarily clean the log. Note that as a side effect of this change, log covering now occurs when cleaning the log as well. This is harmless, facilitates subsequent cleanups, and is mostly temporary as various operations switch to use explicit log covering.
--- fs/xfs/xfs_log.c | 49 +++++++++++++++++++++++++++++++++++++++++++++--- fs/xfs/xfs_log.h | 2 +- 2 files changed, 47 insertions(+), 4 deletions(-)
fs/xfs/xfs_log.c +46 -3
@@ -91,6 +91,9 @@ STATIC intxlog_iclogs_empty ( struct xlog *log); +static int +xfs_log_cover (struct xfs_mount *); + static void xlog_grant_sub_space( struct xlog *log,
@@ -936,10 +939,9 @@ xfs_log_unmount_write(* To do this, we first need to shut down the background log work so it is not * trying to cover the log as we clean up. We then need to unpin all objects in * the log so we can then flush them out. Once they have completed their IO and -* run the callbacks removing themselves from the AIL, we can write the unmount -* record. +* run the callbacks removing themselves from the AIL, we can cover the log. */ -void +int xfs_log_quiesce (struct xfs_mount *mp) {
@@ -957,6 +959,8 @@ xfs_log_quiesce(xfs_wait_buftarg (mp->m_ddev_targp);xfs_buf_lock (mp->m_sb_bp);xfs_buf_unlock (mp->m_sb_bp); + +return xfs_log_cover (mp); }void
@@ -1092,6 +1096,45 @@ xfs_log_need_covered(return needed; } +/* +* Explicitly cover the log. This is similar to background log covering but +* intended for usage in quiesce codepaths. The caller is responsible to ensure +* the log is idle and suitable for covering. The CIL, iclog buffers and AIL +* must all be empty. +*/ +static int +xfs_log_cover ( +struct xfs_mount *mp) +{ +struct xlog *log = mp->m_log; +int error =0 ; + +ASSERT ((xlog_cil_empty (log) &&xlog_iclogs_empty (log) && + !xfs_ail_min_lsn (log->l_ailp)) || +XFS_FORCED_SHUTDOWN (mp)); + +if (!xfs_log_writable (mp)) +return 0 ; + +/* +* To cover the log, commit the superblock twice (at most) in +* independent checkpoints. The first serves as a reference for the +* tail pointer. The sync transaction and AIL push empties the AIL and +* updates the in-core tail to the LSN of the first checkpoint. The +* second commit updates the on-disk tail with the in-core LSN, +* covering the log. Push the AIL one more time to leave it empty, as +* we found it. +*/ +while (xfs_log_need_covered (mp)) { + error =xfs_sync_sb (mp, true); +if (error) +break ; +xfs_ail_push_all_sync (mp->m_ail); + } + +return error; +} +/* * We may be holding the log iclog lock upon entering this routine. */
fs/xfs/xfs_log.h +1 -1
@@ -138,7 +138,7 @@ void xlog_cil_process_committed(struct list_head *list);bool xfs_log_item_in_current_chkpt (struct xfs_log_item *lip);void xfs_log_work_queue (struct xfs_mount *mp); -void xfs_log_quiesce (struct xfs_mount *mp); +int xfs_log_quiesce (struct xfs_mount *mp);void xfs_log_clean (struct xfs_mount *mp);bool xfs_log_check_lsn (struct xfs_mount *,xfs_lsn_t );bool xfs_log_in_recovery (struct xfs_mount *);
Signature · 1 line
2.26.2
Re: [PATCH v2 4/9] xfs: cover the log during log quiesce
Quoted 39 lines · Brian Foster
The log quiesce mechanism historically terminates by marking the log clean with an unmount record. The primary objective is to indicate that log recovery is no longer required after the quiesce has flushed all in-core changes and written back filesystem metadata. While this is perfectly fine, it is somewhat hacky as currently used in certain contexts. For example, filesystem freeze quiesces (i.e. cleans) the log and immediately redirties it with a dummy superblock transaction to ensure that log recovery runs in the event of a crash.
While this functions correctly, cleaning the log from freeze context is clearly superfluous given the current redirtying behavior. Instead, the desired behavior can be achieved by simply covering the log. This effectively retires all on-disk log items from the active range of the log by issuing two synchronous and sequential dummy superblock update transactions that serve to update the on-disk log head and tail. The subtle difference is that the log technically remains dirty due to the lack of an unmount record, though recovery is effectively a no-op due to the content of the checkpoints being clean (i.e. the unmodified on-disk superblock).
Log covering currently runs in the background and only triggers once the filesystem and log has idled. The purpose of the background mechanism is to prevent log recovery from replaying the most recently logged items long after those items may have been written back. In the quiesce path, the log has been deliberately idled by forcing the log and pushing the AIL until empty in a context where no further mutable filesystem operations are allowed. Therefore, we can cover the log as the final step in the log quiesce codepath to reflect that all previously active items have been successfully written back.
This facilitates selective log covering from certain contexts (i.e. freeze) that only seek to quiesce, but not necessarily clean the log. Note that as a side effect of this change, log covering now occurs when cleaning the log as well. This is harmless, facilitates subsequent cleanups, and is mostly temporary as various operations switch to use explicit log covering.
Quoted 2 lines
Signed-off-by Brian Foster <[email protected]>Reviewed-by Christoph Hellwig <[email protected]>
Looks good,
--D
Quoted 103 lines
--- fs/xfs/xfs_log.c | 49 +++++++++++++++++++++++++++++++++++++++++++++--- fs/xfs/xfs_log.h | 2 +- 2 files changed, 47 insertions(+), 4 deletions(-)fs/xfs/xfs_log.c +46
-3@@ -91,6 +91,9 @@ STATIC intxlog_iclogs_empty ( struct xlog *log); +static int +xfs_log_cover (struct xfs_mount *); + static void xlog_grant_sub_space( struct xlog *log,@@ -936,10 +939,9 @@ xfs_log_unmount_write(* To do this, we first need to shut down the background log work so it is not * trying to cover the log as we clean up. We then need to unpin all objects in * the log so we can then flush them out. Once they have completed their IO and -* run the callbacks removing themselves from the AIL, we can write the unmount -* record. +* run the callbacks removing themselves from the AIL, we can cover the log. */ -void +int xfs_log_quiesce (struct xfs_mount *mp) {@@ -957,6 +959,8 @@ xfs_log_quiesce(xfs_wait_buftarg (mp->m_ddev_targp);xfs_buf_lock (mp->m_sb_bp);xfs_buf_unlock (mp->m_sb_bp); + +return xfs_log_cover (mp); }void @@ -1092,6 +1096,45 @@ xfs_log_need_covered(return needed; } +/* +* Explicitly cover the log. This is similar to background log covering but +* intended for usage in quiesce codepaths. The caller is responsible to ensure +* the log is idle and suitable for covering. The CIL, iclog buffers and AIL +* must all be empty. +*/ +static int +xfs_log_cover ( +struct xfs_mount *mp) +{ +struct xlog *log = mp->m_log; +int error =0 ; + +ASSERT ((xlog_cil_empty (log) &&xlog_iclogs_empty (log) && + !xfs_ail_min_lsn (log->l_ailp)) || +XFS_FORCED_SHUTDOWN (mp)); + +if (!xfs_log_writable (mp)) +return 0 ; + +/* +* To cover the log, commit the superblock twice (at most) in +* independent checkpoints. The first serves as a reference for the +* tail pointer. The sync transaction and AIL push empties the AIL and +* updates the in-core tail to the LSN of the first checkpoint. The +* second commit updates the on-disk tail with the in-core LSN, +* covering the log. Push the AIL one more time to leave it empty, as +* we found it. +*/ +while (xfs_log_need_covered (mp)) { + error =xfs_sync_sb (mp, true); +if (error) +break ; +xfs_ail_push_all_sync (mp->m_ail); + } + +return error; +} +/* * We may be holding the log iclog lock upon entering this routine. */ fs/xfs/xfs_log.h +1
-1@@ -138,7 +138,7 @@ void xlog_cil_process_committed(struct list_head *list);bool xfs_log_item_in_current_chkpt (struct xfs_log_item *lip);void xfs_log_work_queue (struct xfs_mount *mp); -void xfs_log_quiesce (struct xfs_mount *mp); +int xfs_log_quiesce (struct xfs_mount *mp);void xfs_log_clean (struct xfs_mount *mp);bool xfs_log_check_lsn (struct xfs_mount *,xfs_lsn_t );bool xfs_log_in_recovery (struct xfs_mount *);Signature · 1 line
2.26.2
Re: [PATCH v2 4/9] xfs: cover the log during log quiesce
In reply to Brian FosterQuoted 39 lines · Brian Foster
The log quiesce mechanism historically terminates by marking the log clean with an unmount record. The primary objective is to indicate that log recovery is no longer required after the quiesce has flushed all in-core changes and written back filesystem metadata. While this is perfectly fine, it is somewhat hacky as currently used in certain contexts. For example, filesystem freeze quiesces (i.e. cleans) the log and immediately redirties it with a dummy superblock transaction to ensure that log recovery runs in the event of a crash.
While this functions correctly, cleaning the log from freeze context is clearly superfluous given the current redirtying behavior. Instead, the desired behavior can be achieved by simply covering the log. This effectively retires all on-disk log items from the active range of the log by issuing two synchronous and sequential dummy superblock update transactions that serve to update the on-disk log head and tail. The subtle difference is that the log technically remains dirty due to the lack of an unmount record, though recovery is effectively a no-op due to the content of the checkpoints being clean (i.e. the unmodified on-disk superblock).
Log covering currently runs in the background and only triggers once the filesystem and log has idled. The purpose of the background mechanism is to prevent log recovery from replaying the most recently logged items long after those items may have been written back. In the quiesce path, the log has been deliberately idled by forcing the log and pushing the AIL until empty in a context where no further mutable filesystem operations are allowed. Therefore, we can cover the log as the final step in the log quiesce codepath to reflect that all previously active items have been successfully written back.
This facilitates selective log covering from certain contexts (i.e. freeze) that only seek to quiesce, but not necessarily clean the log. Note that as a side effect of this change, log covering now occurs when cleaning the log as well. This is harmless, facilitates subsequent cleanups, and is mostly temporary as various operations switch to use explicit log covering.
Quoted 2 lines
Signed-off-by Brian Foster <[email protected]>Reviewed-by Christoph Hellwig <[email protected]>
Ok, makes sense
Quoted 101 lines
--- fs/xfs/xfs_log.c | 49 +++++++++++++++++++++++++++++++++++++++++++++--- fs/xfs/xfs_log.h | 2 +- 2 files changed, 47 insertions(+), 4 deletions(-)fs/xfs/xfs_log.c +46
-3@@ -91,6 +91,9 @@ STATIC intxlog_iclogs_empty ( struct xlog *log); +static int +xfs_log_cover (struct xfs_mount *); + static void xlog_grant_sub_space( struct xlog *log,@@ -936,10 +939,9 @@ xfs_log_unmount_write(* To do this, we first need to shut down the background log work so it is not * trying to cover the log as we clean up. We then need to unpin all objects in * the log so we can then flush them out. Once they have completed their IO and -* run the callbacks removing themselves from the AIL, we can write the unmount -* record. +* run the callbacks removing themselves from the AIL, we can cover the log. */ -void +int xfs_log_quiesce (struct xfs_mount *mp) {@@ -957,6 +959,8 @@ xfs_log_quiesce(xfs_wait_buftarg (mp->m_ddev_targp);xfs_buf_lock (mp->m_sb_bp);xfs_buf_unlock (mp->m_sb_bp); + +return xfs_log_cover (mp); }void @@ -1092,6 +1096,45 @@ xfs_log_need_covered(return needed; } +/* +* Explicitly cover the log. This is similar to background log covering but +* intended for usage in quiesce codepaths. The caller is responsible to ensure +* the log is idle and suitable for covering. The CIL, iclog buffers and AIL +* must all be empty. +*/ +static int +xfs_log_cover ( +struct xfs_mount *mp) +{ +struct xlog *log = mp->m_log; +int error =0 ; + +ASSERT ((xlog_cil_empty (log) &&xlog_iclogs_empty (log) && + !xfs_ail_min_lsn (log->l_ailp)) || +XFS_FORCED_SHUTDOWN (mp)); + +if (!xfs_log_writable (mp)) +return 0 ; + +/* +* To cover the log, commit the superblock twice (at most) in +* independent checkpoints. The first serves as a reference for the +* tail pointer. The sync transaction and AIL push empties the AIL and +* updates the in-core tail to the LSN of the first checkpoint. The +* second commit updates the on-disk tail with the in-core LSN, +* covering the log. Push the AIL one more time to leave it empty, as +* we found it. +*/ +while (xfs_log_need_covered (mp)) { + error =xfs_sync_sb (mp, true); +if (error) +break ; +xfs_ail_push_all_sync (mp->m_ail); + } + +return error; +} +/* * We may be holding the log iclog lock upon entering this routine. */ fs/xfs/xfs_log.h +1
-1@@ -138,7 +138,7 @@ void xlog_cil_process_committed(struct list_head *list);bool xfs_log_item_in_current_chkpt (struct xfs_log_item *lip);void xfs_log_work_queue (struct xfs_mount *mp); -void xfs_log_quiesce (struct xfs_mount *mp); +int xfs_log_quiesce (struct xfs_mount *mp);void xfs_log_clean (struct xfs_mount *mp);bool xfs_log_check_lsn (struct xfs_mount *,xfs_lsn_t );bool xfs_log_in_recovery (struct xfs_mount *);
PATCH v2 5/9 xfs: don't reset log idle state on covering checkpoints
In reply to Brian FosterNow that log covering occurs on quiesce, we'd like to reuse the underlying superblock sync for final superblock updates. This includes things like lazy superblock counter updates, log feature incompat bits in the future, etc. One quirk to this approach is that once the log is in the IDLE (i.e. already covered) state, any subsequent log write resets the state back to NEED. This means that a final superblock sync to an already covered log requires two more sb syncs to return the log back to IDLE again.
For example, if a lazy superblock enabled filesystem is mount cycled without any modifications, the unmount path syncs the superblock once and writes an unmount record. With the desired log quiesce covering behavior, we sync the superblock three times at unmount
time: once for the lazy superblock counter update and twice more to cover the log. By contrast, if the log is active or only partially covered at unmount time, a final superblock sync would doubly serve as the one or two remaining syncs required to cover the log.
This duplicate covering sequence is unnecessary because the filesystem remains consistent if a crash occurs at any point. The superblock will either be recovered in the event of a crash or written back before the log is quiesced and potentially cleaned with an unmount record.
Update the log covering state machine to remain in the IDLE state if additional covering checkpoints pass through the log. This facilitates final superblock updates (such as lazy superblock counters) via a single sb sync without losing covered status. This provides some consistency with the active and partially covered cases and also avoids harmless, but spurious checkpoints when quiescing the log.
--- fs/xfs/xfs_log.c | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-)
fs/xfs/xfs_log.c +6 -3
@@ -2597,12 +2597,15 @@ xlog_covered_state( int iclogs_changed) {/* -* We usually go to NEED. But we go to NEED2 if the changed indicates we -* are done writing the dummy record. If we are done with the second -* dummy recored (DONE2), then we go to IDLE. +* We go to NEED for any non-covering writes. We go to NEED2 if we just +* wrote the first covering record (DONE). We go to IDLE if we just +* wrote the second covering record (DONE2) and remain in IDLE until a +* non-covering write occurs. */ switch (prev_state) {case XLOG_STATE_COVER_IDLE : +if (iclogs_changed ==1 ) +return XLOG_STATE_COVER_IDLE ;case XLOG_STATE_COVER_NEED :case XLOG_STATE_COVER_NEED2 :break ;
Signature · 1 line
2.26.2
Re: [PATCH v2 5/9] xfs: don't reset log idle state on covering checkpoints
Quoted 32 lines · Brian Foster
Now that log covering occurs on quiesce, we'd like to reuse the underlying superblock sync for final superblock updates. This includes things like lazy superblock counter updates, log feature incompat bits in the future, etc. One quirk to this approach is that once the log is in the IDLE (i.e. already covered) state, any subsequent log write resets the state back to NEED. This means that a final superblock sync to an already covered log requires two more sb syncs to return the log back to IDLE again.
For example, if a lazy superblock enabled filesystem is mount cycled without any modifications, the unmount path syncs the superblock once and writes an unmount record. With the desired log quiesce covering behavior, we sync the superblock three times at unmount
time: once for the lazy superblock counter update and twice more to cover the log. By contrast, if the log is active or only partially covered at unmount time, a final superblock sync would doubly serve as the one or two remaining syncs required to cover the log.This duplicate covering sequence is unnecessary because the filesystem remains consistent if a crash occurs at any point. The superblock will either be recovered in the event of a crash or written back before the log is quiesced and potentially cleaned with an unmount record.
Update the log covering state machine to remain in the IDLE state if additional covering checkpoints pass through the log. This facilitates final superblock updates (such as lazy superblock counters) via a single sb sync without losing covered status. This provides some consistency with the active and partially covered cases and also avoids harmless, but spurious checkpoints when quiescing the log.
Quoted 2 lines
Signed-off-by Brian Foster <[email protected]>Reviewed-by Darrick J. Wong <[email protected]>
Ok, makes sense
Quoted 28 lines
--- fs/xfs/xfs_log.c | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-)fs/xfs/xfs_log.c +6
-3@@ -2597,12 +2597,15 @@ xlog_covered_state( int iclogs_changed) {/* -* We usually go to NEED. But we go to NEED2 if the changed indicates we -* are done writing the dummy record. If we are done with the second -* dummy recored (DONE2), then we go to IDLE. +* We go to NEED for any non-covering writes. We go to NEED2 if we just +* wrote the first covering record (DONE). We go to IDLE if we just +* wrote the second covering record (DONE2) and remain in IDLE until a +* non-covering write occurs. */ switch (prev_state) {case XLOG_STATE_COVER_IDLE : +if (iclogs_changed ==1 ) +return XLOG_STATE_COVER_IDLE ;case XLOG_STATE_COVER_NEED :case XLOG_STATE_COVER_NEED2 :break ;
PATCH v2 6/9 xfs: fold sbcount quiesce logging into log covering
In reply to Brian Fosterxfs_log_sbcount() calls xfs_sync_sb() to sync superblock counters to disk when lazy superblock accounting is enabled. This occurs on unmount, freeze, and read-only (re)mount and ensures the final values are calculated and persisted to disk before each form of quiesce completes.
Now that log covering occurs in all of these contexts and uses the same xfs_sync_sb() mechanism to update log state, there is no need to log the superblock separately for any reason. Update the log quiesce path to sync the superblock at least once for any mount where lazy superblock accounting is enabled. If the log is already covered, it will remain in the covered state. Otherwise, the next sync as part of the normal covering sequence will carry the associated superblock update with it. Remove xfs_log_sbcount() now that it is no longer needed.
--- fs/xfs/xfs_log.c | 20 ++++++++++++++++++-- fs/xfs/xfs_mount.c | 31 ------------------------------- fs/xfs/xfs_mount.h | 1 - fs/xfs/xfs_super.c | 8 -------- 4 files changed, 18 insertions(+), 42 deletions(-)
fs/xfs/xfs_log.c +18 -2
@@ -1108,6 +1108,7 @@ xfs_log_cover( {struct xlog *log = mp->m_log;int error =0 ; +bool need_covered; ASSERT((xlog_cil_empty(log) && xlog_iclogs_empty(log) && !xfs_ail_min_lsn(log->l_ailp)) ||
@@ -1116,6 +1117,21 @@ xfs_log_cover(if (!xfs_log_writable (mp))return 0 ; +/* +* xfs_log_need_covered() is not idempotent because it progresses the +* state machine if the log requires covering. Therefore, we must call +* this function once and use the result until we've issued an sb sync. +* Do so first to make that abundantly clear. +* +* Fall into the covering sequence if the log needs covering or the +* mount has lazy superblock accounting to sync to disk. The sb sync +* used for covering accumulates the in-core counters, so covering +* handles this for us. +*/ + need_covered =xfs_log_need_covered (mp); +if (!need_covered && !xfs_sb_version_haslazysbcount (&mp->m_sb)) +return 0 ; +/* * To cover the log, commit the superblock twice (at most) in * independent checkpoints. The first serves as a reference for the
@@ -1125,12 +1141,12 @@ xfs_log_cover(* covering the log. Push the AIL one more time to leave it empty, as * we found it. */ -while (xfs_log_need_covered (mp)) { +do { error =xfs_sync_sb (mp, true);if (error)break ;xfs_ail_push_all_sync (mp->m_ail); - } + }while (xfs_log_need_covered (mp));return error; }
fs/xfs/xfs_mount.c +0 -31
@@ -1124,12 +1124,6 @@ xfs_unmountfs(xfs_warn (mp,"Unable to free reserved block pool. " "Freespace may not be correct on next mount." ); - error =xfs_log_sbcount (mp); -if (error) -xfs_warn (mp,"Unable to update superblock counters. " -"Freespace may not be correct on next mount." ); - -xfs_log_unmount (mp);xfs_da_unmount (mp);xfs_uuid_unmount (mp);
@@ -1164,31 +1158,6 @@ xfs_fs_writable(return true; } -/* -* xfs_log_sbcount -* -* Sync the superblock counters to disk. -* -* Note this code can be called during the process of freezing, so we use the -* transaction allocator that does not block when the transaction subsystem is -* in its frozen state. -*/ -int -xfs_log_sbcount (xfs_mount_t *mp) -{ -if (!xfs_log_writable (mp)) -return 0 ; - -/* -* we don't need to do this if we are updating the superblock -* counters on every modification. -*/ -if (!xfs_sb_version_haslazysbcount (&mp->m_sb)) -return 0 ; - -return xfs_sync_sb (mp, true); -} -/* * Deltas for the block count can vary from 1 to very large, but lock contention * only occurs on frequent small block count updates such as in the delayed
fs/xfs/xfs_mount.h +0 -1
@@ -399,7 +399,6 @@ int xfs_buf_hash_init(xfs_perag_t *pag);void xfs_buf_hash_destroy (xfs_perag_t *pag);extern void xfs_uuid_table_free (void ); -extern int xfs_log_sbcount (xfs_mount_t *);extern uint64_t xfs_default_resblks (xfs_mount_t *mp);extern int xfs_mountfs (xfs_mount_t *mp); extern int xfs_initialize_perag(xfs_mount_t *mp, xfs_agnumber_t agcount,
fs/xfs/xfs_super.c +0 -8
@@ -884,19 +884,11 @@ voidxfs_quiesce_attr ( struct xfs_mount *mp) { -int error =0 ; -cancel_delayed_work_sync (&mp->m_log->l_work);/* force the log to unpin objects from the now complete transactions */ xfs_log_force (mp,XFS_LOG_SYNC ); - -/* Push the superblock and write an unmount record */ - error =xfs_log_sbcount (mp); -if (error) -xfs_warn (mp,"xfs_attr_quiesce: failed to log sb changes. " -"Frozen image may not be consistent." );xfs_log_clean (mp); }
Signature · 1 line
2.26.2
Re: [PATCH v2 6/9] xfs: fold sbcount quiesce logging into log covering
Quoted 16 lines · Brian Foster
xfs_log_sbcount()callsxfs_sync_sb()to sync superblock counters to disk when lazy superblock accounting is enabled. This occurs on unmount, freeze, and read-only (re)mount and ensures the final values are calculated and persisted to disk before each form of quiesce completes.Now that log covering occurs in all of these contexts and uses the same
xfs_sync_sb()mechanism to update log state, there is no need to log the superblock separately for any reason. Update the log quiesce path to sync the superblock at least once for any mount where lazy superblock accounting is enabled. If the log is already covered, it will remain in the covered state. Otherwise, the next sync as part of the normal covering sequence will carry the associated superblock update with it. Removexfs_log_sbcount()now that it is no longer needed.
Quoted 2 lines
Signed-off-by Brian Foster <[email protected]>Reviewed-by Darrick J. Wong <[email protected]>
Ok, looks ok
Quoted 142 lines
--- fs/xfs/xfs_log.c | 20 ++++++++++++++++++-- fs/xfs/xfs_mount.c | 31 ------------------------------- fs/xfs/xfs_mount.h | 1 - fs/xfs/xfs_super.c | 8 -------- 4 files changed, 18 insertions(+), 42 deletions(-)fs/xfs/xfs_log.c +18
-2@@ -1108,6 +1108,7 @@ xfs_log_cover( {struct xlog *log = mp->m_log;int error =0 ; +bool need_covered; ASSERT((xlog_cil_empty(log) && xlog_iclogs_empty(log) && !xfs_ail_min_lsn(log->l_ailp)) ||@@ -1116,6 +1117,21 @@ xfs_log_cover(if (!xfs_log_writable (mp))return 0 ; +/* +* xfs_log_need_covered() is not idempotent because it progresses the +* state machine if the log requires covering. Therefore, we must call +* this function once and use the result until we've issued an sb sync. +* Do so first to make that abundantly clear. +* +* Fall into the covering sequence if the log needs covering or the +* mount has lazy superblock accounting to sync to disk. The sb sync +* used for covering accumulates the in-core counters, so covering +* handles this for us. +*/ + need_covered =xfs_log_need_covered (mp); +if (!need_covered && !xfs_sb_version_haslazysbcount (&mp->m_sb)) +return 0 ; +/* * To cover the log, commit the superblock twice (at most) in * independent checkpoints. The first serves as a reference for the @@ -1125,12 +1141,12 @@ xfs_log_cover(* covering the log. Push the AIL one more time to leave it empty, as * we found it. */ -while (xfs_log_need_covered (mp)) { +do { error =xfs_sync_sb (mp, true);if (error)break ;xfs_ail_push_all_sync (mp->m_ail); - } + }while (xfs_log_need_covered (mp));return error; }fs/xfs/xfs_mount.c +0
-31@@ -1124,12 +1124,6 @@ xfs_unmountfs(xfs_warn (mp,"Unable to free reserved block pool. " "Freespace may not be correct on next mount." ); - error =xfs_log_sbcount (mp); -if (error) -xfs_warn (mp,"Unable to update superblock counters. " -"Freespace may not be correct on next mount." ); - -xfs_log_unmount (mp);xfs_da_unmount (mp);xfs_uuid_unmount (mp);@@ -1164,31 +1158,6 @@ xfs_fs_writable(return true; } -/* -* xfs_log_sbcount -* -* Sync the superblock counters to disk. -* -* Note this code can be called during the process of freezing, so we use the -* transaction allocator that does not block when the transaction subsystem is -* in its frozen state. -*/ -int -xfs_log_sbcount (xfs_mount_t *mp) -{ -if (!xfs_log_writable (mp)) -return 0 ; - -/* -* we don't need to do this if we are updating the superblock -* counters on every modification. -*/ -if (!xfs_sb_version_haslazysbcount (&mp->m_sb)) -return 0 ; - -return xfs_sync_sb (mp, true); -} -/* * Deltas for the block count can vary from 1 to very large, but lock contention * only occurs on frequent small block count updates such as in the delayed fs/xfs/xfs_mount.h +0
-1@@ -399,7 +399,6 @@ int xfs_buf_hash_init(xfs_perag_t *pag);void xfs_buf_hash_destroy (xfs_perag_t *pag);extern void xfs_uuid_table_free (void ); -extern int xfs_log_sbcount (xfs_mount_t *);extern uint64_t xfs_default_resblks (xfs_mount_t *mp);extern int xfs_mountfs (xfs_mount_t *mp); extern int xfs_initialize_perag(xfs_mount_t *mp, xfs_agnumber_t agcount,fs/xfs/xfs_super.c +0
-8@@ -884,19 +884,11 @@ voidxfs_quiesce_attr ( struct xfs_mount *mp) { -int error =0 ; -cancel_delayed_work_sync (&mp->m_log->l_work);/* force the log to unpin objects from the now complete transactions */ xfs_log_force (mp,XFS_LOG_SYNC ); - -/* Push the superblock and write an unmount record */ - error =xfs_log_sbcount (mp); -if (error) -xfs_warn (mp,"xfs_attr_quiesce: failed to log sb changes. " -"Frozen image may not be consistent." );xfs_log_clean (mp); }
PATCH v2 7/9 xfs: remove duplicate wq cancel and log force from attr quiesce
In reply to Brian FosterThese two calls are repeated at the beginning of xfs_log_quiesce(). Drop them from xfs_quiesce_attr().
--- fs/xfs/xfs_super.c | 5 ----- 1 file changed, 5 deletions(-)
fs/xfs/xfs_super.c +0 -5
@@ -884,11 +884,6 @@ voidxfs_quiesce_attr ( struct xfs_mount *mp) { -cancel_delayed_work_sync (&mp->m_log->l_work); - -/* force the log to unpin objects from the now complete transactions */ -xfs_log_force (mp,XFS_LOG_SYNC ); -xfs_log_clean (mp); }
Signature · 1 line
2.26.2
Re: [PATCH v2 7/9] xfs: remove duplicate wq cancel and log force from attr quiesce
Quoted 5 lines · Brian Foster
These two calls are repeated at the beginning of
xfs_log_quiesce(). Drop them fromxfs_quiesce_attr().Signed-off-by Brian Foster <[email protected]>Reviewed-by Darrick J. Wong <[email protected]>
Looks ok to me
Quoted 21 lines
--- fs/xfs/xfs_super.c | 5 ----- 1 file changed, 5 deletions(-)fs/xfs/xfs_super.c +0
-5@@ -884,11 +884,6 @@ voidxfs_quiesce_attr ( struct xfs_mount *mp) { -cancel_delayed_work_sync (&mp->m_log->l_work); - -/* force the log to unpin objects from the now complete transactions */ -xfs_log_force (mp,XFS_LOG_SYNC ); -xfs_log_clean (mp); }
PATCH v2 8/9 xfs: remove xfs_quiesce_attr()
In reply to Brian Fosterxfs_quiesce_attr() is now a wrapper for xfs_log_clean(). Remove it and call xfs_log_clean() directly.
--- fs/xfs/xfs_mount.c | 2 +- fs/xfs/xfs_super.c | 24 ++---------------------- 2 files changed, 3 insertions(+), 23 deletions(-)
fs/xfs/xfs_mount.c +1 -1
@@ -946,7 +946,7 @@ xfs_mountfs(*/ if ((mp->m_flags & (XFS_MOUNT_RDONLY |XFS_MOUNT_NORECOVERY )) ==XFS_MOUNT_RDONLY ) { -xfs_quiesce_attr (mp); +xfs_log_clean (mp); }/*
fs/xfs/xfs_super.c +2 -22
@@ -867,26 +867,6 @@ xfs_restore_resvblks(struct xfs_mount *mp)xfs_reserve_blocks (mp, &resblks,NULL ); } -/* -* Trigger writeback of all the dirty metadata in the file system. -* -* This ensures that the metadata is written to their location on disk rather -* than just existing in transactions in the log. This means after a quiesce -* there is no log replay required to write the inodes to disk - this is the -* primary difference between a sync and a quiesce. -* -* We cancel log work early here to ensure all transactions the log worker may -* run have finished before we clean up and log the superblock and write an -* unmount record. The unfreeze process is responsible for restarting the log -* worker correctly. -*/ -void -xfs_quiesce_attr ( -struct xfs_mount *mp) -{ -xfs_log_clean (mp); -} -/* * Second stage of a freeze. The data is already frozen so we only * need to take care of the metadata. Once that's done sync the superblock
@@ -909,7 +889,7 @@ xfs_fs_freeze( flags =memalloc_nofs_save ();xfs_stop_block_reaping (mp);xfs_save_resvblks (mp); -xfs_quiesce_attr (mp); +xfs_log_clean (mp); ret =xfs_sync_sb (mp, true);memalloc_nofs_restore (flags);return ret;
@@ -1752,7 +1732,7 @@ xfs_remount_ro(*/ xfs_save_resvblks (mp); -xfs_quiesce_attr (mp); +xfs_log_clean (mp); mp->m_flags |=XFS_MOUNT_RDONLY ;return 0 ;
Signature · 1 line
2.26.2
Re: [PATCH v2 8/9] xfs: remove xfs_quiesce_attr()
Quoted 5 lines · Brian Foster
xfs_quiesce_attr()is now a wrapper forxfs_log_clean(). Remove it and callxfs_log_clean()directly.Signed-off-by Brian Foster <[email protected]>Reviewed-by Darrick J. Wong <[email protected]>
Looks good
Quoted 68 lines
--- fs/xfs/xfs_mount.c | 2 +- fs/xfs/xfs_super.c | 24 ++---------------------- 2 files changed, 3 insertions(+), 23 deletions(-)fs/xfs/xfs_mount.c +1
-1@@ -946,7 +946,7 @@ xfs_mountfs(*/ if ((mp->m_flags & (XFS_MOUNT_RDONLY |XFS_MOUNT_NORECOVERY )) ==XFS_MOUNT_RDONLY ) { -xfs_quiesce_attr (mp); +xfs_log_clean (mp); }/* fs/xfs/xfs_super.c +2
-22@@ -867,26 +867,6 @@ xfs_restore_resvblks(struct xfs_mount *mp)xfs_reserve_blocks (mp, &resblks,NULL ); } -/* -* Trigger writeback of all the dirty metadata in the file system. -* -* This ensures that the metadata is written to their location on disk rather -* than just existing in transactions in the log. This means after a quiesce -* there is no log replay required to write the inodes to disk - this is the -* primary difference between a sync and a quiesce. -* -* We cancel log work early here to ensure all transactions the log worker may -* run have finished before we clean up and log the superblock and write an -* unmount record. The unfreeze process is responsible for restarting the log -* worker correctly. -*/ -void -xfs_quiesce_attr ( -struct xfs_mount *mp) -{ -xfs_log_clean (mp); -} -/* * Second stage of a freeze. The data is already frozen so we only * need to take care of the metadata. Once that's done sync the superblock @@ -909,7 +889,7 @@ xfs_fs_freeze( flags =memalloc_nofs_save ();xfs_stop_block_reaping (mp);xfs_save_resvblks (mp); -xfs_quiesce_attr (mp); +xfs_log_clean (mp); ret =xfs_sync_sb (mp, true);memalloc_nofs_restore (flags);return ret;@@ -1752,7 +1732,7 @@ xfs_remount_ro(*/ xfs_save_resvblks (mp); -xfs_quiesce_attr (mp); +xfs_log_clean (mp); mp->m_flags |=XFS_MOUNT_RDONLY ;return 0 ;
PATCH v2 9/9 xfs: cover the log on freeze instead of cleaning it
In reply to Brian FosterFilesystem freeze cleans the log and immediately redirties it so log recovery runs if a crash occurs after the filesystem is frozen. Now that log quiesce covers the log, there is no need to clean the log and redirty it to trigger log recovery because covering has the same effect. Update xfs_fs_freeze() to quiesce (and thus cover) the log.
--- fs/xfs/xfs_super.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
fs/xfs/xfs_super.c +1 -2
@@ -889,8 +889,7 @@ xfs_fs_freeze( flags =memalloc_nofs_save ();xfs_stop_block_reaping (mp);xfs_save_resvblks (mp); -xfs_log_clean (mp); - ret =xfs_sync_sb (mp, true); + ret =xfs_log_quiesce (mp);memalloc_nofs_restore (flags);return ret; }
Signature · 1 line
2.26.2
Re: [PATCH v2 9/9] xfs: cover the log on freeze instead of cleaning it
Quoted 8 lines · Brian Foster
Filesystem freeze cleans the log and immediately redirties it so log recovery runs if a crash occurs after the filesystem is frozen. Now that log quiesce covers the log, there is no need to clean the log and redirty it to trigger log recovery because covering has the same effect. Update
xfs_fs_freeze()to quiesce (and thus cover) the log.Signed-off-by Brian Foster <[email protected]>Reviewed-by Darrick J. Wong <[email protected]>
Ok makes sense
Quoted 19 lines
--- fs/xfs/xfs_super.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)fs/xfs/xfs_super.c +1
-2@@ -889,8 +889,7 @@ xfs_fs_freeze( flags =memalloc_nofs_save ();xfs_stop_block_reaping (mp);xfs_save_resvblks (mp); -xfs_log_clean (mp); - ret =xfs_sync_sb (mp, true); + ret =xfs_log_quiesce (mp);memalloc_nofs_restore (flags);return ret; }