Just how dangerous is sending SIGINT to resize2fs tasked with shrinking?

I inherited an old PC-server (quad Pentium 4) that only had partitions for /, /boot and swap (RAID1 with 2 1T SATA disks), but needed to update the distro (from CentOS 6.9). I decided to create a new partition so that the one containing / could be formatted. But I forgot to add the -p flag to resize2fs and now it's silently staring back at me and I can't tell how much longer it could take (it's been at it for 50+ hours). Now, I know that shrinking a filesystem [can take a long time](https://serverfault.com/q/213693/426271) , but while I could wait for [100 hours](https://serverfault.com/q/436224/426271) , something like [800 hours is out of the question](https://bbs.archlinux.org/viewtopic.php?id=147563) . Here's what I'm thinking at the moment: - Go ahead with the Ctrl+C && e2fsck. - Mount the partition and manually delete 100G+ worth of data that serves us no purpose. - Start from the top with resize2fs -p ... But I haven't been able to find [consensus](https://www.spinics.net/lists/linux-ext4/msg51307.html) on just how [dangerous](https://serverfault.com/a/501623/426271) it is to send SIGINT to resize2fs. I do have an extra backup of the important information, but would still like to do this without corrupting the filesystem. And yes, I'm aware it might be faster to just install the distro from scratch and restore my backup. **Update**: I decided to interrupt it. And everything seems to be fine, but the question still stands. I'm still curious.