From: Brian Foster <bfoster@redhat.com>
To: xfs@oss.sgi.com
Subject: [PATCH 0/2] xfs log recovery delay instrumentation
Date: Wed, 20 Aug 2014 12:55:53 -0400 [thread overview]
Message-ID: <1408553755-10255-1-git-send-email-bfoster@redhat.com> (raw)
Hi all,
Here's a couple patches to add the log recovery delay instrumentation
required for reproducing the log recovery buf race problem uncovered by
Alex:
http://oss.sgi.com/archives/xfs/2014-08/msg00155.html
It looked easier to dump this tunable in /proc, but it seems like we
want to move away from adding more things there. This series defines a
generic sys/fs/xfs/debug location to serve a similar purpose and exports
the log recovery delay tunable therein.
The original problem is now easily reproduced with a 10s or so log
recovery delay and the xfstests test I posted the other day:
http://oss.sgi.com/archives/xfs/2014-08/msg00261.html
One thing that comes to mind as I write this is whether it might be a
good idea to only export this debug subdirectory for DEBUG enabled
kernels. Thoughts? Any other thoughts, reviews or flames are appreciated
as well.
Brian
Brian Foster (2):
xfs: add debug sysfs attribute set
xfs: export log_recovery_delay to delay mount time log recovery
fs/xfs/xfs_globals.c | 4 +++
fs/xfs/xfs_log_recover.c | 12 ++++++++
fs/xfs/xfs_super.c | 15 ++++++++--
fs/xfs/xfs_sysctl.h | 5 ++++
fs/xfs/xfs_sysfs.c | 71 ++++++++++++++++++++++++++++++++++++++++++++++++
fs/xfs/xfs_sysfs.h | 1 +
6 files changed, 106 insertions(+), 2 deletions(-)
--
1.8.3.1
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2014-08-20 16:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-20 16:55 Brian Foster [this message]
2014-08-20 16:55 ` [PATCH 1/2] xfs: add debug sysfs attribute set Brian Foster
2014-08-20 16:55 ` [PATCH 2/2] xfs: export log_recovery_delay to delay mount time log recovery Brian Foster
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1408553755-10255-1-git-send-email-bfoster@redhat.com \
--to=bfoster@redhat.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox