Hello,
thanks for responding.
NeilBrown:
The upstream bug tracker is
mailto:linux-r...@vger.kernel.org
Well ok, though a regular mailinglist makes it rather hard to get an overview
for non-devs,
and reporting involves receiving unrelated messages.
This really needs to be fixed by
On Mon, 7 Jan 2013 13:34:05 +0100 (CET) bug556...@arcor.de wrote:
Hello,
thanks for responding.
NeilBrown:
The upstream bug tracker is
mailto:linux-r...@vger.kernel.org
Well ok, though a regular mailinglist makes it rather hard to get an overview
for non-devs,
and reporting
Alan Woodland:
If I've understood this correctly one possible workaround for this
(for the time being) would be to add a boot parameter that lets you
artificially limit max_hw_sectors? In this case it seems forcing all
md devices down from 248 to 240 would probably avoid potential data
loss
On Sun, 6 Jan 2013 12:31:46 +0100 (CET) bug556...@arcor.de wrote:
Alan Woodland:
If I've understood this correctly one possible workaround for this
(for the time being) would be to add a boot parameter that lets you
artificially limit max_hw_sectors? In this case it seems forcing all
md
4 matches
Mail list logo
