public inbox for linux-bcachefs@vger.kernel.org
 help / color / mirror / Atom feed
From: BP25 <bp25@posteo.net>
To: linux-bcachefs@vger.kernel.org
Subject: Version Control capabilities plus two small unrelated questions
Date: Wed, 24 Dec 2025 16:02:01 +0000	[thread overview]
Message-ID: <f284018630d0a24414d38028cd397345@posteo.net> (raw)

Hello, would someone kindly advise whether bcachefs supports file 
versioning, somewhat in the spirit of Stallman (lecture at KTH Sweden in 
1986) where files are individually versioned (as opposed as taking 
snapshots of entire volumes) but the versions are not just ordinary 
distinct files, they are hidden files connected with each other.

In particular is there a standard way to 'follow' the same file along 
its snapshotted versions? Say, ask bcachefs to return the list of 
snapshotted versions by giving input this or that file in the current 
version of the filesystem? Note that if such file was deleted and 
another with the same name created I don't want that new file also to 
show up. And related question, is there any command that would list the 
snapshotted files which have no corresponding in the current version of 
the file system (for example because I deleted such file after having 
snapshotted it)?

First small unrelated question: do you confirm that standard Guix is 
currently incompatible with bcachefs as root filesystem and is there any 
plan to patch Guix so that it's possible (with standard Guix 
installation)? Note: "Currently Guix System only supports ext4, btrfs, 
JFS, F2FS, and XFS file systems. In particular, code that reads file 
system UUIDs and labels only works for these file system types."

Why does the generation number in bcachefs snapshots starts from U32max 
and goes down, instead of the naive start from 0 and goes up? There must 
be some strong conceptual reason for doing the first because I see 
already a few small conceptual reasons to do the second.

  Please CC or BCC me because I'm not subscribed ro the mailing list.


             reply	other threads:[~2025-12-24 16:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-24 16:02 BP25 [this message]
2025-12-24 16:11 ` Version Control capabilities plus two small unrelated questions BP25
2025-12-26 17:09 ` Kent Overstreet
2025-12-27  0:08   ` BP25
2025-12-30 23:42   ` Franz Schultz

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=f284018630d0a24414d38028cd397345@posteo.net \
    --to=bp25@posteo.net \
    --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