Re: [PATCH] scsi: sd: Remember that READ CAPACITY(16) succeeded

2018-03-22 Thread Menion
D CAPACITY(16). >> >> Remember that we have successfully issued READ CAPACITY(16) so we can >> take the fast path on subsequent revalidate attempts. >> >> Reported-by: Menion <men...@gmail.com> >> Signed-off-by: Martin K. Petersen <martin.peter...@oracl

Re: dmesg flooded with "Very big device. Trying to use READ CAPACITY(16)"

2018-03-10 Thread Menion
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 <h...@infradead.org>: > On Tue, Mar 06, 2018 at 09:40:56AM +0100, Menion wrote: >> Hi all >> Operating big

Re: dmesg flooded with "Very big device. Trying to use READ CAPACITY(16)"

2018-03-09 Thread Menion
>> 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) >>

Re: dmesg flooded with "Very big device. Trying to use READ CAPACITY(16)"

2018-03-08 Thread Menion
neither, there are no dbg for kernel ppa in ubuntu :( 2018-03-08 12:10 GMT+01:00 Steffen Maier <ma...@linux.vnet.ibm.com>: > > On 03/08/2018 12:07 PM, Menion wrote: >> >> Unfortunately the Ubuntu kernel is not configured for ftrace or >> kprobe, and I am operatin

Re: dmesg flooded with "Very big device. Trying to use READ CAPACITY(16)"

2018-03-08 Thread Menion
018 11:34 AM, Menion wrote: >> >> I did some more test >> This log is specific from the function sd_read_capacitysd_revalidate_disk >> From what I can see, it seems that it is called only when probing >> newly attached devices >> A quick look in the cod

Re: dmesg flooded with "Very big device. Trying to use READ CAPACITY(16)"

2018-03-08 Thread Menion
Menion <men...@gmail.com>: > 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

Re: dmesg flooded with "Very big device. Trying to use READ CAPACITY(16)"

2018-03-08 Thread Menion
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

Re: dmesg flooded with "Very big device. Trying to use READ CAPACITY(16)"

2018-03-07 Thread Menion
2018-03-07 14:51 GMT+01:00 Steffen Maier <ma...@linux.vnet.ibm.com>: > > 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, un

Re: dmesg flooded with "Very big device. Trying to use READ CAPACITY(16)"

2018-03-07 Thread Menion
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 <martin.peter...@oracle.com>: > > Menion, > >> Operating big capacity HDD such 8TB with complex filesystems like >> BTRFS in RAID mode

dmesg flooded with "Very big device. Trying to use READ CAPACITY(16)"

2018-03-06 Thread Menion
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