I got a typical zip error: Output file write failure (write error on zip file) but I did not see any logs in /var/log/syslog or /var/log/messages. I've attached my ssd into another computer with specs:

Dell optiplex 9020
intel core i5-4570
intel hd graphics 4600
Adata 240 GB ssd
Fedora Linux 38
kernel version Linux 6.2.15-300.fc38.x86_64

perhaps zip and find together can zip up files and folders in smaller chunks instead of unmanageable chunks. Is this possible?

When using these are only supposed to zip folders which shouldn't be a heavy load on this system but instead it gives me

You don't want -type d, that only adds directories to the zip. And I don't think you need the -r (find is doing the recursive op for you).

Try this:

find ./sdcard -print | xargs zip -0 /home/username/Documents/archive.zip

Which approximates the '+' sign on the end of your find command but perhaps it might be broken.

What does xargs do in this syntax ? I am receiving alot of zip warning: name not matched lines in the output

The funny thing is that I am trying to use the same find and zip commands on a new pixel 7 device and it seems to not give me zip I/O errors. The space on my galaxy s8 is 63.77 GB/64 GB and I have a bunch of different smb and ftp apps installed. I just did a test on the pixel 7 and it is at the moment zipping the DCIM/Camera folder without any issues including .mp4 and .jpg files. It seems like there is an actual problem on the s8 weather its conflicting apps or a software issue with android 9.

That means it is an error on the phone, it is independent from that find command or zip or anything else. But we don't know anything about the phone, sd card, configuration and environment, hard to say anything. Can you use it with the phone at all?

What do you mean ? I can still use my galaxy s8 normally but it's just that there are many apps and the storage is near to 64 GB the phone works fine i can use the apps and stuff. What information do you need about the phone ? I am not using an sdcard, there is no micro sd card inside the phone

To make troubleshooting this easier, would you like remote assistance of my phone so that we can see in real time what's happening?

Since you gave no details actually I don't know your setup. What I only see is that i/o error, which means some device cannot be read. I have no idea what is exactly that directory (named sdcard ar DCIM), but it looks like it is inaccessible.
The random error may mean it is only a problem with your cable, but actually I'm not really sure about that.
You have to identify what caused this i/o error (and on exactly on which device).

What do you mean my setup ? I've already given you what I am using...I am using a samsung galaxy s8 and fedora 38. What do you exactly mean by mode details ?

Attached Thumbnails

     

Any suggestions?

1. The error is with zip. find has nothing to do with it, IMO.
2. Logs: do right after zip fails and cat the most recently changed files to see if there’s any indication of cause.
3. How big is the source directory? Mayhaps you’re running out of room.
4. Check the man page for zip. There should be a way to have it be more verbose.

No, this i/o error occurs when accessing files inside the sdcard directory. This is a remote webdav directory and either the driver is incorrect or there is a permission issue, misconfiguration or something is wrong with the phone, but who knows?

When I typed this command it said

The source directory is 186.3 MB free as seen in the attachment



The only thing I came across is that -v is displayed after a command is successful not after it fails...

That's what I think but we need to determine what exactly is interfering. Which driver specifically ? is it the ubuntu drivers or the galaxy s8 drivers? I am using a genuine samsung OEM USB cable. At what steps does the find or zip command check for permissions? maybe we need to change permissions at some step in the process...

This is not the find or zip, it is the filesystem access itself, does not depend on the tool you use (as you could see cat produced the same error). Also you could see (based on the strace output) a simple read caused the i/o error. You might check the logs of webdav (if there were any) to see what's going on. Probably you can find something in /var/log.
this is somewhat similar: https://bugs.launchpad.net/ubuntu/+s...e/+bug/1100190

There are lots of logs in there which should I look at specifically ?

syslog, messages, kern.log, dmesg, but in general everywhere. Probably webdav has its own logfile somewhere, I don't know how is it configured.