From: David Chinner <dgc@sgi.com>
To: Russell Cattelan <cattelan@thebarn.com>
Cc: David Chinner <dgc@sgi.com>,
Christoph Hellwig <hch@infradead.org>,
Barry Naujok <bnaujok@sgi.com>,
"xfs@oss.sgi.com" <xfs@oss.sgi.com>, xfs-dev <xfs-dev@sgi.com>
Subject: Re: REVIEW: xfs_reno
Date: Wed, 3 Oct 2007 09:41:27 +1000 [thread overview]
Message-ID: <20071002234126.GH23367404@sgi.com> (raw)
In-Reply-To: <470274BF.7070702@thebarn.com>
On Tue, Oct 02, 2007 at 11:41:35AM -0500, Russell Cattelan wrote:
> >At that point, we'll got a "working" shrink that will allow
> >shrinking to only 50% of the original size because the log will
> >get in the way. To fix that, we'll need to implement transactions
> >to move the log...
>
> If we do that could be move to an inode based log?
What do we gain from doing that? (I'm a bit slow today)
> Keep it contagious so recovery won't have to parse
> up the file system to find the log.
I'm worried by those contagious logs. What do you catch from them? :)
> The normal running case should be easier to deal with if
> the log was just a file?
I don't see how it changes anything - we address the log directly
by block number and device...
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
next prev parent reply other threads:[~2007-10-02 23:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-02 7:08 REVIEW: xfs_reno Barry Naujok
2007-10-02 7:20 ` Nathan Scott
2007-10-02 9:02 ` Christoph Hellwig
2007-10-02 9:19 ` David Chinner
2007-10-02 16:41 ` Russell Cattelan
2007-10-02 23:41 ` David Chinner [this message]
2007-10-03 1:05 ` Barry Naujok
2007-10-03 4:58 ` David Chinner
2007-10-03 1:30 ` Timothy Shimmin
2007-10-03 5:50 ` 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=20071002234126.GH23367404@sgi.com \
--to=dgc@sgi.com \
--cc=bnaujok@sgi.com \
--cc=cattelan@thebarn.com \
--cc=hch@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.