Displaying 6 results from an estimated 6 matches for "max_hw_sectors_kb".
2017 Dec 19
0
kernel: blk_cloned_rq_check_limits: over max segments limit., Device Mapper Multipath, iBFT, iSCSI COMSTAR
...ging, at boot, I have disabled multipathd service
I wrote the below script to query /sys/block for block device information:
?
# cat bin/max_sectors_kb
#!/bin/bash
?
printf "%-18s: %-37s %-15s %-18s\n" $sysblk "Sys Block Node" "Device" "max_sectors_kb"
"max_hw_sectors_kb"
for b in `ls /sys/block/`
do
??????? sysblk=/sys/block/$b
??????? ls $sysblk/dm/name > /dev/null 2>&1
??????? if [ $? -ne 0 ]; then
??????????????? vendor=`cat $sysblk/device/vendor`
??????????????? model=`cat $sysblk/device/model`
??????????????? name="$vendor $model"
???...
2008 Nov 25
1
Correct way to change I/O scheduler in a iSCSI dev
Hi,
What's the correct way to change configuration parameters for an iSCSI
device? For example I/O scheduler, max_sectors_kb, etc...
I could add commands to the S99local script:
echo noop > /sys/block/sdb/queue/scheduler
echo 64 > /sys/block/sdb/queue/max_hw_sectors_kb
Unfortunately, iSCSI device names might change from sdb to, say, sdc
(server reboot, iSCSI target reconnection). If this happens, customizations
would be lost or applied to a different device.
Any workaround for this using centOS? sysctl, udev, anything else? It also
may be applied to Fiber Chann...
2011 Feb 17
7
Re: [Bugme-new] [Bug 29302] New: Null pointer dereference with large max_sectors_kb
...wiki.kernel.org before using
>
> fs created label (null) on /dev/sdb
> nodesize 4096 leafsize 4096 sectorsize 4096 size 2.73TB
> Btrfs Btrfs v0.19
> [140532]stg-bot ~ # mount /dev/sdb /mnt
> [140540]stg-bot ~ # umount /mnt
> [140543]stg-bot ~ # cat /sys/block/sdb/queue/max_hw_sectors_kb >
> /sys/block/sdb/queue/max_sectors_kb
> [140710]stg-bot ~ # mkfs.btrfs /dev/sdb
>
> WARNING! - Btrfs Btrfs v0.19 IS EXPERIMENTAL
> WARNING! - see http://btrfs.wiki.kernel.org before using
>
> fs created label (null) on /dev/sdb
> nodesize 4096 leafsize 4096 se...
2018 May 23
3
[PATCH] block drivers/block: Use octal not symbolic permissions
...ttr = {.name = "max_sectors_kb", .mode = S_IRUGO | S_IWUSR },
+ .attr = {.name = "max_sectors_kb", .mode = 0644 },
.show = queue_max_sectors_show,
.store = queue_max_sectors_store,
};
static struct queue_sysfs_entry queue_max_hw_sectors_entry = {
- .attr = {.name = "max_hw_sectors_kb", .mode = S_IRUGO },
+ .attr = {.name = "max_hw_sectors_kb", .mode = 0444 },
.show = queue_max_hw_sectors_show,
};
static struct queue_sysfs_entry queue_max_segments_entry = {
- .attr = {.name = "max_segments", .mode = S_IRUGO },
+ .attr = {.name = "max_segments&...
2018 May 23
3
[PATCH] block drivers/block: Use octal not symbolic permissions
...ttr = {.name = "max_sectors_kb", .mode = S_IRUGO | S_IWUSR },
+ .attr = {.name = "max_sectors_kb", .mode = 0644 },
.show = queue_max_sectors_show,
.store = queue_max_sectors_store,
};
static struct queue_sysfs_entry queue_max_hw_sectors_entry = {
- .attr = {.name = "max_hw_sectors_kb", .mode = S_IRUGO },
+ .attr = {.name = "max_hw_sectors_kb", .mode = 0444 },
.show = queue_max_hw_sectors_show,
};
static struct queue_sysfs_entry queue_max_segments_entry = {
- .attr = {.name = "max_segments", .mode = S_IRUGO },
+ .attr = {.name = "max_segments&...
2011 Aug 08
7
“bio too big” regression and silent data corruption in 3.0
tl;dr version: 3.0 produces “bio too big” dmesg entries and silently
corrupts data in “meta-raid1/data-single” configurations on disks with
different max_hw_sectors, where 2.6.38 worked fine.
tl;dr side-issue: on-line removal of partitions holding “single” data
attempts to create raid0 (rather than single) block groups. If it can''t
get enough room for raid0 over all remaining disks, it