From: Gene Heskett <gene.heskett@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: James Bottomley <James.Bottomley@steeleye.com>,
Mike Christie <michaelc@cs.wisc.edu>,
Andreas Steinmetz <ast@domdv.de>,
linux-scsi@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: 2.6.20.3: kernel BUG at mm/slab.c:597 try#2
Date: Mon, 19 Mar 2007 19:29:41 -0400 [thread overview]
Message-ID: <200703191929.41268.gene.heskett@gmail.com> (raw)
In-Reply-To: <1174342017.3512.58.camel@mulgrave.il.steeleye.com>
On Monday 19 March 2007, James Bottomley wrote:
>On Mon, 2007-03-19 at 17:47 -0400, Gene Heskett wrote:
>> James, could this also be the cause of a tar based backup going crazy
>> and thinking all data is new under any 2.6.21-rc* kernel I've tested
>> so far with amanda, which in my case uses tar? I've tried the fedora
>> patched tar-1.15-1, and one I hand built right after 1.15-1 came out
>> over a year ago, and they both do it, but only when booted to a
>> 2.6.21-rc* kernel.
>>
>> This obviously will be a show-stopper, either for amanda (and by
>> inference, any app that uses tar), or for the migration of an amanda
>> users machinery to a 2.6.21 kernel.
>
>Er, I don't think so .. that sounds like mtime miscompare, which is
>either a problem with the filesystem or a problem with the way mtime is
>stored in the tar archive.
>
>James
Well, since the times reported by ls -l --full-time are sane
[root@coyote pix]# ls -l --full-time
total 924784
-rw-r--r-- 1 root root 985324 2002-06-09 18:14:54.000000000 -0400
0203.jpg
[... the rest of a 100k listing, booted to 2.6.20.3-rdsl-0.31]
And:
[root@coyote pix]# ls -l --full-time
total 924784
-rw-r--r-- 1 root root 985324 2002-06-09 18:14:54.000000000 -0400
0203.jpg
booted to 2.6.21-rc4
allthough the fractional second is a string of .000000000, even when
booted to a tar-unfriendly kernel, then it would tend to point at tar,
but two differently built versions of tar have been confirmed as
miss-behaving in the presence of a kernel in the 2.6.21 series so far,
all of them.
I'm going to reboot twice more tonight, once to verify that the output of
an ls -l --full-time is as I said above, I'll save this and do that again
and clip it in after a reboot to 2.6.21-rc4, and once to 2.6.20.4-rc1 to
see if by chance one of those patches is the guilty party. I'll leave
the latter running tonight for the amanda run & see what falls out.
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Try to relax and enjoy the crisis.
-- Ashleigh Brilliant
prev parent reply other threads:[~2007-03-19 23:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-19 0:34 2.6.20.3: kernel BUG at mm/slab.c:597 try#2 Andreas Steinmetz
2007-03-19 6:00 ` Andrew Morton
2007-03-19 8:00 ` Pekka Enberg
2007-03-19 8:32 ` Pekka Enberg
2007-03-19 8:35 ` Pekka Enberg
2007-03-19 17:49 ` Mike Christie
2007-03-19 18:29 ` James Bottomley
2007-03-19 19:06 ` Mike Christie
2007-03-19 21:12 ` Mike Christie
2007-03-19 23:25 ` Andreas Steinmetz
2007-03-19 23:40 ` Andrew Morton
2007-03-19 23:46 ` Andreas Steinmetz
2007-03-19 23:25 ` Andreas Steinmetz
2007-03-19 21:47 ` Gene Heskett
2007-03-19 22:06 ` James Bottomley
2007-03-19 23:29 ` Gene Heskett [this message]
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=200703191929.41268.gene.heskett@gmail.com \
--to=gene.heskett@gmail.com \
--cc=James.Bottomley@steeleye.com \
--cc=akpm@linux-foundation.org \
--cc=ast@domdv.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
/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