Read Error At Byte 0
do not get a noticication. Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] We have vzdump of a CT which fails. In the email report of the backup [ top part] and on the PVE web page, there is no indication of a failure . Here is the top part of the 24987 lines of the log : Mar 18 22:36:18 INFO: Starting Backup of VM 102 (openvz) Mar 18 22:36:18 INFO: CTID 102 exist mounted running Mar 18 22:36:18 INFO: status = running Mar 18 22:36:18 INFO: backup mode: snapshot Mar 18 22:36:18 INFO: ionice priority: 7 Mar 18 22:36:18 INFO: creating lvm snapshot of /dev/mapper/pve-data ('/dev/pve/vzsnap-fbc241-0') Mar 18 22:36:18 INFO: Logical volume "vzsnap-fbc241-0" created Mar 18 22:36:20 INFO: creating archive '/data/pve-storage/dump/vzdump-openvz-102-2012_03_18-22_36_18.tar.lzo' Mar 18 22:44:43 INFO: tar: ./var/lib/bluecherry/recordings/2012/03/17/000010/04-58-24.mkv: Warning: Read error at byte 0, while reading 6656 bytes: Input/output error Mar 18 22:44:43 INFO: tar: ./var/lib/bluecherry/recordings/2012/03/17/000010/20-21-01.mkv: Warning: Read error at byte 0, while reading 7680 bytes: Input/output error Mar 18 22:44:43 INFO: tar: ./var/lib/bluecherry/recordings/2012/03/17/000010/17-02-09.mkv: Warning: Read error at byte 0, while reading 3584 bytes: Input/output error Mar 18 22:44:44 INFO: tar: ./var/lib/bluecherry/recordings/2012/03/17/000010/12-01-22.mkv: Warning: Read error at byte 0, while reading 3072 bytes: Input/output error Mar 18 22:44:44 INFO: tar: ./var/lib/bluecherry/recordings/2012/03/17/000010/16-42-34.mkv: Warning: Read error at byte 0, while reading 10240 bytes: Input/output error .... Mar 18 22:47:50 INFO: tar: ./usr/include/lct/font.h: Warning: Read error at byte 0, while reading 2311 bytes: Input/output error Mar 18 22:47:50 INFO: tar: ./usr/include/lct/latin8.syms.h: Warning: Read error at byte 0, while reading 1699 bytes: Input/output error Ma
Sign in Pricing Blog Support Search GitHub This repository Watch 352 Star 4,797 Fork 628 dnschneid/crouton Code Issues 428 Pull requests 12 Projects 0 Wiki Pulse Graphs New issue Cannot create backup - error with tar and trusty/etc/init/dbus.conf #1897 Open compumetrika opened this Issue Jun 27, 2015 · 7 comments Labels None yet Milestone No milestone Assignees No one assigned 4 participants compumetrika commented Jun 27, 2015 I'm running trusty under crouton on an Acer c720-3404. I've been http://pve.proxmox.com/pipermail/pve-user/2012-March/003492.html successfully backing up to a thumb drive in the past using a command from the readme (plus file location): sudo edit-chroot -b -f /media/removable/USB\ Drive/ trusty However this recently stopped working. There appears to be a missing file or something similar which throws an error under tar (see below). I've searched through both open and closer issues and haven't https://github.com/dnschneid/crouton/issues/1897 seen something which looks applicable (but of course may have missed something -- if there is something applicable I'm happily corrected...) I've confirmed that the file system is correct (have tried this with ext4 and ntfs) and that the thumbdrive is writeable for the OS. Here is the current error I am getting: chronos@localhost ~ $ sudo edit-chroot -b -f '/media/removable/USB Drive/trusty-20150627-1530.bz' trusty Unmounting /mnt/stateful_partition/crouton/chroots/trusty... tar: trusty/etc/init/dbus.conf: Read error at byte 0, while reading 489 bytes: Input/output error20150627-1530.bz... tar: trusty/etc/default/dbus: Read error at byte 0, while reading 297 bytes: Input/output error tar: trusty/home/npalmer/.cache/keyring-eqBjZV/control: socket ignored tar: trusty/home/npalmer/.cache/keyring-8YoqWk/control: socket ignored tar: trusty/home/npalmer/.config/chromium/Default/Cookies: File shrank by 1121280 bytes; padding with zeros tar: Exiting with failure status due to previous errors Unable to backup /mnt/stateful_partition/crouton/chroots/trusty. Deleting partial archive. I get this error regardless of the file system I use on the thumb drive. The drive itself is SanDisk Ultra USB 3.0 128GB, and there is nothing else on the drive -- I've formatted it to whichever filesystem I wanted to try out (ntfs and ext4 and eve
12:52:07 +0100 User-agent: KMail/4.11.5 (Linux/3.13-1-amd64; KDE/4.11.5; x86_64; ; ) On Tuesday 18 March 2014 20:05:07 Daniel Kahn Gillmor wrote: > On 03/18/2014 05:31 PM, Tim Rühsen https://lists.gnu.org/archive/html/bug-wget/2014-03/msg00109.html wrote: > > $ wget -d --ca-certificate=ca-rsa-cert.pem > > --private-key=ca-rsa-key-plain.pem https://example.com:8443 > > 2014-03-18 21:48:04 (1.88 GB/s) - Read error at byte 5116 (The TLS > > connection was non-properly terminated.).Retrying. > > > > There seems to be a problem in Wget 1.15 (on Debian SID)... > > hm, i'll try to take a look at this. I read error just took a look at it and it is not a bug, but might need some discussion. The server does not send a Content-Length header, so the number of expected bytes is unknown. Wget expects the server to properly close the connection to expect the transfer being ok. In our case, the connection shutdown by the server generates an read error at error at the Wget side. (I guess this is a difference between SSL and plain TCP connections.) Wget assumes the transfer being incomplete and tries it again and again. Not really a bug, but also not the result a user would expect... Saying "the server is buggy" doesn't help either. Here is a debug output. $ ../src/wget -d --ca-certificate=ca-rsa-cert.pem --private-key=ca-rsa-key- plain.pem https://example.com:8443 Setting --ca-certificate (cacertificate) to ca-rsa-cert.pem Setting --private-key (privatekey) to ca-rsa-key-plain.pem DEBUG output created by Wget 1.15.11-8a34-dirty on linux-gnu. URI encoding = ‘UTF-8’ --2014-03-19 12:25:28-- https://example.com:8443/ Certificates loaded: 162 Resolving example.com (example.com)... 127.0.0.1 Caching example.com => 127.0.0.1 Connecting to example.com (example.com)|127.0.0.1|:8443... connected. Created socket 4. Releasing 0x0000000001724de0 (new refcount 1). ---request begin--- GET / HTTP/1.1 Accept: */* Host: example.com:8443 Connection: Keep-Alive ---request end--- HTTP request sent, awaiting response... ---response begin--- HTTP/1.0 200 ok Content-type: text/html ---response end--- 200 ok Registered socket 4 for persistent reuse. Length: unspecified [text/html] Saving to: ‘index.html.3’ [ <=> ] 5,116 --.-K/s in 0s Disabling further reuse of socket 4. A len=5116 contlen=-1 res=-1 B len=5116 contlen=-1 res=-1 2014-03-19 12:25:2