public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "hch@infradead.org" <hch@infradead.org>,
	"viswas.g@microsemi.com" <viswas.g@microsemi.com>,
	"gerry.morong@microsemi.com" <gerry.morong@microsemi.com>,
	"mahesh.rajashekhara@microsemi.com"
	<mahesh.rajashekhara@microsemi.com>,
	"POSWALD@suse.com" <POSWALD@suse.com>,
	"scott.benesh@microsemi.com" <scott.benesh@microsemi.com>,
	"don.brace@microsemi.com" <don.brace@microsemi.com>,
	"bader.alisaleh@microsemi.com" <bader.alisaleh@microsemi.com>,
	"kevin.barnett@microsemi.com" <kevin.barnett@microsemi.com>,
	"joseph.szczypek@hpe.com" <joseph.szczypek@hpe.com>,
	"scott.teel@microsemi.com" <scott.teel@microsemi.com>,
	"jejb@linux.vnet.ibm.com" <jejb@linux.vnet.ibm.com>,
	"justin.lindley@microsemi.com" <justin.lindley@microsemi.com>,
	"John.Hall@microsemi.com" <John.Hall@microsemi.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] sd: preserve sysfs updates to max_sectors_kb
Date: Mon, 21 Aug 2017 19:53:13 +0000	[thread overview]
Message-ID: <1503345191.2571.13.camel@wdc.com> (raw)
In-Reply-To: <4993A297653ECB4581FA5C3C31323D195B8DBDE4@avsrvexchmbx2.microsemi.net>

On Mon, 2017-08-21 at 19:12 +0000, Don Brace wrote:
> On Friday Bart Van Assche wrote:
> > Can you check on your test system which udev rule changes
> > max_sectors_kb? I
> > have checked two recent Linux distro's but haven't been able to find
> > such a udev rule:
> > $ grep -rw max_sectors_kb /usr/lib/udev/rules.d /etc/udev/rules.d | wc
> > -l
> > 0
> > 
> > Thanks,
> > 
> > Bart.
> 
> On my system it is 60-block.rules, and it is the last rule in that rule
> file.
> --
> # do not edit this file, it will be overwritten on update
> 
> # enable in-kernel media-presence polling
> ACTION=="add", SUBSYSTEM=="module", KERNEL=="block",
> ATTR{parameters/events_dfl_poll_msecs}=="0", \
>   ATTR{parameters/events_dfl_poll_msecs}="2000"
> 
> # forward scsi device event to corresponding block device
> ACTION=="change", SUBSYSTEM=="scsi", ENV{DEVTYPE}=="scsi_device",
> TEST=="block", ATTR{block/*/uevent}="change"
> 
> # watch metadata changes, caused by tools closing the device node which
> was opened for writing
> ACTION!="remove", SUBSYSTEM=="block",
> KERNEL=="loop*|nvme*|sd*|vd*|xvd*|pmem*", OPTIONS+="watch"

Hello Don,

Can you have another look at the udev rules on your test system? The last
rule in 60-block.rules looks like a watch rule to me. The same holds for the
upstream version of that file (https://github.com/systemd/systemd/blob/maste
r/rules/60-block.rules).

Bart.

  reply	other threads:[~2017-08-21 19:54 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-18 21:00 [PATCH] sd: preserve sysfs updates to max_sectors_kb Don Brace
2017-08-18 21:05 ` Bart Van Assche
2017-08-18 21:29   ` Don Brace
2017-08-18 21:46     ` Bart Van Assche
2017-08-21 19:12       ` Don Brace
2017-08-21 19:53         ` Bart Van Assche [this message]
2017-08-21 20:14           ` Don Brace
2017-08-29 17:41             ` Don Brace
2017-08-29 17:42             ` Don Brace
2017-08-29 18:13               ` Bart Van Assche
2017-08-29 18:36                 ` Don Brace
2017-08-29 19:41                   ` Don Brace
2017-08-29 22:25                     ` Bart Van Assche
2017-08-29 22:32                       ` Don Brace
2017-08-29 23:00                         ` Bart Van Assche
2017-08-30  1:24                           ` Martin K. Petersen
2017-09-09 10:32                             ` Martin Wilck
2017-09-28  1:37                               ` Martin K. Petersen
2017-09-28  1:38 ` [PATCH] scsi: sd: Do not override max_sectors_kb sysfs setting Martin K. Petersen
2017-09-29 12:26   ` Martin Wilck
2017-09-29 13:46   ` Don Brace

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1503345191.2571.13.camel@wdc.com \
    --to=bart.vanassche@wdc.com \
    --cc=John.Hall@microsemi.com \
    --cc=POSWALD@suse.com \
    --cc=bader.alisaleh@microsemi.com \
    --cc=don.brace@microsemi.com \
    --cc=gerry.morong@microsemi.com \
    --cc=hch@infradead.org \
    --cc=jejb@linux.vnet.ibm.com \
    --cc=joseph.szczypek@hpe.com \
    --cc=justin.lindley@microsemi.com \
    --cc=kevin.barnett@microsemi.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mahesh.rajashekhara@microsemi.com \
    --cc=scott.benesh@microsemi.com \
    --cc=scott.teel@microsemi.com \
    --cc=viswas.g@microsemi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox