[2019-03-13 18:20] Thorsten Glaser
> On Wed, 13 Mar 2019, Dmitry Bogatov wrote:
>
> > Sorry, I am totally confused. Mind to make a patch?
>
> Eh, just donât drop support, and at best document that
> people should use the new tune2fs option for ext[234].
>
> No sense in making a patch, weâve
> And, I can't see standalone tune2fs even in unstable:
>
> $ apt-file find /bin/tune2fs
> android-sdk: /usr/lib/android-sdk/tools/bin/tune2fs
/sbin/tune2fs is shipped by e2fsprogs.
--
Pierre Ynard
[2019-03-11 19:27] Thorsten Glaser
> On Mon, 11 Mar 2019, Dmitry Bogatov wrote:
> > So, you propose that we:
> > * drop all checks for /forcecheck
>
> No!
>
> > * document this fact in NEWS file
> > * write documentation, that e[2-4]fs users should use tune2fs tool
> >instead
>
> Yes.
On Wed, 13 Mar 2019, Dmitry Bogatov wrote:
> Sorry, I am totally confused. Mind to make a patch?
Eh, just don’t drop support, and at best document that
people should use the new tune2fs option for ext[234].
No sense in making a patch, we’ve frozen.
bye,
//mirabilos
--
«MyISAM tables -will-
On Mon, 11 Mar 2019, Dmitry Bogatov wrote:
> So, you propose that we:
> * drop all checks for /forcecheck
No!
> * document this fact in NEWS file
> * write documentation, that e[2-4]fs users should use tune2fs tool
>instead
Yes.
//mirabilos
--
tarent solutions GmbH
Rochusstraße 2-4,
[2019-03-09 21:57] Thorsten Glaser
> > But I really want to have some transition plan to get rid of
> > /forcecheck, something like:
>
> … you might like that tune2fs can now (1.45.0-1, not yet in
> buster, officially not likely to make it but we can hope) set
> a flag force_fsck that next
On Sat, 9 Mar 2019, Pierre Ynard wrote:
> /fastboot and /forcefsck are created by `shutdown -f` and `shutdown -F`
Oh, I didn’t know that, I just sudo touch them as used to on Unix.
> the shutdown binary, it could create /forcefsck or /run/forcefsck, which
/run is a tmpfs.
> would then be
> > As you convincingly remarked below, we may want honor `test -f /forcecheck'
> > for every filesystem, whose `fsck' supports `-f' option. As far as I
> > follow the thread, it is:
> >
> > ext2 ext3 ext4 reiserfs
>
> Interesting that acceptance of that parameter is so low.
fsck.minix
On Sat, 9 Mar 2019, Dmitry Bogatov wrote:
> As you convincingly remarked below, we may want honor `test -f /forcecheck'
> for every filesystem, whose `fsck' supports `-f' option. As far as I
> follow the thread, it is:
>
> ext2 ext3 ext4 reiserfs
Interesting that acceptance of that
[2019-03-07 15:15] Pierre Ynard
> > Sounds reasonable. Will you make patch?
>
> What does ext* expand to, what's the list of ext filesystem types for
> which we want to honor forcefsck? ext2, ext3 and ext4?
As you convincingly remarked below, we may want honor `test -f /forcecheck'
for every
> Sounds reasonable. Will you make patch?
What does ext* expand to, what's the list of ext filesystem types for
which we want to honor forcefsck? ext2, ext3 and ext4?
> What is relations of reiserfs and /forcecheck convention on timeline?
> We want to deprecate /forcecheck, and making it respect
[2019-03-05 02:50] Pierre Ynard
> reopen 686895
> thanks
>
> /etc/init.d/checkfs.sh also checks forcefsck to pass -f to fsck,
> so it needs to be fixed too. It won't be as simple as checkroot.sh
> because fsck -A can apply to any number of filesystems of any type and
> checkfs.sh doesn't track
reopen 686895
thanks
/etc/init.d/checkfs.sh also checks forcefsck to pass -f to fsck,
so it needs to be fixed too. It won't be as simple as checkroot.sh
because fsck -A can apply to any number of filesystems of any type and
checkfs.sh doesn't track specifics when calling it.
Perhaps the simplest
Hi Dmitry,
Dmitry Bogatov writes:
> control: tags -1 +patch
>
> [2014-11-24 22:30] Petter Reinholdtsen
>> Given that -f is force only for ext*, I suspect a more sensible
>> approach is to only enable forcefsck for ext*, not disable it for
>> btrfs.
>
> Like this?
>
> diff --git
control: tags -1 +patch
[2014-11-24 22:30] Petter Reinholdtsen
> Given that -f is force only for ext*, I suspect a more sensible
> approach is to only enable forcefsck for ext*, not disable it for
> btrfs.
Like this?
diff --git a/debian/src/initscripts/etc/init.d/checkroot.sh
Control: tags -1 - patch
Given that -f is force only for ext*, I suspect a more sensible approach
is to only enable forcefsck for ext*, not disable it for btrfs.
--
Happy hacking
Petter Reinholdtsen
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
tag 686895 + patch
thanks
Hi,
I ran into the very same bug. It seems to be a more conceptual problem than
btrfs-related, but for making btrfsck work, I added this patch:
--- checkroot.sh2014-02-16 23:34:17.349214647 +
+++ /etc/init.d/checkroot.sh2014-02-16
17 matches
Mail list logo
