* data logging 2.6 - possible bug
@ 2004-02-10 21:06 Christian Mayrhuber
2004-02-10 21:33 ` Dieter Nützel
0 siblings, 1 reply; 4+ messages in thread
From: Christian Mayrhuber @ 2004-02-10 21:06 UTC (permalink / raw)
To: reiserfs-list
Hi,
after a week of uptime on my daily use workstation
with kernel 2.6.2-rc2 + 2.6.1 exp data logging patches
I did a reboot and reiserfsck of the raid1 device /dev/md1.
Reiserfsck found 5 corruptions all of the style:
/.tmp-kallsyms2.ovpf-10680: The file [420253 452289] has the
wrong block count in the StatData (256), should be (320).
Only .tmp-kallsyms[1|2].ovpf files in / and /usr/src/2.6.2-rc2
were affected, no "production" files.
These files are not listed by ls -f, neither before --fix-fixable
nor after it. --fix-fixable was able to correct these corruptions.
--
lg, Chris
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: data logging 2.6 - possible bug
2004-02-10 21:06 data logging 2.6 - possible bug Christian Mayrhuber
@ 2004-02-10 21:33 ` Dieter Nützel
2004-02-11 10:10 ` Christian Mayrhuber
0 siblings, 1 reply; 4+ messages in thread
From: Dieter Nützel @ 2004-02-10 21:33 UTC (permalink / raw)
To: reiserfs-list; +Cc: Christian Mayrhuber
Am Dienstag, 10. Februar 2004 22:06 schrieb Christian Mayrhuber:
> Hi,
>
> after a week of uptime on my daily use workstation
> with kernel 2.6.2-rc2 + 2.6.1 exp data logging patches
> I did a reboot and reiserfsck of the raid1 device /dev/md1.
>
> Reiserfsck found 5 corruptions all of the style:
> /.tmp-kallsyms2.ovpf-10680: The file [420253 452289] has the
> wrong block count in the StatData (256), should be (320).
>
> Only .tmp-kallsyms[1|2].ovpf files in / and /usr/src/2.6.2-rc2
> were affected, no "production" files.
> These files are not listed by ls -f, neither before --fix-fixable
> nor after it. --fix-fixable was able to correct these corruptions.
Have tried to check your disks?
No problems, here.
--
Dieter Nützel
@home: <Dieter.Nuetzel () hamburg ! de>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: data logging 2.6 - possible bug
2004-02-10 21:33 ` Dieter Nützel
@ 2004-02-11 10:10 ` Christian Mayrhuber
2004-02-11 13:38 ` Chris Mason
0 siblings, 1 reply; 4+ messages in thread
From: Christian Mayrhuber @ 2004-02-11 10:10 UTC (permalink / raw)
To: reiserfs-list
Dieter Nützel wrote:
> Have tried to check your disks?
I reiserfscked the disks before the use of 2.6 + data logging
and they were clean. (a week ago)
Yesterday:
1. The fs and md devices had a clean shutdown.
2. --check
3. --fix-fixable
4. Ran badblocks read only test. => no bad blocks found
>
> No problems, here.
Great for you ;-)
I had 2.4 + data logging running for about half a year with
zero problems, too.
--
lg, Chris
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: data logging 2.6 - possible bug
2004-02-11 10:10 ` Christian Mayrhuber
@ 2004-02-11 13:38 ` Chris Mason
0 siblings, 0 replies; 4+ messages in thread
From: Chris Mason @ 2004-02-11 13:38 UTC (permalink / raw)
To: Christian Mayrhuber; +Cc: reiserfs-list
On Wed, 2004-02-11 at 05:10, Christian Mayrhuber wrote:
> Dieter Nützel wrote:
>
> > Have tried to check your disks?
> I reiserfscked the disks before the use of 2.6 + data logging
> and they were clean. (a week ago)
It does look like a 2.6 data logging bug, I must not be logging the stat
data after filling holes or something. I'll take a look, thanks.
-chris
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2004-02-11 13:38 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-02-10 21:06 data logging 2.6 - possible bug Christian Mayrhuber
2004-02-10 21:33 ` Dieter Nützel
2004-02-11 10:10 ` Christian Mayrhuber
2004-02-11 13:38 ` Chris Mason
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.