From: Dave Chinner <david@fromorbit.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs@oss.sgi.com, Joe Landman <joe.landman@gmail.com>
Subject: Re: converting from external log to internal log ... is this possible?
Date: Tue, 9 Sep 2014 08:07:38 +1000 [thread overview]
Message-ID: <20140908220738.GP30012@dastard> (raw)
In-Reply-To: <540DF86D.8080705@sandeen.net>
On Mon, Sep 08, 2014 at 01:41:49PM -0500, Eric Sandeen wrote:
> On 9/8/14 1:10 PM, Joe Landman wrote:
> >Figured I'd ask, looked on the FAQ and didn't see anything there
> >relevant to this. There is a hint of this in xfs_growfs,
> >specifically the -i option, though it is noted that "[NOTE: This
> >option is not implemented]".
>
> Yep, it's never been implemented. You could do it manually with
> some very careful xfs_db surgery, if you had enough contiguous
> freespace available, but it's not at all supported.
>
> Basically, no, you can't do it without getting very far under
> the hood and directly editing the disk.
There's nothing amazingly difficult about implementing
external-to-internal journal. First allocate the contiguous extent
for the new log, then zero it, then freeze the filesystem to bring
the external log down to a clean state, atomically modify the
superblock on disk to point at the new log, then re-initialise all
the log state to point at the new log, update the head and tail to
new cycles at the start of the new log, and unfreeze....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2014-09-08 22:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-08 18:10 converting from external log to internal log ... is this possible? Joe Landman
2014-09-08 18:41 ` Eric Sandeen
2014-09-08 22:07 ` Dave Chinner [this message]
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=20140908220738.GP30012@dastard \
--to=david@fromorbit.com \
--cc=joe.landman@gmail.com \
--cc=sandeen@sandeen.net \
--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