[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAH3VSLwhe7ZHfuc1+RatWvrvAOAS3HakYoRr5+PNnvvrue9BmA@mail.gmail.com>
Date: Mon, 26 Nov 2012 09:48:10 +0100
From: Roger Niva <rogerniva@...il.com>
To: Andreas Dilger <adilger@...ger.ca>
Cc: "linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>
Subject: Re: Ext4 file corruption using cp
On Sun, Nov 11, 2012 at 6:50 PM, Andreas Dilger <adilger@...ger.ca> wrote:
> On 2012-11-11, at 4:37, Roger Niva <rogerniva@...il.com> wrote:
>>
>> We are trying to pin down a file corruption issue we have on 5
>> productionservers and would like some suggestions about how to proceed
>> to find the culprit. It may or may not be ext4-related, but as that is
>> the only clue we have so far, we're trying here first.
>>
>> The productionservers are running Slackware 13.37 with a selfcompiled
>> kernel (no patches or external modules).
>> We have a script running daily that copies files from one folder to
>> another using cp.
>
> there was a bug in ext4 FIEMAP ioctl code in the past that interacted badly with fileutils for copying files that were just written and still in cache. That was around 2.6.26 or so.
>
> You should probably try a new version of fileutils to see if that solves the problem. Alternately, if you run "sync" before "cp" this should also avoid the problem.
>
> Cheers, Andreas
Hi.
We have now been running a newer coreutils (/bin/cp) for about a week
without seeing this pop up again, so we're reasonably sure it fixed
the issue for us.
Thanks a bunch!
--
Vennlig hilsen,
Roger Niva
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists