Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: "Torbjörn Jansson" <torbjorn@jansson.tech>
To: Chris Murphy <lists@colorremedies.com>
Cc: Nikolay Borisov <nborisov@suse.com>,
	Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs-convert aborts with an assert
Date: Thu, 9 Jun 2022 19:55:20 +0200	[thread overview]
Message-ID: <22dce7de-4709-49fc-9a4f-4f3d179bd242@jansson.tech> (raw)
In-Reply-To: <CAJCQCtQ5W1CqiLedXt0ZzaVOnJ2d_nugFHyt879yOs3W_K=YjA@mail.gmail.com>

On 2022-06-07 20:24, Chris Murphy wrote:
> On Mon, Jun 6, 2022 at 12:51 PM Torbjörn Jansson <torbjorn@jansson.tech> wrote:
> 
>> Filesystem features:      has_journal ext_attr dir_index filetype meta_bg
>> extent 64bit flex_bg casefold sparse_super large_file huge_file dir_nlink
>> extra_isize metadata_csum
> 
> ^^casefold
> 
> I don't think this is related to the reported problem, but it occurs
> to me maybe btrfs-progs should check for this feature and warn? The
> feature being set means there could be behavioral expectations that
> Btrfs can't currently provide since it doesn't support casefolding.
> 

In my case i planed on using it but since, at the time, the ext4 tools for my 
dist did not support changing the flag properly i never started to use it.

i'm not a dev and don't know all the details about this but i think at least 
there should not be possible to end up with duplicate filenames as a result of 
this.

  reply	other threads:[~2022-06-09 17:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-06 14:03 btrfs-convert aborts with an assert Torbjörn Jansson
2022-06-06 14:14 ` Nikolay Borisov
2022-06-06 14:31 ` Nikolay Borisov
2022-06-06 15:00   ` Torbjörn Jansson
2022-06-06 15:21     ` Nikolay Borisov
2022-06-06 15:31       ` Torbjörn Jansson
2022-06-07 18:24     ` Chris Murphy
2022-06-09 17:55       ` Torbjörn Jansson [this message]
2022-06-06 14:34 ` David Sterba

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=22dce7de-4709-49fc-9a4f-4f3d179bd242@jansson.tech \
    --to=torbjorn@jansson.tech \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.com \
    --cc=nborisov@suse.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