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

>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

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

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

There are times when a large file is copied up to 99% and then deleted after having received the error. Other times when the error occurs earlier and only a part of it is copied. Does it make sense to calculate the checksum if in both cases in output I don't have the same information that there is in input ? Because in the first case it is totally deleted and in the second case I have only a

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

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

-> 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

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:

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?

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

-------- 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>

I had a sparc64 (Netra X1) running a stable/9 from late March 2013. Actually, the kernel may've been a bit newer than that as I was working with folks to diagnose and repair some Netra-X1 specific issues. But, ZFS worked fine. I have two pools, zroot as a RAID1 (using equally sized partitions at the front of two large disks), and a zdata that is a large pool of the remaining space of both

I have samba 4.3 running on FreeBSD 10.2 on ZFS and I am unable to create new GPOs, getting "invalid Parameter" response.Log files indicate ACL issues. Domain was provisioned with --use-ntvfs option.Filesystem is mounted with this options:zroot/ROOT/default on / (zfs, local, noatime, nfsv4acls) acl options on zfs are this:zroot/ROOT/default aclmode passthrough inherited from

Followed the instructions here: http://www.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html The upgrade borked. Error message: Can't find 'kernel' When I checked with ls /boot/kernel/, the directory does exist. :-( Since the system has encrypted root partion with ZFSonROOT, I tried to follow instructions at https://forums.freebsd.org/viewtopic.php?&t=8958 to boot

Edgar, thanks for the help! -------- Original Message -------- Subject: Re: Dovecot 2.2.16: disappearing messages, mismatched summaries, duplicated messages, excessive full re-downloads From: Edgar Pettijohn III <edgar at pettijohn-web.com> To: David Gessel <gessel at blackrosetech.com> Date: Sat Apr 18 2015 16:30:07 GMT+0300 (Arabic Standard Time) > > On Apr 18, 2015, at 8:00

Hi, I installed FreeBSD/amd64 9.1-RELEASE yesterday. I chose to do a manual installation due to the use of ZFS. I checked out stable/9 and recompiled both world and GENERIC kernel. Said kernel and world was installed without any problems. System is still up & running, with uname -a revealing r243825. I then decided to upgrade the root pool to feature flags, SPA version 5000, and was not so

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