On Wed, 2012-11-07 at 16:50 +0400, hr...@infotech.am wrote:
> The problem solved in Debian Wheezy for kernel
> linux-image-3.2.0-4-amd64 3.2.32-1 amd64 Linux 3.2 for 64-bit PCs
Are you sure? This doesn't include any of the changes that were
expected to fix this bug, as you did not report that you had tested
them. It does have other bug fixes for ext4, though.
Ben.
-- Ben Hutchings
The program is absolutely right; therefore, the computer must be wrong.
Yeah, Bug is not completely disappeared,
my test was done in new formatted partition, which was almost free, and no
any error was appeared for image 160Gb.
But when I tried to format 160Gb image file on the other machine, where
the 2Tb partition is full more than 80% and fragmented, I could reproduce
the bug.
I'm not sure that these facts are directly connected to bug reproduction,
but doing few test on different machines, I'm able to reproduce the error.
>> This doesn't include any of the changes that were
>> expected to fix this bug, as you did not report that you had tested them.
Yeah, I haven't chance to compile and test the new kernel due to lack of
time:(
Hrayr
> On Wed, 2012-11-07 at 16:50 +0400, hr...@infotech.am wrote:
>> The problem solved in Debian Wheezy for kernel
>> linux-image-3.2.0-4-amd64 3.2.32-1 amd64 Linux 3.2 for 64-bit PCs
> Are you sure? This doesn't include any of the changes that were
> expected to fix this bug, as you did not report that you had tested
> them. It does have other bug fixes for ext4, though.
> Ben.
> --
> Ben Hutchings
> The program is absolutely right; therefore, the computer must be wrong.
-- To UNSUBSCRIBE, email to debian-bugs-dist-REQU...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
On Tue, 2012-11-13 at 02:33 +0400, hr...@infotech.am wrote:
> Yeah, Bug is not completely disappeared,
> my test was done in new formatted partition, which was almost free, and no
> any error was appeared for image 160Gb.
> But when I tried to format 160Gb image file on the other machine, where
> the 2Tb partition is full more than 80% and fragmented, I could reproduce
> the bug.
> I'm not sure that these facts are directly connected to bug reproduction,
> but doing few test on different machines, I'm able to reproduce the error.
> >> This doesn't include any of the changes that were
> >> expected to fix this bug, as you did not report that you had tested them.
> Yeah, I haven't chance to compile and test the new kernel due to lack of
> time:(
I tested Ted's patches on top of 3.2.37 (one of them needed a context
change as we already got commit
dee1f973ca341c266229faa5a1a5bb268bed3531) and they seem to fix the
problem: I see no errors from mke2fs, or the kernel, or subsequent
'fsck.ext4 -f' of the inner and outer filesystems.
I have therefore committed these for the next Debian release and will
also queue them up for 3.2.y.
Ben.
-- Ben Hutchings
Experience is what causes a person to make new mistakes instead of old ones.
