On Sat, 5 Apr 1997 22:57:45 -0500 (EST), Dave Wreski
<tel1dvw@is.ups.com> said:
> I don't think we have someone who is keeping track of the reports
> that (hopefully) will come in regarding working and non working
> configuration with regard to ext2 corruption. Do you have a web
> page to keep these on, and know the people that should be contacted
> for them to reference when doing testing/development (Ted Ts'o and
> Remy Card?) ?
I am paying very close attention to ext2 corruption reports, and have
been investigating a number on and off for a while. I've been doing
so since well before 1.0. However, we simply haven't seen any real
problems recently which weren't attributable, with _fairly_ high
certainty, to device driver or hardware problems. That's the trouble
with filesystems --- they depend on a whole stack of other components,
but if anything in that stack breaks it's often the filesystem itself
which gets blamed.
Having said that, there _does_ look like a definite problem in the VFS
inode.c as described in the latest thread, but even that shouldn't
affect filesystems in isolation --- it would only have any effect if
you were using non-filesystem inodes such as pipes and sockets in
addition to the filesystem itself.
> Anyway, my P180 doesn't have this problem. I modified your one-hellova
> wicked 'script' to run infinitely. I started it last night, and stopped
> it after 10hours
Excellent.
> Here is a known working configuration.
Thanks --- noted.
> Hope thats adequate. Also, I've never really been involved in
> bug-reports/bug-tracing. I would assume this takes precendence over
> further development until this is resolved?
You can't stall development just because some people are reporting
problems which are (a) not reproducible on other systems and (b) not
definitely identified as being the responsibility of any one component
in the system anyway. However, there _are_ people out here who pay
close attention to filesystem bug reports, so you are not being
ignored...
Cheers,
Stephen.