Recent content by ManfredCC

Seems to be a problem at Thecus' side. They can reproduce it (testing it with Ubuntu) in their labs and they are working on a solution.

I'll give it a try. I've installed ubuntu to check the max_sectors_kb and it shows 8192 too. Proxmox switched to ubuntu kernel and therefore it is clear :-(

PS: running dd doesn't change max_sectors_kb. Funny enough...dd resets the max_sectors_kb again to 8192

Doesn't change anything. The only thing which helps is to change max_sector_kb to 512.

No answer from Thecus up to now... Clean installation of debian 8.2 (64) uses max_sectors_kb = 512 as standard setting. Means iscsi is working without errors... I will try udev-rules from your posting (tried to define udev rule to set max_sectors_kb to 512, but with no success)...

Buffer I/O error on dev sdb1, logical block xxxxxxxx . . . blk_update_request: I/O error,dev sdb1, sector xxxxxxx . . . . xxxxxx = different blocks, sectors ...and the file is corrupted... as mentioned before - this happens only when max_sectors_kb is 8192 (working only with lower numbers -...

Hiho, since the update to 4.1 (and previous 4.0) the setting for max_sectors_kb is 8192. In <=3.4 it was 512. When connecting to my SAN and using it i get continuous error messages. Setting this value to 512 (/sys/block/sdx/queue/max_sectors_kb) solves the problem and everything is ok. But this...