public inbox for cluster-cvs@sourceware.org help / color / mirror / Atom feed
From: alewis@sourceware.org To: cluster-cvs@sources.redhat.com Subject: cluster/gfs/gfs_fsck initialize.c lost_n_found ... Date: Thu, 03 Mar 2005 19:53:00 -0000 [thread overview] Message-ID: <20050303195357.28324.qmail@sourceware.org> (raw) CVSROOT: /cvs/cluster Module name: cluster Changes by: alewis@sourceware.org 2005-03-03 19:53:57 Modified files: gfs/gfs_fsck : initialize.c lost_n_found.c pass1.c pass2.c pass3.c pass5.c util.c util.h Log message: o increment link count when dealing with bad '.' & '..' entries o Clears up the spurious "Found unused inode marked in-use" msgs (bz #150207) o Make sure disk is synced at end, handle link count for l+f better o Changing GFS_METATYPE_EA -> ED - handles metadata change in GFS 6.1 (bz #150208) Patches: http://sources.redhat.com/cgi-bin/cvsweb.cgi/cluster/gfs/gfs_fsck/initialize.c.diff?cvsroot=cluster&r1=1.7&r2=1.8 http://sources.redhat.com/cgi-bin/cvsweb.cgi/cluster/gfs/gfs_fsck/lost_n_found.c.diff?cvsroot=cluster&r1=1.6&r2=1.7 http://sources.redhat.com/cgi-bin/cvsweb.cgi/cluster/gfs/gfs_fsck/pass1.c.diff?cvsroot=cluster&r1=1.9&r2=1.10 http://sources.redhat.com/cgi-bin/cvsweb.cgi/cluster/gfs/gfs_fsck/pass2.c.diff?cvsroot=cluster&r1=1.9&r2=1.10 http://sources.redhat.com/cgi-bin/cvsweb.cgi/cluster/gfs/gfs_fsck/pass3.c.diff?cvsroot=cluster&r1=1.7&r2=1.8 http://sources.redhat.com/cgi-bin/cvsweb.cgi/cluster/gfs/gfs_fsck/pass5.c.diff?cvsroot=cluster&r1=1.6&r2=1.7 http://sources.redhat.com/cgi-bin/cvsweb.cgi/cluster/gfs/gfs_fsck/util.c.diff?cvsroot=cluster&r1=1.5&r2=1.6 http://sources.redhat.com/cgi-bin/cvsweb.cgi/cluster/gfs/gfs_fsck/util.h.diff?cvsroot=cluster&r1=1.2&r2=1.3
next reply other threads:[~2005-03-03 19:53 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-03-03 19:53 alewis [this message] 2005-03-03 19:57 alewis
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=20050303195357.28324.qmail@sourceware.org \ --to=alewis@sourceware.org \ --cc=cluster-cvs@sources.redhat.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: linkBe 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 read-only IMAP folder(s) and NNTP newsgroup(s).