On Tue, Dec 24, 2024 at 3:54 AM Michael Tokarev wrote:
>
> Hi!
>
> The no-unsafe-io workaround in dpkg was needed for 2005-era ext2fs
> issues, where a power-cut in the middle of filesystem metadata
> operation (which dpkg does a lot) might result in in unconsistent
> filesystem state. This worka
Hi,
On 12/24/24 18:54, Michael Tokarev wrote:
The no-unsafe-io workaround in dpkg was needed for 2005-era ext2fs
issues, where a power-cut in the middle of filesystem metadata
operation (which dpkg does a lot) might result in in unconsistent
filesystem state.
The thing it protects against is
* Andreas Metzler [241224 11:53]:
> On 2024-12-23 Gioele Barabucci wrote:
> > On 22/12/24 06:56, Andreas Metzler wrote:
> >> On 2024-12-22 Sean Whitton wrote:
> >>> On Sat 21 Dec 2024 at 10:23pm +01, Gioele Barabucci wrote:
>
> We have a mechanism for when you feel responsible: "Maintainer
Hi Michael,
That sounds like a neat idea. Especially, with the proliferation of more
complex filesystems like BTRFS, the penalty of calling fsyc() a lot becomes
very visible. I’m not a BTRFS user myself, but I always hear comments and
discuss about it.
Removing this workaround can help to remo
Hi,
On Tue, Dec 24, 2024 at 6:54 AM Michael Tokarev wrote:
>
> Hi!
>
> The no-unsafe-io workaround in dpkg was needed for 2005-era ext2fs
> issues, where a power-cut in the middle of filesystem metadata
> operation (which dpkg does a lot) might result in in unconsistent
> filesystem state. This
Package: wnpp
Severity: wishlist
Owner: Tobias Frost
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: ondelsolver
Version : (does not release with version number)
Upstream Contact: cont...@ondsel.com
* URL : https://github.com/Ondsel-Development/OndselSolver
On 2024-12-23 Gioele Barabucci wrote:
> On 22/12/24 06:56, Andreas Metzler wrote:
>> On 2024-12-22 Sean Whitton wrote:
>>> On Sat 21 Dec 2024 at 10:23pm +01, Gioele Barabucci wrote:
We have a mechanism for when you feel responsible: "Maintainer: $me".
What is being discussed here is a
Hi,
Le 2024-12-24 10:54, Michael Tokarev a écrit :
How about turning this option - force-unsafe-io - to on by default
in 2025? That would be a great present for 2025 New Year! :)
That sounds like a sensible idea to me.
Cheers, and best wishes,
--
Julien Plissonneau Duquène
Hi!
The no-unsafe-io workaround in dpkg was needed for 2005-era ext2fs
issues, where a power-cut in the middle of filesystem metadata
operation (which dpkg does a lot) might result in in unconsistent
filesystem state. This workaround slowed down dpkg operations
quite significantly (and has been
9 matches
Mail list logo
