On 08/12, John Kehayias via Linux-f2fs-devel wrote: > Hello again, > > As this is the main disk for a homeserver, I was anxious to get it working > again. After reading about what seemed like the same exact problem here: > https://old.reddit.com/r/linuxquestions/comments/whomdc/expanded_f2fs_cant_mount/ > I thought using a newer f2fs-tools would help (I think I ended up with > latest git commit). As I reported earlier though, resize won't do anything > (already resized). So I thought about shrinking, though it might be risky. > > First, I tested with a disk image, made with dd and mounted with sudo > udisksctl loop-setup -f disk.img. Then I could operate on the loop device > with that partition, /dev/loop0p2 in my case. So I tried shrinking, bolstered > by the good experiences reported in > https://www.mail-archive.com/[email protected]/msg23214.html > Since the size was something like twice the data on it, I didn't worry too > much about how much smaller I made it. That was then mountable! So I resized > back to the full size, and that still worked. Bonus: working on the disk > image was much faster on my SSD than the original memory card. > > I made another fresh image for backup and then repeated these steps on the > actual disk (memory card): resize.f2fs to shrink slightly (with -t <some > sector amount less than max>) and then resize it fully. Everything worked! > > I have logs of the resizes and fscks happy to share though I know this has > been reported and seems fixed in current versions.
Ah, so the recent f2fs-tools addressed your problem, right? > > John > > > _______________________________________________ > Linux-f2fs-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel _______________________________________________ Linux-f2fs-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
