similar to: rsync: [sender] read errors mapping "file" : Input/output error (5)

Mario, Are you running windows on the same hardware as Linux/BSD ? Is it a dual-boot system? If you have different systems for windows vslinux, it's possible there is a HW issue with one of them. Tom On 24 December 2024 7:44:16?am GMT+12:00, Mario Marietto via rsync <rsync at lists.samba.org> wrote: > What would you think if I told you that using Windows I no longer had that

What would you think if I told you that using Windows I no longer had that problem ? Would you still think that there are hardware problems ? And if so, why would they only manifest themselves using Linux and FreeBSD and not using Windows? On Mon, Dec 23, 2024 at 9:38?PM Robin Lee Powell < rlpowell at digitalkingdom.org> wrote: > Then you get to look at other hardware; CPU, RAM,

>Almost certainly your drive is going bad. On Linux I'd tell you to check dmesg for drive errors, I don't know what the FreeBSD equivalent is. But I strongly recommend that you treat that drive as "going to fail any second". I'm not sure that this is the reason. I see the error regardless of the USB disks that I use. And I have a lot of USB disks,10 disks. No,I

Happened again : root at Z390-AORUS-PRO-DEST:/mnt/zroot-133/A_FILES/Backup/FreeBSD# sudo rsync -azvvP FreeBSD-141-UFS-sdc-DarkMatter.img /mnt/sdj1/OS/Backup/BSD/FreeBSD sending incremental file list delta-transmission disabled for local transfer or --whole-file FreeBSD-141-UFS-sdc-DarkMatter.img 320,072,933,376 *100%* 80.31MB/s 1:03:20 (xfr#1, to-chk=0/1) rsync: [sender] read errors mapping

>As it's just a single file you're trying to copy, why not use cp? >Although I expect that cp will also throw an IO error at some point. Yes,I tried cp and I got the same error,that usually happens before rsync,that is able to complete the transfer until 99%. I've detached and reattached the USB disks,but I still see the error. On Mon, Dec 23, 2024 at 11:07?AM Paul Slootman via

On Mon 23 Dec 2024, Mario Marietto via rsync wrote: > > Everytime I try to copy a file from one USB disk to another one (does not > matter which one),I get this kind of error : > > > mario at Z390-AORUS-PRO-DEST:/mnt/zroot-133/A_FILES/Backup/FreeBSD# rsync > -avxHAXP FreeBSD-141-UFS-sdc-DarkMatter.img > /mnt/sdj1/OS/Backup/BSD/FreeBSD --ignore-existing > > sending

Hello. Everytime I try to copy a file from one USB disk to another one (does not matter which one),I get this kind of error : mario at Z390-AORUS-PRO-DEST:/mnt/zroot-133/A_FILES/Backup/FreeBSD# rsync -avxHAXP FreeBSD-141-UFS-sdc-DarkMatter.img /mnt/sdj1/OS/Backup/BSD/FreeBSD --ignore-existing sending incremental file list FreeBSD-141-UFS-sdc-DarkMatter.img 320,072,933,376 100% 83.57MB/s

-> Did you re-read the data and compare checksums ? Don't know how to do this. -> 2nd thought: What file systems do you use, and is there a peculiar size of the file, hitting a limit? Do I read this correct, rsync throws the error at 320,072,933,376, then continues to 640,302,152,539 bytes (file size) ? I don't know. What I know is that almost every big file reaches the 99 % /

On 23.12.24 20:44, Mario Marietto via rsync wrote: > What would you think if I told you that using Windows I no longer had that problem ? > Would you still think that there are hardware problems ? > And if so, why would they only manifest themselves using Linux and FreeBSD and not using Windows? Did you re-read the data and compare checksums? Sometimes Windows is not so good in passing

Good morning, I have a problem with ZFS: ZFS filesystem version 4 ZFS storage pool version 15 Yesterday my comp with Freebsd 8.2 releng shutdown with ad4 error detached,when I copy a big file... and after reboot in 2 wd green 1tb say me goodbye. One of them die and other with zfs errors: Apr 24 04:53:41 Flash root: ZFS: vdev I/O failure, zpool=zroot path= offset=187921768448 size=512 error=6

A friend and I mirror our music collections on each other's servers; between the two of us we have several hundred gigs of flac files. My friend runs Linux, I run FreeBSD. Recently we started playing with flac-1.1.4 (we had been using flac-1.1.2 previously) and I noticed something strange. flac-1.1.4, run with identical options on identical files, produces different output on the linux

My goal is to authenticate a Windows 2003 Server user from a FreeBSD 4.10 box via samba. A week ago I had this working. I then needed to verify the procedure and test on a fresh install. Now it doesn't work, despite doing the same steps (I think). I generated a Kerberos ticket on the w2k3 box and transfered it to the FreeBSD box. I used the ktutil command to incorporate the ticket into

Version Info: FreeBSD 9.2-RELEASE #0 r266046 AMD64, Dovecot 2.2.13, dovecot-pigeonhole-0.4.3, amavisd-new-2.8.0_2,1, clamav-0.98.4, postfix29-2.9.9_1,1, postfixadmin-2.3.6, spamassassin-3.4.0_12 (zpool data and output of dovecot -n at bottom of post) I suspect these are related problems and further that they are related to some trivial newb error I've made in my configuration, but searching

Hi I am on commit 20f51c29a99299384e840e148f02aae66bfb45be. FreeBSD freebsd.vaaraahi.com 8.0-RELEASE FreeBSD 8.0-RELEASE #0 freebsd# ./configure checking build system type... i386-unknown-freebsd8.0 checking host system type... i386-unknown-freebsd8.0 checking whether make sets $(MAKE)... yes checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default

Hi, I was trying to rebuild world on a FreeBSD 10 test system, that I had just installed. ZFS root was setup. I let the installation program do all the ZFS setup and configuration. I put root on a 5 disk encrypted raidz array. Besides the installer configuring 5 times the amount of swap space I asked for (asked for 8gb, installer put 8gb on each drive, for 40gb in total.) everything was working

On 18 Apr 2015, at 15:02, David Gessel <gessel at blackrosetech.com> wrote: > >>> dovecot.log shows runs of this error: >>> Apr 15 09:02:37 imap(user at domain.com): Warning: Maildir /mail/domain.com/user//.Sent: Expunged message reappeared, giving a new UID (old uid=306286, file=1429102024.M826331P1156.host,S=1678,W=1724:2,S) >>> >>> or this error:

-------- Original Message -------- Subject: Re: Dovecot 2.2.16: disappearing messages, mismatched summaries, duplicated messages, excessive full re-downloads From: Timo Sirainen <tss at iki.fi> To: David Gessel <gessel at blackrosetech.com> Date: Thu Apr 16 2015 21:31:30 GMT+0300 (Arabic Standard Time) > On 16 Apr 2015, at 04:45, David Gessel <gessel at blackrosetech.com>

hi, i have raid1 on zfs with 2 device on pool first device died and boot from second not working... i try to get http://mfsbsd.vx.sk/ flash and load from it with zpool import http://puu.sh/2402E when i load zfs.ko and opensolaris.ko i see this message: Solaris: WARNING: Can''t open objset for zroot/var/crash Solaris: WARNING: Can''t open objset for zroot/var/crash zpool status:

This doesn't look related. -James On 7/17/20 2:30 PM, Kirill A. Shutemov wrote: > On Fri, Jul 17, 2020 at 11:57:57AM -0700, James Jones wrote: >> Accept the DRM_FORMAT_MOD_NVIDIA_16BX2_BLOCK() >> family of modifiers to handle broken userspace >> Xorg modesetting and Mesa drivers. >> >> Tested with Xorg 1.20 modesetting driver, >> weston at

Hi Folks.. I have a system that was inadvertently left unmirrored for root. We were able to add a mirror disk, resilver, and fix the corrupted files (nothing very interesting was corrupt, whew), but zpool status -v still shows errors.. Will this self correct when we replace the degraded disk and resilver? Or is there something else that I''m not finding that I need to do to clean up?