Sorry, but it would be much more helpful if you could be extremely
precise with your statements; maybe it's an language problem, but some
of your statements, especially your parenthetical comments, are very
hard for me to parse as valid english and then make semantic sense out
of them.  For example: "(same hardware, but only one server has the
problem, other hardware same problem)" from your first message.   This
is what caused me to believe only one server was having the problems.
I'm also not sure what this parenthetical comment at the end of your
first message means: "(Dapper will find errors until the end of days)".
Now that I look at this carefully, I *think* it means that knoppix can
fix the problems, but when you run e2fsck while booted on Dapper, e2fsck
is reporting a lot of errors, and repeated runs of e2fsck causes it
still report errors.

No one else is reporting problems like this, which causes me to be
suspicious that there is at least something unique in your
configuration.  Are the systems running the whole time; do you have any
problems with unclean shutdowns due to power outages?   Given that you
are reporting that you are seeing this pattern on a variety of SCSI
controllers as well as LVM as well as MD devices, I grant that it's
unlikely to be caused by hardware defects.

*If* the Dapper will find errors until the end of days means that you
can repeatedly run e2fsck and find problems, and but when you boot
Knoppix, the problem goes away, the only question is whether it is a
Dapper kernel bug or an e2fsck bug.   Again, I haven't heard anyone
report problems like this ever, and the sort of problems you are
describing don't sound like the sort of thing which I've fixed recently
in e2fsprogs.   And these days, almost *everyone* is using ext3 over LVM
w/o any problems.  Are you willing to try downloading and compiling a
modern e2fsprogs?   If you like you can try downloading Debian's e2fsck-
static binary from Lenny (http://packages.debian.org/lenny/e2fsck-
static).  That should work on any system since it is statically linked.
Just download the right package for your platform.   I'm pretty sure
though that you will find that this is a Dapper kernel problem...

-- 
Dapper lvm over software raid kills ext3
https://bugs.launchpad.net/bugs/247318
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to