public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ondrej Zary <linux@rainbow-software.org>
To: Konstantin Khlebnikov <khlebnikov@openvz.org>
Cc: Hugh Dickins <hughd@google.com>,
	Kernel development list <linux-kernel@vger.kernel.org>
Subject: [bisected] NFS corruption with 3.4
Date: Tue, 5 Jun 2012 11:16:17 +0200	[thread overview]
Message-ID: <201206051116.17711.linux@rainbow-software.org> (raw)

Hello,
I use NFS for deploying HDD images on new machines. My machine has 2nd network 
card just for this, running DHCPD, TFTPD and kernel NFS server. The target 
machine is set to boot from LAN and boots SystemRescueCD from my machine with 
an autorun script that launches Partimage and deploys the HDD image (400 to 
900 MB compressed).

It worked fine for years, until now. With kernel 3.4, everyting 
works only for the first time after boot (and not always). Next time (next 
machine), partimage aborts almost immediately as it's probably unable to 
decompress the image file. md5sum is different on my machine vs. on the 
target (through NFS). Also SystemRescueCD boot aborts with md5 error 
sometimes. Everything works fine after rebooting back to 3.3.

Bisection found this:

0fc9d1040313047edf6a39fd4d7c7defdca97c62 is the first bad commit
commit 0fc9d1040313047edf6a39fd4d7c7defdca97c62
Author: Konstantin Khlebnikov <khlebnikov@openvz.org>
Date:   Wed Mar 28 14:42:54 2012 -0700

    radix-tree: use iterators in find_get_pages* functions

Reverting this commit in 3.4 fixes the problem.


-- 
Ondrej Zary

             reply	other threads:[~2012-06-05  9:16 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-05  9:16 Ondrej Zary [this message]
2012-06-05 12:45 ` [bisected] NFS corruption with 3.4 Dave Jones
2012-06-05 13:45   ` Holger Hoffstaette
2012-06-05 14:11   ` Ondrej Zary
2012-06-05 13:32 ` [bisected commit 0fc9d10] NFS-server " Konstantin Khlebnikov
2012-06-05 14:20   ` Ondrej Zary
2012-06-05 14:52     ` Konstantin Khlebnikov
2012-06-05 15:07       ` OGAWA Hirofumi
2012-06-05 15:14         ` Konstantin Khlebnikov
2012-06-05 15:59           ` Konstantin Khlebnikov
2012-06-05 16:18             ` OGAWA Hirofumi
2012-06-05 16:39               ` Konstantin Khlebnikov
2012-06-05 22:30                 ` Hans de Bruin
2012-06-06 10:54                   ` Konstantin Khlebnikov
2012-06-05 17:03             ` Toralf Förster
2012-06-05 17:17               ` Konstantin Khlebnikov
2012-06-06  8:55             ` Ondrej Zary
2012-06-05 14:21   ` Toralf Förster

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201206051116.17711.linux@rainbow-software.org \
    --to=linux@rainbow-software.org \
    --cc=hughd@google.com \
    --cc=khlebnikov@openvz.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox