similar to: Weird checksum error with VM images

I'm trying to set up for my small school lab: Samba as PDC, 11 workstations running XP Pro, roaming profiles with folder redirection. (I finally got the workstations to join the domain by adding them by hand--so I assume something is wrong with my add machine script, but I'll address that issue later, since I have only the 11 XP boxes to deal with.) Now I'm working on getting the

Hello everyone, I came back from a long vacation the other day to a RH 7.3 system that would not boot. My situation is similar to Eddy's post "Seriously corrupt ext3 root filesystem - help?" from a couple of days ago. I can mount the drive in read-write and read-only modes. I can get into some of the directories and get certain files off of the disk. But, if I try to access a

Regarding http://twitter.com/CentOS/statuses/79336297579282432 I don't have a twitter account so I'm spamming the list since it looks on topic :) I'd like to see on the LiveCD the following: 1. latest dd_rescue 2. latest gparted 3. ntfs-3g 4. screen 5. mc How about you? -- Nux! www.nux.ro

Posting here in the hope that some one may have encountered problems with recovery from backups on LTO4 media and found a solution. Back ups on FujiFilm LTO4 media (800/1600). Archives created using tar -cf /dev/nst0. ?The tapes were fine when the archives were created (tested by extracting random sample files from them) but something went wrong in storage (no physical damage). Now a few LTO4

Hello folks, I had an ext3 filesystem mounted as the root of a Linux MOO server. Unfortunately, the filesystem was on one of the infamous DTLA-3070xx drives - and the drive decided to fail at the worst moment it possibly could, trashing the filesystem fairly well. The situation is as follows: I used dd_rescue to create an image of what is left of the filesystem, but I ended up with some 65MB

On 03/02/2017 11:57 PM, Robert Moskowitz wrote: > The following worked: > > # dd if=/dev/sdb of=cubietruck.img bs=512 count=6268927 > > 6268927+0 records in > 6268927+0 records out > 3209690624 bytes (3.2 GB, 3.0 GiB) copied, 114.435 s, 28.0 MB/s > > So bs= IS the drive blocksize. > > This is the result of trying a number of different values for bs and > count.

Fabian Cenedese <Cenedese at indel.ch> wrote: >> rsync: write failed on "/Volumes/durack1ml_bak/160405_1234/Backups.backupdb/durack1ml/2016-02-10-091749/durack1ml_hdd/Applications/Adobe Media Encoder CC 2015/Adobe Media Encoder CC 2015.app/Contents/Resources/pdfl/CMaps/ETen-B5-UCS2": Result too large (34) > Are you sure that the problem is with the corrupted source data?

https://bugzilla.samba.org/show_bug.cgi?id=1457 Summary: writefd_unbuffered failed to write Product: rsync Version: 2.6.2 Platform: x86 OS/Version: All Status: NEW Severity: critical Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: markf78@yahoo.com QAContact:

I would really appreciate some help figuring out why one of my students has "disappeared" from the user list, and what to do about it. I'm using Samba3 on Fedora; the client machines are running WinXP. The system has been up and running since the beginning of September. Today one of my 4th-graders was unable to log on; she didn't read the error message carefully, so she

On Tue, Feb 07, 2017 at 04:14:16PM +0100, Cédric Bosdonnat wrote: > Getting checksum involves the same code than verifying them. Create > a get_checksum function and use it in verify_checksum. > --- > mllib/checksums.ml | 25 ++++++++++++++++--------- > mllib/checksums.mli | 9 +++++++++ > 2 files changed, 25 insertions(+), 9 deletions(-) > > diff --git

The attached patch provides an additional check for the checksumming mode to ensure that a file that is actually written out to disk can be read back and has the same MD4 sum as the file on at the originating location. Regards, Nick. -------------- next part -------------- *** rsync-2.6.6pre1/receiver.c 2005-04-14 02:42:13.000000000 +0100 --- rsync-new/receiver.c 2005-07-26

The prescription for Boot Info Table says that checksumming begins at byte 64 of isolinux.bin. When prepcore writes isolinux.bin it begins copying bytes from the input file at the offset given by variable "start". But it begins checksumming at offset 64 of the input file. The problem exists since introduction of prepcore by release 4.00. ISO 9660 programs usually fix it when they write

H, Ady wrote: > A_ The default checksum included in the tested isolinux.bin (offset 20, > 4-bytes-long) is the "correct" one (as oppose to the current situation, > since version 4.00). That's good news. > F_ In the tested isolinux.bin file, there are two additional bytes that > I found to be changed/affected by some ISO-building tools (e.g. > mkisofs), at

On Mon, Apr 16, 2018 at 09:45:48AM -0400, Vlad Yasevich wrote: > On 04/11/2018 06:49 PM, Michael S. Tsirkin wrote: > > On Mon, Apr 02, 2018 at 09:40:02AM -0400, Vladislav Yasevich wrote: > >> To support SCTP checksum offloading, we need to add a new feature > >> to virtio_net, so we can negotiate support between the hypervisor > >> and the guest. > >>

Hi, On a Fedora 18, I try to launch a VM with QEMU-GlusterFS native integration. I have enable fedora-virt-preview repo, and gluster-alpha3 repo. Below the list of installed package : glusterfs-3.4.0-0.3.alpha3.fc18.x86_64 glusterfs-devel-3.4.0-0.3.alpha3.fc18.x86_64 glusterfs-fuse-3.4.0-0.3.alpha3.fc18.x86_64 glusterfs-server-3.4.0-0.3.alpha3.fc18.x86_64

On Mon, Apr 02, 2018 at 09:40:02AM -0400, Vladislav Yasevich wrote: > To support SCTP checksum offloading, we need to add a new feature > to virtio_net, so we can negotiate support between the hypervisor > and the guest. > > The signalling to the guest that an alternate checksum needs to > be used is done via a new flag in the virtio_net_hdr. If the > flag is set, the host

On Mon, Apr 02, 2018 at 09:40:02AM -0400, Vladislav Yasevich wrote: > To support SCTP checksum offloading, we need to add a new feature > to virtio_net, so we can negotiate support between the hypervisor > and the guest. > > The signalling to the guest that an alternate checksum needs to > be used is done via a new flag in the virtio_net_hdr. If the > flag is set, the host

Hi, i think i found a suspect in lzo/prepcore.c and it would indeed be a wrong range of checksumming (speculative congratulations to Ady). Looking at http://repo.or.cz/syslinux.git/blob/0d82b71304d596d80f3c4520f9dcf90048ca50b7:/lzo/prepcore.c it seems that this change in line 374 could yield correct checksums: unsigned int ptr; - for (ptr = 64; ptr < offset; ptr += 4) +

Another checksum offload problem was reported on xen-users, when using a domU as a firewall: http://lists.xensource.com/archives/html/xen-users/2006-04/msg01150.html It also fails without VLANs. The path from dom0->domU with ip_summed==CHECKSUM_HW/proto_csum_blank==1 is broken. - skb_checksum_setup() assumes that a checksum will definitely be calculated in dev_queue_xmit(), but the