Your message dated Sat, 21 Nov 2026 11:29:38 +0100
with message-id <[email protected]>
and subject line Re: Bug#1154660: btrfs: no longer use passno=0 in fstab.d, 
since fsck.btrfs exists thesedays
has caused the Debian Bug report #1154660,
regarding btrfs: no longer use passno=0 in fstab.d, since fsck.btrfs exists 
thesedays
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1154660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1154660
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: partman-btrfs
Version: 67
X-Debbugs-CC: Nicholas D Steeves <[email protected]>


I found commit c2d2b5e6 [1]
"Set btrfs fstab passno to zero, as there is no btrfs fsck scripts."

But we have fsck.btrfs for years now.
Shouldn't that be changed, to allow for automatic filesystem checks?

Or is there a good reason to still leave them disabled?


Holger


[1]
<https://salsa.debian.org/installer-team/partman-btrfs/-/commit/c2d2b5e64f89c612bd29b5b38e83c79a6522dc69>




-- 
Sent from /e/ OS on Fairphone3

--- End Message ---
--- Begin Message ---

Am 21. November 2026 10:16:13 MEZ schrieb Pascal Hambourg 
<[email protected]>:
>       Traditional filesystems need to run their respective fsck utility
>       in case the  filesystem  was  not  unmounted
>       cleanly  and the log needs to be replayed before mount. This is
>       not needed for BTRFS. You should set fs_passno to 0.

Interesting.

Closing this report.


Holger

-- 
Sent from /e/ OS on Fairphone3

--- End Message ---

Reply via email to