Eric Sandeen wrote:
> Bas van Schaik wrote:
>
>
>> Why is e2image refusing to restore the metadata, and what does "File too
>> large" mean?
>>
> How big are things really? stracing the command would show you what is
> returning the error...
>
The image file is 35335922 kbytes (= about 33GB), but is of course
sparse and actually uses 4218560 kbytes (= about 4 GB). The original
filesystem is 550502400 blocks long (block size 4096, number of inodes:
275251200).
The last few lines of output when using strace:
> close(4) = 0
> open("/usr/lib/gconv/ISO8859-1.so", O_RDONLY) = 4
> read(4, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\200\4\0"...,
> 512) = 512
> fstat64(4, {st_mode=S_IFREG|0644, st_size=9436, ...}) = 0
> mmap2(NULL, 8228, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 4,
> 0) = 0xb1ab3000
> mmap2(0xb1ab4000, 8192, PROT_READ|PROT_WRITE,
> MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 4, 0x1) = 0xb1ab4000
> close(4) = 0
> write(2, "e2image-pre-e2fsck-snapshot_2008"...,
> 55e2image-pre-e2fsck-snapshot_2008-03-06: File too large
> ) = 55
> exit_group(1) = ?
> Process 6218 detached
I can't see what's going wrong here.
-- Bas
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
