public inbox for cluster-cvs@sourceware.org help / color / mirror / Atom feed
From: rpeterso@sourceware.org To: cluster-cvs@sources.redhat.com Subject: cluster/gfs2/edit hexedit.c hexedit.h savemeta.c Date: Thu, 18 Oct 2007 19:56:00 -0000 [thread overview] Message-ID: <20071018195641.30826.qmail@sourceware.org> (raw) CVSROOT: /cvs/cluster Module name: cluster Changes by: rpeterso@sourceware.org 2007-10-18 19:56:41 Modified files: gfs2/edit : hexedit.c hexedit.h savemeta.c Log message: While working on bz #291551, I discovered that gfs2_edit savemeta only saved true metadata, but we need more than that. There are lots of blocks that are considered "data" (not metadata) by the RG bitmaps that we still need to save. These include: 1. All the system journals (which may contain both metadata and user data, disguised as data blocks within the journal). We need to pick out the parts that do not contain user data. 2. The system files, such as statfs, inum, quota file, etc. These may be helpful in debugging user problems. 3. Indirect block pointers, which may be counted as data for accounting purposes, even though it's metadata. 4. Directory leaf blocks. This change allows gfs2_edit to save and restore these blocks properly, and also to print out a breakdown of a saved metadata file: gfs2_edit printsavedmeta /tmp/gfsmeta It also improves on the information given when a journal is dumped. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs2/edit/hexedit.c.diff?cvsroot=cluster&r1=1.21&r2=1.22 http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs2/edit/hexedit.h.diff?cvsroot=cluster&r1=1.11&r2=1.12 http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs2/edit/savemeta.c.diff?cvsroot=cluster&r1=1.3&r2=1.4
reply other threads:[~2007-10-18 19:56 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20071018195641.30826.qmail@sourceware.org \ --to=rpeterso@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).