Oh sorry, I hadn't fully realized that as indicated by the title, this was with /forcefsck set. In that case, as I said, since the filesystem is still read-only, the /forcefsck flag can't be cleared - nor should it be cleared at this point, because it covers all mounts and not just root.
So an alternative interface to creating a /forcefsck file would have to be used, one that doesn't reside on the filesystem itself and can be set and cleared for individual filesystems separately - for example, the filesystem internal data. -- Pierre Ynard
