On Mon, 2019-02-18 at 14:06 -0700, Chris Murphy wrote:
> No at worst what happens if SCSI command timer is reached before the
> drive's SCT ERC timeout, is the kernel assumes the device is not
> responding and does a link reset. That link reset obiterates the
> entire command queue on SATA drives.
> On Feb 22, 2019, at 11:00 AM, Omar Sandoval wrote:
>
> On Tue, Feb 19, 2019 at 09:18:20AM +1100, Dave Chinner wrote:
>> On Sat, Feb 16, 2019 at 06:57:45PM -0700, Andreas Dilger wrote:
>>> While it may be a bit of a stretch to call this "forensic evidence",
>>
>> We do forensic analysis of cor
Various sources (https://btrfs.wiki.kernel.org/index.php/Status,
https://wiki.debian.org/Btrfs) warn that "too many" snapshots,
possibly as few as 12, can degrade performance. OTOH, Marc Merlin's
talk identified snapshots as one of btrfs's killer features. And the
status page https://btrfs.wiki.k
Hi,
On 2/23/19 11:10 PM, Ross Boylan wrote:
> Various sources (https://btrfs.wiki.kernel.org/index.php/Status,
> https://wiki.debian.org/Btrfs) warn that "too many" snapshots,
> possibly as few as 12, can degrade performance. OTOH, Marc Merlin's
> talk identified snapshots as one of btrfs's kille
On Sat, Feb 23, 2019 at 11:14 AM Sébastien Luttringer wrote:
> What I don't get is how this could end up to silent sector corruption or let
> accumulate bad sectors. A read timeout, a link reset will end up with an error
> kick at minimum one drive from the array, forcing a full rebuild. No?
N
