Doesn't matter with which filesytem the partition was formatted - the first commandment of any any any filesystem is that it has to get from the <whatever handles the device> in some real or abstract way the from/to-range of where it is allowed to exist.

When then the formatting of the filesystem kicks in, the filesystem prepares all its structures, etc... all within that range.

When you then mount that filesystem, its "universe" will be only within those boundaries.

It's therefore (almost) impossible that a filesystem corrupts your partition (as it is aware of only stuff related to its own universe, which in turn is contained within the partition boudaries), unless you're using some untested-bleeding-edge-filesystem-version and that's not possible unless you're part of the team that develops it.

Therefore:
In your case the issue must most most most probably be that you or somebody else screwed something up and/or that you mount the "thing" (partition, disk, file, whatever) incorrectly and/or that something else happend BUT FOR SURE WITH 99.9999999% PROBABILITY your partition did not get corrupted because of the filesystem becoming full - we would have thousands of such cases if this were true.

You're not posting enough details for us to be able to help.