https://bugs.debian.org/cgi-bin/bugrepo ... bug=785672
Just a heads up guys. Note, for those who need to be near the "bleeding edge", trouble like this can often be avoided by tracking testing instead of sid.
Regards,
PB
Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
Ext4 corruption on Sid
Re: Ext4 corruption on Sid
AFAIK this does not only affect sid. The bug report mentions "much older stable kernels".
I just checked and Debian experimental is on 4.0.3 when I write this.
I tried to look for the commit but I don't know enough about kernel development to learn which kernels this patches. Or when the issue started.See upstream commit
d2dc317d564a46dfc683978a2e5a4f91434e9711 ("ext4: fix data corruption
caused by unwritten and delayed extents"), which has been added to
stable kernels 4.0.3 as well as much older stable kernels.
I just checked and Debian experimental is on 4.0.3 when I write this.
Two servers running Wheezy and Squeeze, two laptops (T61,G530) running Jessie and Squeeze.
Re: Ext4 corruption on Sid
There is an issue on RAID systems that does seem to be a regression from 4.0.1 to 4.0.2
http://news.softpedia.com/news/Linux-Ke ... 1699.shtml
See daumus's post near the top of this thread.
http://www.reddit.com/r/linux/comments/ ... s_an_ext4/
http://news.softpedia.com/news/Linux-Ke ... 1699.shtml
See daumus's post near the top of this thread.
http://www.reddit.com/r/linux/comments/ ... s_an_ext4/
Maybe there is more than one ext4 corruption bug?... The issue is still being investigated.
A patch for a different issue was applied to 4.0.3 and people are inappropriately associating it with this data corruption issue.
Re: Ext4 corruption on Sid
Fot latest on this, see
http://marc.info/?l=linux-raid&m=143219249318260&w=2
http://marc.info/?l=linux-raid&m=143219249318260&w=2
PB.Should there not be a big fat warning going around telling users to disable
discard on Raid 0 until this is fixed? This breaks the [ext4] filesystem completely
and I believe there is absolutly no way one can get back the data.