LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: Gene Heskett <gene.heskett@gmail.com>
Cc: linux-kernel@vger.kernel.org,
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 17:06:57 -0500 [thread overview]
Message-ID: <1174342017.3512.58.camel@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <200703191747.48826.gene.heskett@gmail.com>
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
next prev parent reply other threads:[~2007-03-19 22:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-19 0:34 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 [this message]
2007-03-19 23:29 ` Gene Heskett
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=1174342017.3512.58.camel@mulgrave.il.steeleye.com \
--to=james.bottomley@steeleye.com \
--cc=akpm@linux-foundation.org \
--cc=ast@domdv.de \
--cc=gene.heskett@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--subject='Re: 2.6.20.3: kernel BUG at mm/slab.c:597 try#2' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).