From: rpeterso@sourceware.org <rpeterso@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/gfs2/fsck pass1.c
Date: 26 Mar 2007 19:14:03 -0000 [thread overview]
Message-ID: <20070326191403.32502.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: cluster
Changes by: rpeterso at sourceware.org 2007-03-26 20:14:03
Modified files:
gfs2/fsck : pass1.c
Log message:
Resolves: Bugzilla Bug 232019: gfs2_fsck doesn't fix an ea problem.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs2/fsck/pass1.c.diff?cvsroot=cluster&r1=1.5&r2=1.6
--- cluster/gfs2/fsck/pass1.c 2007/01/23 19:23:07 1.5
+++ cluster/gfs2/fsck/pass1.c 2007/03/26 19:14:03 1.6
@@ -287,8 +287,8 @@
}
static int check_eattr_leaf(struct gfs2_inode *ip, uint64_t block,
- uint64_t parent, struct gfs2_buffer_head **bh,
- void *private)
+ uint64_t parent, struct gfs2_buffer_head **bh,
+ void *private)
{
struct gfs2_sbd *sdp = ip->i_sbd;
struct gfs2_buffer_head *leaf_bh;
@@ -324,10 +324,13 @@
else {
leaf_bh = bread(sdp, block);
if(gfs2_check_meta(leaf_bh, GFS2_METATYPE_EA)) {
- log_warn("EA leaf block has incorrect type.\n");
+ log_warn("EA leaf block %"PRIu64" (0x%"
+ PRIx64") for inode %"PRIu64" (0x%"
+ PRIx64") has incorrect type.\n",
+ block, block, ip->i_di.di_num.no_addr,
+ ip->i_di.di_num.no_addr);
gfs2_block_set(bl, block, gfs2_meta_inval);
- brelse(leaf_bh, not_updated);
- ret = 1;
+ ret = -1;
}
else {
log_debug("Setting block %" PRIu64 " (0x%" PRIx64
next reply other threads:[~2007-03-26 19:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-26 19:14 rpeterso [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-03-26 19:16 [Cluster-devel] cluster/gfs2/fsck pass1.c rpeterso
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=20070326191403.32502.qmail@sourceware.org \
--to=rpeterso@sourceware.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).