Hi The same issue was reported here http://www.spinics.net/lists/linux-ide/msg50641.html
Adding Adrian from Seagate to help track down this issue. On Tue, Aug 25, 2015 at 11:40 PM, Hannes Reinecke <h...@suse.de> wrote: > On 08/26/2015 06:53 AM, Anatol Pomozov wrote: >> Hi >> >> On Sun, Aug 23, 2015 at 11:15 PM, Hannes Reinecke <h...@suse.de> wrote: >>>> I looked at this commit and it actually adds SMR support to SCSI >>>> layer. Reverting ATA_DEV_ZAC means going back to zones-unaware >>>> algorithms. It is suboptimal but still much better than IO failures >>>> and "BTRFS: lost page write due to I/O error on /dev/sdc" errors I see >>>> at my computer. >>>> >>>> If this SMR support is considered as non-stable, can we at least get a >>>> kernel boot (or config) option that disables ZAC? >>>> >>> Again: Has anybody actually _tested_ that reverting this patch fixes >>> this issue? >> >> Yes I tested it. >> >> This error happens only under heavy load with a lot of read/writes >> (like btrfs rebalance). >> >> With current Linux-4.1.6 'btrfs balance' fails after ~10 minutes after >> start. I reverted ZAC related changes and then ran rebalancing. The >> operation finished successfully after 3 hours of running. >> > Can you be a bit more specific about the 'ZAC related changes'? > There have been several patches, and we really would need to know > which one was the offending one. I reverted these changes: 9162c6579bf90b3f5ddb7e3a6c6fa946c1b4cbeb f9ca5ab832e7ac5bc2b6fe0e82ad46d536f436f9 -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
