From: "Piszcz, Justin Michael" <justin.piszcz@mitretek.org>
To: "Kristofer T. Karas" <ktk@enterprise.bidmc.harvard.edu>,
"Linus Torvalds" <torvalds@osdl.org>
Cc: "Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: RE: FS Corruption [Re: Linux 2.6.10-rc3]
Date: Mon, 6 Dec 2004 12:29:17 -0500 [thread overview]
Message-ID: <2E314DE03538984BA5634F12115B3A4E01BC414D@email1.mitretek.org> (raw)
I also got FS corruption with XFS under 2.6.10-rc2.
Booting back to 2.6.9 did not fix the problem, had to re-install.
-----Original Message-----
From: linux-kernel-owner@vger.kernel.org
[mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of Kristofer T.
Karas
Sent: Monday, December 06, 2004 12:23 PM
To: Linus Torvalds
Cc: Kernel Mailing List
Subject: FS Corruption [Re: Linux 2.6.10-rc3]
Linus Torvalds wrote:
>Ok, it's out there in all the normal places, and here's the shortlog
for
>the thing.
>
Hi Linus - I'm seeing filesystem corruption (on ext3 anyway) with -rc3;
there is no such corruption on -rc2. It would be better if somebody
with a clue reported this; but since I haven't seen anything, I thought
I'd hollar before somebody loses work as a result. (Everybody does real
work on -rc kernels, don't they? :-)
I untarred a kernel tarball into a directory, renamed it "foo", reboot
(to clear disk cache), and then did this:
pinhead:/usr/src/kernels# rm -r foo &
[1] 3268
pinhead:/usr/src/kernels# tar xzf linux-2.6.9.tar.gz
rm: cannot remove `foo/include/asm-ppc/linkage.h': No such file or
directory
rm: cannot remove `foo/include/asm-x86_64/rtc.h': No such file or
directory
rm: cannot remove `foo/include/asm-m68knommu/mcftimer.h': No such file
or directory
rm: cannot remove `foo/include/asm-m68k/linkage.h': No such file or
directory
rm: cannot remove `foo/include/asm-sparc64/rwsem.h': No such file or
directory
rm: cannot remove `foo/include/asm-sparc/psr.h': No such file or
directory
[1]+ Exit 1 rm -r foo
pinhead:/usr/src/kernels#
Running e2fsck on the next boot reports I've got a damaged filesystem.
System is a generic PC (a Dell GX110) - I810 chipset, PIII, IDE.
Untainted vanilla kernel. Other config details upon request.
Kris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2004-12-06 17:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-06 17:29 Piszcz, Justin Michael [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-07 14:07 cr7
2004-12-04 0:19 Linux 2.6.10-rc3 Linus Torvalds
2004-12-06 17:23 ` FS Corruption [Re: Linux 2.6.10-rc3] Kristofer T. Karas
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=2E314DE03538984BA5634F12115B3A4E01BC414D@email1.mitretek.org \
--to=justin.piszcz@mitretek.org \
--cc=ktk@enterprise.bidmc.harvard.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®