Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

btrfs: setting a label is only supported on a mount point

未关闭
#966 3 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
8/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
停滞
技术栈
c
领域
backend

调研方向

The payload names no source files, tests or entry points, so there is no obvious place to start. The reporter says the mountpoint-only behaviour is not a real problem and that changing the API would break libblockdev, so the first step is a maintainer decision on whether device-based btrfs labelling is wanted at all. Done would mean that decision is recorded on the issue, with or without a follow-up change.

由索引模型根据 Issue 内容生成。

描述

I noticed that setting a label is only supported via a mountpoint for btrfs, while in theory a label can be set on a device.

btrfs filesystem label [<device>|<mountpoint>] [<newlabel>]

Most other set_label functions seem to use the device. Which in Cockpit leads a somewhat inconsistent experience when the filesystem is not mounted. (In theory we can work around it by first mounting it temporary, set label and umount).

Changing the API over to a mountpoint would break libblockdev's API so I guess that is a not an option and this isn't a real "breaking" or high priority issue for us. (Read: no issue at all)

主要语言
C
星标
137
派生
64
平均合并
1 天 5 小时
30 天内合并 PR
3

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

storaged-project/libblockdev 的其他 Issue

查看 storaged-project/libblockdev 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。