From: Eric Sandeen <sandeen@redhat.com>
To: xfs-oss <xfs@oss.sgi.com>
Subject: [PATCH 1/2] xfs_fsr: extra debugging info
Date: Fri, 30 Mar 2012 09:54:49 -0500 [thread overview]
Message-ID: <4F75C939.6030009@redhat.com> (raw)
Provide 2 new pieces of information when -d is specified to
xfs_fsr:
* If we needed to grow the forkoffset and couldn't
* If we were unable to match the fork offset
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
---
diff --git a/fsr/xfs_fsr.c b/fsr/xfs_fsr.c
index 2db2224..d83bdc9 100644
--- a/fsr/xfs_fsr.c
+++ b/fsr/xfs_fsr.c
@@ -1021,6 +1021,7 @@ fsr_setup_attr_fork(
{
struct stat64 tstatbuf;
int i;
+ int diff = 0;
int last_forkoff = 0;
int no_change_cnt = 0;
int ret;
@@ -1056,7 +1057,6 @@ fsr_setup_attr_fork(
xfs_bstat_t tbstat;
xfs_ino_t ino;
char name[64];
- int diff;
/*
* bulkstat the temp inode to see what the forkoff is. Use
@@ -1122,6 +1122,8 @@ fsr_setup_attr_fork(
* non-contiguous offsets.
*/
/* XXX: unimplemented! */
+ if (dflag)
+ printf(_("data fork growth unimplemented\n"));
goto out;
}
@@ -1137,6 +1139,10 @@ fsr_setup_attr_fork(
out:
if (dflag)
fsrprintf(_("set temp attr\n"));
+ /* We failed to resolve the fork difference */
+ if (dflag && diff)
+ fsrprintf(_("failed to match fork offset\n"));;
+
return 0;
}
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2012-03-30 14:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-30 14:54 Eric Sandeen [this message]
2012-03-30 15:01 ` [PATCH 2/2] xfs_fsr: create extent-based attr to grow forkoff Eric Sandeen
2012-03-30 18:11 ` Eric Sandeen
2012-05-12 1:30 ` Eric Sandeen
2013-10-10 3:11 ` Eric Sandeen
2013-10-10 3:21 ` Dave Chinner
2013-10-10 3:24 ` Eric Sandeen
-- strict thread matches above, loose matches on Subject: below --
2013-10-18 22:07 [PATCH 0/1] xfs_fsr fixes Eric Sandeen
2013-10-18 22:09 ` [PATCH 1/2] xfs_fsr: extra debugging info Eric Sandeen
2013-11-17 10:06 ` Christoph Hellwig
2013-11-18 19:03 ` Rich Johnston
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=4F75C939.6030009@redhat.com \
--to=sandeen@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