Linux-XFS Archive mirror
 help / color / mirror / Atom feed
From: linux-xfs.ykg@rutile.org
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: linux-xfs@vger.kernel.org
Subject: Re: Question about using reflink and realtime features on the same filesystem
Date: Wed, 17 Apr 2024 01:03:49 +0000	[thread overview]
Message-ID: <0101018ee994d5c1-fafa8e6b-6d23-4182-9164-7bd5b33eab19-000000@us-west-2.amazonses.com> (raw)
In-Reply-To: <20240417002639.GJ11948@frogsfrogsfrogs>

On 4/16/2024 17:26, Darrick J. Wong wrote:
> On Tue, Apr 16, 2024 at 11:24:27PM +0000, linux-xfs.ykg@rutile.org wrote:
>> Greetings,
>>
>> I was attempting to use mkfs.xfs on Linux Mint 21 (kernel 6.5.0, xfsprogs
>> 5.13.0) and ran into an error trying to use realtime and reflink features on
>> the same filesystem. Is there anything I'm doing wrong, or is this
>> combination simply not supported on the same filesystem?
>>
>> The exact command I ran was:
>> mkfs.xfs -N -r rtdev=/dev/sda1,extsize=1048576 -m reflink=1 /dev/sda2
>>
>> Which returned with:
>> reflink not supported with realtime devices
>>
>> Just to be clear - I didn't expect to be able to use reflinking on realtime
>> files (*), but I did expect to be able to have realtime files and reflinked
>> non-realtime files supported on the same filesystem. With my limited
>> knowledge of the inner workings of XFS, those two features _seem_ like they
>> could both work together as long as they are used on different inodes. Is
>> this not the case?
> 
> It's not supported, currently.  Patches have been out for review since
> 2020 but have not moved forward due to prioritization and backlog issues.
> Sorry about that. :(
> 
> https://lore.kernel.org/linux-xfs/160945477567.2833676.4112646582104319587.stgit@magnolia/
> 
> --D
> 
>> Thanks,
>> Reed Wilson
>>
>>
>>
>> (*) I noticed that there were recent commits for reflinking realtime files,
>> but that's not really what I was looking for
>>
>>
> 


Thanks for the quick response. It's not really a big problem in my case; I can
work around it fairly easily. I mostly wanted to verify that it's not a supported
configuration since I couldn't find any documentation to that effect.

Thanks again!
Reed Wilson

      reply	other threads:[~2024-04-17  1:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-16 23:24 Question about using reflink and realtime features on the same filesystem linux-xfs.ykg
2024-04-17  0:26 ` Darrick J. Wong
2024-04-17  1:03   ` linux-xfs.ykg [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=0101018ee994d5c1-fafa8e6b-6d23-4182-9164-7bd5b33eab19-000000@us-west-2.amazonses.com \
    --to=linux-xfs.ykg@rutile.org \
    --cc=djwong@kernel.org \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).