linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 4/4 RESEND] btrfs: scrub maintenance event should be recorded in the messages
Date: Tue, 20 May 2014 01:03:42 +0800	[thread overview]
Message-ID: <1400519022-5540-4-git-send-email-anand.jain@oracle.com> (raw)
In-Reply-To: <1400519022-5540-1-git-send-email-anand.jain@oracle.com>

so to help problem understanding and solving

Signed-off-by: Anand Jain <anand.jain@oracle.com>
---
 fs/btrfs/ioctl.c | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/fs/btrfs/ioctl.c b/fs/btrfs/ioctl.c
index e174770..ff27c08 100644
--- a/fs/btrfs/ioctl.c
+++ b/fs/btrfs/ioctl.c
@@ -3702,10 +3702,17 @@ static long btrfs_ioctl_scrub(struct file *file, void __user *arg)
 			goto out;
 	}
 
+	btrfs_info(root->fs_info, "Scrub started");
+
 	ret = btrfs_scrub_dev(root->fs_info, sa->devid, sa->start, sa->end,
 			      &sa->progress, sa->flags & BTRFS_SCRUB_READONLY,
 			      0);
 
+	if (ret)
+		btrfs_info(root->fs_info, "Scrub failed - %d", ret);
+	else
+		btrfs_info(root->fs_info, "Scrub finished");
+
 	if (copy_to_user(arg, sa, sizeof(*sa)))
 		ret = -EFAULT;
 
-- 
1.8.5.3


  parent reply	other threads:[~2014-05-19 17:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-19 17:03 [PATCH 1/4 RESEND] Btrfs: all super blocks of the replaced disk must be scratched Anand Jain
2014-05-19 17:03 ` [PATCH 2/4 RESEND] btrfs: btrfs_rm_device() should zero mirror SB as well Anand Jain
2014-05-19 17:03 ` [PATCH 3/4 RESEND] btrfs: add framework to read fs info from btrfs-control Anand Jain
2014-05-19 17:03 ` Anand Jain [this message]
2014-05-20  6:31 ` [PATCH 1/4 RESEND V3] Btrfs: all super blocks of the replaced disk must be scratched Anand Jain

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=1400519022-5540-4-git-send-email-anand.jain@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).