Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Mark Harmstone <maharmstone@meta.com>
To: "waxhead@dirtcellar.net" <waxhead@dirtcellar.net>,
	Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: BTRFS list of grievances
Date: Fri, 27 Sep 2024 17:44:25 +0000	[thread overview]
Message-ID: <20e5cba7-2112-4023-9994-5fac115abc2a@meta.com> (raw)
In-Reply-To: <aebe9671-6f44-9d20-f077-b19e09fa1fcd@dirtcellar.net>

On 27/9/24 12:20, waxhead wrote:
> 2. USE DEVICE ID's EVERYWHERE INSTEAD OF /dev/sdX:
> 4. THE ABILITY TO SET A LABEL FOR A DEVICE ID:

I think the view is that this is the job of udev, not btrfs. Presumably 
you can use udev rules to give block devices arbitrary names.
Maybe it might be useful if there was an option to btrfs-progs so that 
it printed the symlink names in /dev/disk/by-partlabel if present.

> 9. ABILITY TO MERGE / CONSUME EXISTING BTRFS:

Yeah, I've had the same idea - this is something that's definitely 
possible, it just needs someone to implement it.

If we're writing a wishlist, I'll add:

BAD SECTOR TREE

i.e. a list of sectors known to be bad that the allocator should avoid, 
in the same way that it avoids the superblocks. NTFS has something 
similar, and I think ext2 does too.

Mark

  parent reply	other threads:[~2024-09-27 17:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-27 11:20 BTRFS list of grievances waxhead
2024-09-27 16:27 ` Roman Mamedov
2024-09-27 18:05   ` Remi Gauvin
2024-09-27 19:01     ` Colin S
2024-10-02 19:31       ` Chris Murphy
2024-10-02 23:18         ` Colin S
2024-09-28 10:15   ` Paul Jones
2024-09-28 17:51   ` Roman Mamedov
2024-09-27 17:44 ` Mark Harmstone [this message]
2024-09-30 21:43 ` Goffredo Baroncelli
2024-10-03 17:10   ` Goffredo Baroncelli
2024-10-03 17:26     ` Remi Gauvin
2024-10-03 18:24       ` Goffredo Baroncelli
2024-10-03 18:32         ` Remi Gauvin

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=20e5cba7-2112-4023-9994-5fac115abc2a@meta.com \
    --to=maharmstone@meta.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=waxhead@dirtcellar.net \
    /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