Description of problem: I have tried setting up a f2fs USB with various methods (including GNOME Disks, KDE Partition Manager, gparted and mkfs.f2fs and the outcome is always a read-only USB Version-Release number of selected component (if applicable): f2fs-tools 1.8.0 (also tried on 1.6.0 with the same result) How reproducible: Format a USB drive to f2fs filesystem type and then try to write any file to it. Steps to Reproduce: 1. Create a filesystem type of f2fs on a USB drive with any program e.g. gparted 2. Remove USB drive safely after creation and re-insert (to make sure the system recognizes it normally) 3. Try to write a file to the drive Actual results: The USB is read-only Expected results: The USB can be written to with any file Additional info:
I've been advised that this bug has something to do with how KDE Partition Manager/gparted are not running chown on the USB drive after creation of the f2fs partition.
(In reply to safestate from comment #1) > I've been advised that this bug has something to do with how KDE Partition > Manager/gparted are not running chown on the USB drive after creation of the > f2fs partition. Who suggested you that this is a partitionmanager/gparted error? What "chown" command should be run that it's not?
(In reply to Mattia Verga from comment #2) > (In reply to safestate from comment #1) > > I've been advised that this bug has something to do with how KDE Partition > > Manager/gparted are not running chown on the USB drive after creation of the > > f2fs partition. > > Who suggested you that this is a partitionmanager/gparted error? What > "chown" command should be run that it's not? Some person on Reddit..
He also advised that chown needs to be run on the drive, as by default drives/folders are owned by root. (Not sure if this was correct but whatever)
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.