;
>> Remember that we have successfully issued READ CAPACITY(16) so we can
>> take the fast path on subsequent revalidate attempts.
>>
>> Reported-by: Menion
>> Signed-off-by: Martin K. Petersen
>> ---
>> drivers/scsi/sd.c | 2 ++
>> 1 file changed, 2 in
that read_capacity16 works and because of the storage size you
must use it, then I think the scsi layer shall go for it
2018-03-10 11:29 GMT+01:00 Christoph Hellwig :
> On Tue, Mar 06, 2018 at 09:40:56AM +0100, Menion wrote:
>> Hi all
>> Operating big capacity HDD such 8TB with comp
>> static int sd_try_rc16_first(struct scsi_device *sdp)
>> {
>> if (sdp->host->max_cmd_len < 16)
>> return 0;
>
>
> option
>
>> if (sdp->try_rc_10_first)
>> return 0;
>
>
> option
>
>> if (sdp->scsi_level > SCSI_SPC_2)
>> retu
neither, there are no dbg for kernel ppa in ubuntu :(
2018-03-08 12:10 GMT+01:00 Steffen Maier :
>
> On 03/08/2018 12:07 PM, Menion wrote:
>>
>> Unfortunately the Ubuntu kernel is not configured for ftrace or
>> kprobe, and I am operating this server so I am not sure if I
Unfortunately the Ubuntu kernel is not configured for ftrace or
kprobe, and I am operating this server so I am not sure if I will
eventually find the time and the risk to install a self-compiled
kernel
2018-03-08 11:53 GMT+01:00 Steffen Maier :
>
> On 03/08/2018 11:34 AM, Menion wrote:
&
0 GMT+01:00 Menion :
> Anyhow, I checked something that I should have checked since the beginning.
> I have stopped smartd and I still get this log, so it is something
> else doing it, but does anyone have an idea how understand what
> subsystem is calling again and again the read_capa
Menion :
> Hi
> I have tried it, but it does not work:
>
> [ 39.230095] sd 0:0:0:0: [sda] Very big device. Trying to use READ
> CAPACITY(16).
> [ 39.338032] sd 0:0:0:1: [sdb] Very big device. Trying to use READ
> CAPACITY(16).
> [ 39.618268] sd 0:0:0:2: [sdc] Very big de
CAPACITY(16).
[ 658.840440] sd 0:0:0:4: [sde] Very big device. Trying to use READ
CAPACITY(16).
smartd details (before I had the ver 6.5 of 2016)
menion@Menionubuntu:/lib/firmware/brcm$ smartd --version
smartd 6.7 (build date Mar 8 2018)
[x86_64-linux-4.15.5-041505-generic] (local build)
Copyright (C
2018-03-07 14:51 GMT+01:00 Steffen Maier :
>
> On 03/07/2018 09:24 AM, Menion wrote:
>>
> ...
>
> but from then on, you only get it roughly once every 300 seconds, i.e. 5
> minutes
>
> that's where I suspect user space as trigger, unless there is a kernel
> fe
nothing to do with this
capacity check, and I should have reported this here.
Bye
2018-03-07 3:45 GMT+01:00 Martin K. Petersen :
>
> Menion,
>
>> Operating big capacity HDD such 8TB with complex filesystems like
>> BTRFS in RAID mode endup in dmesg get flooded by this log, due
Hi all
Operating big capacity HDD such 8TB with complex filesystems like
BTRFS in RAID mode endup in dmesg get flooded by this log, due too
many capacity checks (opaque to the filesystem itself)
The logs come from here:
https://elixir.bootlin.com/linux/latest/source/drivers/scsi/sd.c#L2508
The ge
11 matches
Mail list logo
