On 02.10.2012 00:53, Chris Murphy wrote:
On Oct 1, 2012, at 3:33 PM, Pierre Beck wrote:
It's particularly annoying when in RAID and the disk could've simply been
kicked within few seconds. Something that needs improvement IMHO.
Except that while this helps with faster recovery, you'
Check the SMART values of the disks if possible. Watch for command
timeouts and the usual bad sector stuff. I've had similar issues with
Adaptec controllers. Bad disks seem to cause havoc. The outstanding
operation isn't answered within [SCSI Timeout, default 30,
/sys/block/sdX/device/timeout]
C? They won't know what hit them when their new PC crawls
because disk is trashed.
Greetings,
Pierre Beck
On 30.09.2012 20:52, H. Peter Anvin wrote:
On 09/30/2012 02:38 AM, Pierre Beck wrote:
Hi,
there seems to be a bug in either ext4 or VM code triggered with 16 GB
memory when compiled wit
Greetings,
Pierre Beck
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
access. A quick cure was to set dirty_bytes and
dirty_background_bytes to sane values, overriding the ratios. An
educated guess: the result of dirty_ratio calculation is stored as an
unsigned 32-bit integer and overflows?
Greetings,
Pierre Beck
--
To unsubscribe from this list: send the line
5 matches
Mail list logo
