All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Marcin Sura <mailing-lists@sura.pl>
Cc: linux-xfs@vger.kernel.org
Subject: Re: Can I add external log device after filesystem was created?
Date: Thu, 3 Nov 2016 19:37:03 -0500	[thread overview]
Message-ID: <ba7f0c5e-2e89-98b6-f1ff-9ad00334fcba@sandeen.net> (raw)
In-Reply-To: <CACNifpV7qQ_5YzJJfdaKi3SThBa7x4N=VNeK1f_OkijiXh6zPA@mail.gmail.com>

If it's just test data, I can give you a recipe for moving it with
xfs_db, I think - if you're willing to lose the filesystem if
something goes wrong.  ;)

-Eric

On 11/3/16 4:14 PM, Marcin Sura wrote:
> Hi,
> 
> We are building huge test system with hundreds TB of data. We want to
> execute some performance tests without and with external log device.
> Filling in the data is a time consuming process, so my first idea was
> to create the filesystem without external log, execute the tests and
> then add external log and repeat the tests without recreating the
> filesystem. Now I know I have to do this. Thanks
> 
> BR
> Marcin
> 
> 2016-11-03 20:57 GMT+01:00 Eric Sandeen <sandeen@sandeen.net>:
>> On 11/3/16 2:28 PM, Marcin Sura wrote:
>>> Hi,
>>>
>>> I've created filesystem with default mkfs.xfs command, started to use
>>> the filesystem. Few days later I've got nice SSD-based lun which can
>>> be used as external log device.
>>>
>>> Can I add that lun as external log device to an existing filesystem? How?
>>>
>>> BR
>>> Marcin
>>
>> There is no supported mechanism for doing this.  It can be done with xfs_db
>> disk-editing surgery, but that's not really recommended.
>>
>> What is your reason for wanting to move the log?
>>
>> -Eric
> 

      reply	other threads:[~2016-11-04  0:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-03 19:28 Can I add external log device after filesystem was created? Marcin Sura
2016-11-03 19:57 ` Eric Sandeen
2016-11-03 21:14   ` Marcin Sura
2016-11-04  0:37     ` Eric Sandeen [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=ba7f0c5e-2e89-98b6-f1ff-9ad00334fcba@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=linux-xfs@vger.kernel.org \
    --cc=mailing-lists@sura.pl \
    /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.