linux-bcachefs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Steigerwald <martin@lichtvoll.de>
To: linux-bcachefs@vger.kernel.org
Subject: Questions related to BCacheFS
Date: Sat, 18 Nov 2023 20:15:50 +0100	[thread overview]
Message-ID: <23311511.6Emhk5qWAg@lichtvoll.de> (raw)

Hi!

Awesome that BCacheFS is finally merged! Many thanks to everyone who made 
this happen. I appreciate it!

I am writing an article about BCacheFS. I am willing to provide a link 
once it is published. It will be in German language.

I do have a few questions:

1) Is discard supported? fstrim says it is not. However /sys/fs/bcachefs/
UUID/options/discard shows "1". BCacheFS User manual Principles of 
Operations mentions it at a device option. I am not completely sure how 
these work. Auto-detected and just IOCTL for fstrim missing?

2) What are the plans for scrubbing? Right now it is not yet implemented, 
right?

3) Is the documentation of mount and other options in
https://bcachefs.org/bcachefs-principles-of-operation.pdf complete? If 
not, care to elaborate what is missing?

4) What are the plans or ideas for documentation? I specially ask as there 
does not seem to be a manpage like mount.bcachefs or mkfs.bcachefs yet. 
There is no mention of bcachefs in mount manpage either. And no bcachefs 
manpage in section 5 like with btrfs or xfs. There is a bcachefs manpage 
in section 8 which for example for a complete list of mount options refers 
to above Principles of Operation user manual. And it has information on 
"bcachefs format" and some other sub commands. I bet it is still too early 
or maybe you have different plans on how to go about documentation. 
Anything you can share already regarding this?

5) Is the feature implementation status on bcachefs.org up-to-date? How 
about the one in Principles of Operation user manual? Is any of these more 
up-to-date? If anything is missing from these, care to elaborate?

6) What is the status for xxhash checksums? They are mentioned as an 
option in the output of "bcachefs format". Yet no mention of it in 
bcachefs manpage nor in Principles of Operation user manual.

7) On mounting BCacheFS without compression enabled on 6.7-rc1, shortly 
before rc2, commit 791c8ab095f71327899023223940dd52257a4173 also LZ4 
compression modules  lz4hc_compress and lz4_compress are loaded. Why?

8) Regarding bcachefs-tools. More out of curiosity, cause there is already 
a bcachefs-tools package in Debian repo, albeit only version 1.2. I see a 
"debian" directory, however version number is 1.0.8-2~bpo8+1 while 
compiling via make gives version 1.33. So I suppose packaging information 
is not up to date? For now I am going with "make install" from bcachefs-
tools git repo, as package in Debian repo is outdated.

9) What is the preferred way to report bugs? Mailing list? Kernel bug 
tracker? Both? Anything else?

10) Anything you think an article about BCacheFS should absolutely 
mention?

There may be more at a later time. :)

Best,
-- 
Martin



             reply	other threads:[~2023-11-18 19:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-18 19:15 Martin Steigerwald [this message]
2023-11-18 19:50 ` Questions related to BCacheFS Kent Overstreet
2023-11-18 20:57   ` Martin Steigerwald
2023-11-18 21:07     ` Kent Overstreet
2023-11-18 23:15       ` Martin Steigerwald
2023-11-18 23:42         ` Kent Overstreet
2023-11-19 11:13           ` Martin Steigerwald
2023-11-19 16:43             ` Martin Steigerwald
2023-11-19 23:10             ` Kent Overstreet
2023-11-20 17:34               ` Martin Steigerwald
2023-12-03 16:58               ` Martin Steigerwald
2023-12-18 16:50                 ` Martin Steigerwald
2023-12-28 22:29     ` deletion time of big files (was: Re: Questions related to BCacheFS) Martin Steigerwald
2023-12-29 18:48       ` Kent Overstreet
2023-12-30 10:51         ` Martin Steigerwald

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=23311511.6Emhk5qWAg@lichtvoll.de \
    --to=martin@lichtvoll.de \
    --cc=linux-bcachefs@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 NNTP newsgroup(s).