Hi, Il 29/03/19 11:12, Alexander E. Patrakov ha scritto: > Dear Maintainer, > > approximately 1.5 years ago I have discovered a reproducible case > of filesystem corruption by fstransform, and reported it upstream: > > https://github.com/cosmos72/fstransform/issues/13 > > I understand that the reproducer is with non-default options, > but it may also apply with the default options to systems with > huge storage and relatively small amount of RAM.
Thanks for reporting this bug. I can reproduce it, but given that the upstream issue has been open for more than a year I doubt it will be solved soon. I agree that having a silent failure with data corruption is not nice towards the user, but given that fstransform displays prominent warnings about the fact that it can easily screw up data, I think it is not a ground for removing the package altogether. The package can still be helpful to the users, as long as the users are aware of the risks connected with it. So what I would rather do is to modify the starting up message so that the user is aware that running fstransform in low resources environments can lead to data corruption. Of course, if the user goes to plumbing level and manually changes internal options, then risks for breakages is really to be expected. Of course a proper fix for the bug would be better, but in the meantime I think this is enough to fix this RC bug and keep fstransform in the release without putting to much risk on the users. Thanks, Giovanni. -- Giovanni Mascellani <g.mascell...@gmail.com> Postdoc researcher - Université Libre de Bruxelles
signature.asc
Description: OpenPGP digital signature
