[Bug 2063369] Re: e2image reports invalid argument when used with big partitions
Theodore Ts'o
2063369 at bugs.launchpad.net
Thu Apr 25 13:38:53 UTC 2024
If the file system has a limit on the size of the file (for example,
ext4 has a maximum file size of 16TB), then when you do a relative seek
via llseek(fd, offset, SEEK_CURR), the system call will return EINVAL.
This is what is causing the error.
If you want to create a raw image of a very large file system, you'll
either to write it to a block device which is sufficiently large, or
you'll have to make sure the destination file system can support a file
size of that particular length. (And, of course, has sufficient free
space to hold the raw image in the first place.)
Another workaround is to compress the file, e.g., "e2image -pr /dev/md3
- | gzip > md3.e2i.gz"
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, 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
More information about the foundations-bugs
mailing list