Serious filesystem bug?
 

Hello everyone,

I don't know how to catogorize this:
I am using Debian/Squeeze on a laptop with an encrypted ext3 filesystem.
(Encryption done through the debian-installer).
I have a h2-database running. It got corrupted many times. I had to "
touch /forcefsck" and after a reboot and the forced filesystemcheck all
was again okay.
The same problem appeared with downloaded ISOs. I ran md5sum checks on
the ISO and they were wrong. After forcing a fsck at boottime the md5sum
of the ISOs were correct!


Does anyone got similiar problems?


Greetings!

--
Slobodan


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: 4D1D69F6.3080609@aleksic.de">http://lists.debian.org/4D1D69F6.3080609@aleksic.de

Serious filesystem bug?
 

Slobodan Aleksić schreef:

Hello everyone,

I don't know how to catogorize this:
I am using Debian/Squeeze on a laptop with an encrypted ext3 filesystem.
(Encryption done through the debian-installer).
I have a h2-database running. It got corrupted many times. I had to "
touch /forcefsck" and after a reboot and the forced filesystemcheck all
was again okay.
The same problem appeared with downloaded ISOs. I ran md5sum checks on
the ISO and they were wrong. After forcing a fsck at boottime the md5sum
of the ISOs were correct!
This is not the unique, might have been unnoticed, filesystem usage that
you'd expect for new bugs to occur. So my guess is that there might be a
problem with your hardware. What does

smartctl -H /dev/yourdrive
tell you? Also try
smartctl --test=short /dev/yourdrive
and then
smartctl --test=long /dev/yourdrive
Hopefully this uncovers something useful.

Sjoerd

Serious filesystem bug?
 

I first guessed also a hardwarefailure, all smarttests passed without
errors, the only thing I found was that the partitiontable is showing me
(fdisk -l) :

"Partition 1 does not end on cylinder boundary."
My first partition is the boot partition.

Very curious for now, because I am running several instances of
Debian/Squeeze as servers and I am not getting such errors or problems
there.


I believe if no one else got these problems that this is due to my
hardware in any kind...


Thanks for your assistance!



On 12/31/2010 10:01 AM, Sjoerd Hardeman wrote:

Slobodan Aleksić schreef:

Hello everyone,

I don't know how to catogorize this:
I am using Debian/Squeeze on a laptop with an encrypted ext3
filesystem. (Encryption done through the debian-installer).
I have a h2-database running. It got corrupted many times. I had to "
touch /forcefsck" and after a reboot and the forced filesystemcheck
all was again okay.
The same problem appeared with downloaded ISOs. I ran md5sum checks on
the ISO and they were wrong. After forcing a fsck at boottime the
md5sum of the ISOs were correct!

This is not the unique, might have been unnoticed, filesystem usage that
you'd expect for new bugs to occur. So my guess is that there might be a
problem with your hardware. What does
smartctl -H /dev/yourdrive
tell you? Also try
smartctl --test=short /dev/yourdrive
and then
smartctl --test=long /dev/yourdrive
Hopefully this uncovers something useful.

Sjoerd





--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4D1F2BB5.9080101@aleksic.de">http://lists.debian.org/4D1F2BB5.9080101@aleksic.de

Serious filesystem bug?
 

Op 01-01-11 14:27, Slobodan Aleksić schreef:
> I first guessed also a hardwarefailure, all smarttests passed without
> errors, the only thing I found was that the partitiontable is showing me
> (fdisk -l) :
> "Partition 1 does not end on cylinder boundary."
> My first partition is the boot partition.
It might of course be useful to use a tool like parted to make sure your
partition does end on the cylinder boundary. I have no clue if this can
be the problem, but it would be interesting to know.

Sjoerd

Serious filesystem bug?
 

Slobodan Aleksić schreef:

Hello everyone,

I don't know how to catogorize this:
I am using Debian/Squeeze on a laptop with an encrypted ext3
filesystem. (Encryption done through the debian-installer).
I have a h2-database running. It got corrupted many times. I had to "
touch /forcefsck" and after a reboot and the forced filesystemcheck
all was again okay.
The same problem appeared with downloaded ISOs. I ran md5sum checks on
the ISO and they were wrong. After forcing a fsck at boottime the
md5sum of the ISOs were correct!


Does anyone got similiar problems?


Greetings!

--
Slobodan



a hardware problem? corrupted disk?

s.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: 4D203778.7000607@home.nl">http://lists.debian.org/4D203778.7000607@home.nl