Well ... the tool could print all possible reasons of the failure to avoid confusion. Writing one byte at the last position seems to me a good solution. If that's acceptable, it would really improve the user experience. Thank you.
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/2063369 Title: e2image reports invalid argument when used with big partitions Status in e2fsprogs package in Ubuntu: New Bug description: It seems e2image is unable to work correctly with large filesystems. I get the following error with etx4 on top of 48TB RAID5 array. # e2image -pr /dev/md3 md3.e2i e2image 1.46.5 (30-Dec-2021) Scanning inodes... Copying 802818 / 1547571 blocks (52%) 00:02:21 remaining at 20.50 MB/sseek_relative: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2063369/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
