From: Lachlan McIlroy <lachlan@sgi.com>
To: xfs-dev <xfs-dev@sgi.com>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: [PATCH] log replay should not overwrite newer ondisk inodes
Date: Thu, 30 Aug 2007 12:12:47 +1000 [thread overview]
Message-ID: <46D6279F.40601@sgi.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 555 bytes --]
Log replay of clustered inodes currently ignores the flushiter
field in the inode that is used to determine if the on-disk inode
is more up to date than the copy in the log. As a result during
log replay the newer inode is being overwritten with an older
version and file size updates are being lost.
I haven't handled the case of the flushiter counter overflowing
but that shouldn't be a problem in this case. The log buffer
contains newly created inodes so their flushiter values will be 0
and the on-disk inodes should not be much greater.
Lachlan
[-- Attachment #2: xfs_log_recover.diff --]
[-- Type: text/x-patch, Size: 1278 bytes --]
--- fs/xfs/xfs_log_recover.c_1.322 2007-08-27 17:45:45.000000000 +1000
+++ fs/xfs/xfs_log_recover.c 2007-08-30 11:50:44.000000000 +1000
@@ -1866,6 +1866,27 @@ xlog_recover_do_inode_buffer(
}
/*
+ * Check if we need to recover an inode from a buffer
+ */
+int
+xfs_recover_inode(
+ char *dest,
+ char *src)
+{
+ xfs_dinode_t *dip = (xfs_dinode_t *)dest;
+ xfs_dinode_t *dilp = (xfs_dinode_t*)src;
+
+ if ((be16_to_cpu(dip->di_core.di_magic) == XFS_DINODE_MAGIC) &&
+ (be16_to_cpu(dilp->di_core.di_magic) == XFS_DINODE_MAGIC) &&
+ (be16_to_cpu(dilp->di_core.di_flushiter) <
+ be16_to_cpu(dip->di_core.di_flushiter))) {
+ return 1;
+ }
+
+ return 0;
+}
+
+/*
* Perform a 'normal' buffer recovery. Each logged region of the
* buffer should be copied over the corresponding region in the
* given buffer. The bitmap in the buf log format structure indicates
@@ -1917,6 +1938,13 @@ xlog_recover_do_reg_buffer(
-1, 0, XFS_QMOPT_DOWARN,
"dquot_buf_recover");
}
+ /*
+ * Sanity check if this is an inode buffer.
+ */
+ if (!error)
+ error = xfs_recover_inode(xfs_buf_offset(bp,
+ (uint)bit << XFS_BLI_SHIFT),
+ item->ri_buf[i].i_addr);
if (!error)
memcpy(xfs_buf_offset(bp,
(uint)bit << XFS_BLI_SHIFT), /* dest */
next reply other threads:[~2007-08-30 2:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-30 2:12 Lachlan McIlroy [this message]
2007-08-30 4:31 ` [PATCH] log replay should not overwrite newer ondisk inodes Timothy Shimmin
2007-08-30 4:50 ` Lachlan McIlroy
2007-08-30 8:29 ` Timothy Shimmin
2007-08-30 8:51 ` Timothy Shimmin
2007-08-31 2:22 ` Lachlan McIlroy
2007-08-31 4:01 ` Mark Goodwin
2007-08-31 15:48 ` David Chinner
2007-09-02 22:50 ` Vlad Apostolov
2007-09-03 8:49 ` David Chinner
2007-09-07 2:03 ` Lachlan McIlroy
2007-09-07 14:05 ` David Chinner
2007-09-10 4:43 ` Lachlan McIlroy
2007-08-31 2:14 ` Lachlan McIlroy
2007-08-30 14:02 ` David Chinner
2007-09-04 23:05 ` Shailendra Tripathi
2007-09-04 23:49 ` David Chinner
2007-09-04 23:51 ` David Chinner
2007-09-05 1:19 ` Timothy Shimmin
2007-09-05 1:40 ` Lachlan McIlroy
2007-09-05 6:54 ` David Chinner
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=46D6279F.40601@sgi.com \
--to=lachlan@sgi.com \
--cc=xfs-dev@sgi.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