Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#42624 - [f2fs-tools] fsck.f2fs does not work properly
Attached to Project:
Arch Linux
Opened by Alois Nespor (anespor) - Thursday, 30 October 2014, 15:36 GMT
Last edited by Tobias Powalowski (tpowa) - Thursday, 05 March 2015, 07:44 GMT
Opened by Alois Nespor (anespor) - Thursday, 30 October 2014, 15:36 GMT
Last edited by Tobias Powalowski (tpowa) - Thursday, 05 March 2015, 07:44 GMT
|
Detailsfsck.f2fs does not work properly in version 1.4.0.
Please upgrade to the latest git version, where it is already fixed, if you can. |
This task depends upon
Closed by Tobias Powalowski (tpowa)
Thursday, 05 March 2015, 07:44 GMT
Reason for closing: Fixed
Additional comments about closing: 1.4.1-1
Thursday, 05 March 2015, 07:44 GMT
Reason for closing: Fixed
Additional comments about closing: 1.4.1-1
Comment by Doug Newgard (Scimmia) -
Thursday, 30 October 2014, 16:02 GMT
This is a pretty lousy report. What's the problem? What fixed it? Was there an upstream bug report? If it's that serious, why isn't upstream making a release?
Comment by Alois Nespor (anespor) -
Thursday, 30 October 2014, 16:32 GMT
This is a pretty lousy report, because it is hard to explain - because the error after repair at the moment can not be repeated. The point is that f2fs filesystem created directories with the same name twice (must have diacritical marks this directory). Then such a directory can not be deleted. Version 1.4.0 (f2fs) ends with some statement and does not repair (obviously a bug - but already fixed - who commit it exactly I do not know). I try latest git version and works. Because it could affect more users, I asked for an update.