On Fri, 20 Aug 2021 at 16:27, Gao Xiang <xiang@kernel.org> wrote:

On Fri, Aug 20, 2021 at 04:16:= 20PM +0300, Igor Eisberg wrote:
> You're quicker than expected, thanks for answering.
> Not sure how to check if lz4 was builtin, but considering that erofsfu= se is
> only about 34.5KB (stripped) I would guess not?
> Here's the output of erofsfuse -d (it prints this but never exists= back to
> shell unless I do Ctrl+C):

Yeah, it will run erofsfuse in foreground, and you need to access the
erofs compressed files, and then check the printed result.

But I think there is a easier way to check if lz4 was linked, just type
ldd <your erofsfuse program>

if lz4 was linked, it will print some message like below:
=C2=A0 =C2=A0 =C2=A0 =C2=A0 linux-vdso.so.1 (0x00007ffee176e000)
=C2=A0 =C2=A0 =C2=A0 =C2=A0 libfuse.so.2 =3D> /lib/x86_64-linux-gnu/= libfuse.so.2 (0x00007f8e21f24000)
=C2=A0 =C2=A0 =C2=A0 =C2=A0 liblz4.so.1 =3D> /lib/x86_64-linux-gnu/l= iblz4.so.1 (0x00007f8e21f01000)
=C2=A0 =C2=A0 =C2=A0 =C2=A0 libpthread.so.0 =3D> /lib/x86_64-linux-g= nu/libpthread.so.0 (0x00007f8e21ee0000)
=C2=A0 =C2=A0 =C2=A0 =C2=A0 libc.so.6 =3D> /lib/x86_64-linux-gnu/lib= c.so.6 (0x00007f8e21d1f000)
=C2=A0 =C2=A0 =C2=A0 =C2=A0 libdl.so.2 =3D> /lib/x86_64-linux-gnu/li= bdl.so.2 (0x00007f8e21d1a000)
=C2=A0 =C2=A0 =C2=A0 =C2=A0 /lib64/ld-linux-x86-64.so.2 (0x00007f8e21f91000= )

Thanks,
Gao Xiang

>
> erofsfuse 1.3
> >
> > disk: product.img
> >
> > mountpoint: product-mnt
> >
> > dbglevel: 7
> >
> > FUSE library version: 2.9.9
> >
> > nullpath_ok: 0
> >
> > nopath: 0
> >
> > utime_omit_ok: 0
> >
> > unique: 1, opcode: INIT (26), nodeid: 0, insize: 56, pid: 0
> >
> > INIT: 7.27
> >
> > flags=3D0x003ffffb
> >
> > max_readahead=3D0x00020000
> >
> > EROFS: erofsfuse_init() Line[23] Using FUSE protocol 7.27
> >
> >=C2=A0 =C2=A0 INIT: 7.19
> >
> >=C2=A0 =C2=A0 flags=3D0x00000011
> >
> >=C2=A0 =C2=A0 max_readahead=3D0x00020000
> >
> >=C2=A0 =C2=A0 max_write=3D0x00020000
> >
> >=C2=A0 =C2=A0 max_background=3D0
> >
> >=C2=A0 =C2=A0 congestion_threshold=3D0
> >
> >=C2=A0 =C2=A0 unique: 1, success, outsize: 40
> >
> >
> On Fri, 20 Aug 2021 at 15:49, Gao Xiang <xiang@kernel.org> wrote:
>
> > Hi Igor,
> >
> > On Fri, Aug 20, 2021 at 03:34:05PM +0300, Igor Eisberg wrote:
> > > Hey there, getting straight to the point.
> > > Our team is using Debian 10, in which erofs mounting is not = supported and
> > > we have no option of updating the kernel, nor do we have sud= o permissions
> > > on this server.
> > >
> > > Our only choice is to use erofsfuse to mount an Android imag= e
> > (compression
> > > was used on that image), for the sole purpose of extracting = its contents
> > to
> > > another folder for processing.
> > > Tried on Debian 10, pop_OS! and even the latest Kubuntu (whe= re native
> > > mounting is supported), but on all of them I could not copy = files which
> > are
> > > compressed from the mounted image to another location (ext4 = file system).
> > >
> > > The error I'm getting is: "Operation not supported = (95)"
> > >
> >
> > Thanks for your feedback.
> >
> > Could you check if lz4 was built-in when building erofsfuse? I gu= ess
> > that is the reason (lack of lz4 support builtin).
> >
> > If not, could you add -d to erofsfuse when starting up?
> >
> > Thanks,
> > Gao Xiang
> >
> > > Notes:
> > > * Only extremely small (< 1 KB) files which are stored un= compressed are
> > > copied successfully.
> > > * Copying works perfectly when mounting the image with "= ;sudo mount" on
> > the
> > > latest Kubuntu, so it has to be something with erofsfuse. > > >
> > > Anything you can do to help resolve this?
> > >
> > > Best,
> > > Igor.
> >