Looking at the Wikipedia article about Error Recovery Control, it
mentions[1] the FreeBSD handles this better.
Just what do they do and could it be done in Debian? Or is somebody
already working on something like this for the kernel?
"In a software RAID configuration whether or not TLER is hel
I understand that the mdadm maintainer chose[1] not to include a patch
for changing SCT values, but maybe md, lvm, btrfs and friends could be
patched to simply check the SCT values and emit warnings through syslog
or dmesg if they find SCT has not bee configured before a device is
assembled or mo
Hi,
I haven't seen the issue come up on the btrfs mailing list recently,
but in the year I've followed the list it has been fairly well
established that the default kernel SCT is too short for desktop-class
drives. I haven't personally run into issues, because my drives have
7sec SCT ERC, and the
There is now a report in the upstreadm issue tracker
https://www.smartmontools.org/ticket/658
Comments are welcome.
Control: Severity -1 important
>As long as one has not been hit by this bug it may not seem too
> severe,
> but that changes as soon as some common intermittent disk read/write
> error (possibly even unavoidable over time), that could be perfectly
> recoverable by the firmware with correct defaul
upstream without response, but it is still
a distro resposibility to ensure that installations will have safe
defaults. Note that the provided udev rules specific to mdadm are only
to be included in the mdadm package.)
This is at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780162#5
Look fo
Control: Severity 780207 serious
Control: Severity 780162 serious
I've thought about the serverity some more, and conclueded I'll do an
attempt setting severity back to serious:
The affected user base is very large (with regular non-raid drives).
An occasional read/or write error can happen anyt
Am Sun, 15 Mar 2015 23:57:44 +0100
schrieb Tobias Frost :
Thanks for responding.
> Control: Severity 780207 important
> Control: Severity 780162 wishlist
>
> Hi Chris,
>
> can you please let us know the link to the upstream discussion?
There are frequent reports and responds (like look at rece
Control: Severity 780207 important
Control: Severity 780162 wishlist
Hi Chris,
can you please let us know the link to the upstream discussion?
From your description, I don't see a imminent risk of data loss which warrants
a RC bug level. Therefore downgrading to important.
(CC'ing also the sma
9 matches
Mail list logo
