[Bugme-new] [Bug 33112] New: Possible file corruption (RAID10+LVM+ext4) with chromium and kernel build
bugzilla-daemon at bugzilla.kernel.org
bugzilla-daemon at bugzilla.kernel.org
Tue Apr 12 00:56:08 PDT 2011
https://bugzilla.kernel.org/show_bug.cgi?id=33112
Summary: Possible file corruption (RAID10+LVM+ext4) with
chromium and kernel build
Product: IO/Storage
Version: 2.5
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Other
AssignedTo: io_other at kernel-bugs.osdl.org
ReportedBy: cate at cateee.net
Regression: Yes
[Set to "Component: Other", because the long block chain]
Just after solving bug #32062 I did a system update (debian unstable, new gcc
and binutils + gold [but I don't think gold is enabled on default]).
Now at every kernel update I have a linker error, usually on some **/built-in.o
(something like "invalid character in 1,1"), or in some *.lds or *.dbg files
(invalid/empty file).
This is solvable with a make mrproper and a complete build.
I was thinking about some Debian chaintool problem, but earlier today I did
further check and I found that the **/built-in.o files seem to contain the
chromium history (debian chromium), which I think it is saved frequently.
BTW I use the browser a lot when building the kernels, and I often shut down
the system just after the kernel build.
So I think there is a problem on flushing the buffers to the disk.
You can see my setup (and some dmesg) in
https://bugzilla.kernel.org/show_bug.cgi?id=32062 and in
https://bugzilla.kernel.org/show_bug.cgi?id=24012 , but in short: 4 disks, with
a RAID10. I build a LVM on them, and then some ext4 fs, and usually I have a
lot of free memory.
In next days I'll try to bisect the bug, but it will be slow, especially if the
bug is not 100% reproducible. BTW: do you have some tools to detect earlier
possible disk corruptions?
ciao
cate
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
More information about the Bugme-new
mailing list