public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Ansgar Esztermann-Kirchner <aeszter@mpinat.mpg.de>
To: <linux-xfs@vger.kernel.org>
Subject: Re: Replacing the external log device
Date: Wed, 12 Apr 2023 14:53:28 +0200	[thread overview]
Message-ID: <ZDapyHDzMVjD2Qk/@aeszter.mpibpc.intern> (raw)
In-Reply-To: <ZDafWCuO8iZB1Vev@infradead.org>

[-- Attachment #1: Type: text/plain, Size: 1098 bytes --]

On Wed, Apr 12, 2023 at 05:08:56AM -0700, Christoph Hellwig wrote:
> Let me restate that:  you created a new XFS file system, but then tried
> to reuse an existing log device for it?

Yes (more or less, as the existing log device should be reformatted by
xfs_repair).
 
> How did you format the new file system?  XFS either expects and internal
> log, or a log device?  For the above error it must have been formatted
> with a different external log?  

Yes, that's correct.

> And then you just switched the mount
> option to the log device of the previous file system?

I physically replaced the disks.

> If so that can't work, and I'm surprised you got so far.

Hmm. Does that mean a zeroed log is still different from one that has
been freshly created? If that is true, then that would be a difference
from the "working" and "not working" cases.
Or do you mean that a log device cannot be replaced even if it is
physically damaged?

A.

-- 
Ansgar Esztermann
Sysadmin Dep. Theoretical and Computational Biophysics
https://www.mpinat.mpg.de/person/11315/3883774

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 4945 bytes --]

      reply	other threads:[~2023-04-12 13:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-12  7:21 Replacing the external log device Ansgar Esztermann-Kirchner
2023-04-12 12:08 ` Christoph Hellwig
2023-04-12 12:53   ` Ansgar Esztermann-Kirchner [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=ZDapyHDzMVjD2Qk/@aeszter.mpibpc.intern \
    --to=aeszter@mpinat.mpg.de \
    --cc=linux-xfs@vger.kernel.org \
    /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