linux-erofs.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Igor Eisberg <igoreisberg@gmail.com>
To: linux-erofs@lists.ozlabs.org
Subject: An issue with erofsfuse
Date: Fri, 20 Aug 2021 15:34:05 +0300	[thread overview]
Message-ID: <CABjEcnGniBcadC4DDV4xCio8UmZyhSGWt+_gi_ESbYwoOQ2E0w@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 957 bytes --]

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 sudo permissions
on this server.

Our only choice is to use erofsfuse to mount an Android image (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 (where 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)"

Notes:
* Only extremely small (< 1 KB) files which are stored uncompressed 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.

[-- Attachment #2: Type: text/html, Size: 1198 bytes --]

             reply	other threads:[~2021-08-20 12:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-20 12:34 Igor Eisberg [this message]
2021-08-20 12:48 ` An issue with erofsfuse Gao Xiang
2021-08-20 13:16   ` Igor Eisberg
2021-08-20 13:26     ` Huang Jianan
2021-08-20 13:26     ` Gao Xiang
2021-08-20 13:35       ` Igor Eisberg
2021-08-20 13:42         ` Gao Xiang
2021-08-20 13:58           ` Igor Eisberg
2021-08-20 14:05             ` Gao Xiang
2021-08-20 14:14               ` Igor Eisberg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CABjEcnGniBcadC4DDV4xCio8UmZyhSGWt+_gi_ESbYwoOQ2E0w@mail.gmail.com \
    --to=igoreisberg@gmail.com \
    --cc=linux-erofs@lists.ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).