(Sorry, accidentally dropped the lists. Adding it back & re-posting my
off-list response.)
On Thu, Mar 15, 2018 at 04:05:53PM +0100, Kashyap Chamarthy wrote:
> On Thu, Mar 15, 2018 at 03:33:46PM +0100, Douglas Gilbert wrote:
> > On 2018-03-15 02:44 PM, Douglas Gilbert wrote:
> > > On 2018-03-15
On Thu, Mar 15, 2018 at 08:45:05AM -0400, Martin K. Petersen wrote:
>
> Kashyap,
>
> > /me naively wonders if it has anything to do with accessing it via
> > Linux.
>
> I'm guessing that the drive doesn't actually support SCSI UNMAP. I have
> a T3 that reports all the right things in the
On 2018-03-15 01:45 PM, Martin K. Petersen wrote:
Kashyap,
/me naively wonders if it has anything to do with accessing it via
Linux.
I'm guessing that the drive doesn't actually support SCSI UNMAP. I have
a T3 that reports all the right things in the bl/lbpv VPD pages but also
has lbpme set
Kashyap,
> /me naively wonders if it has anything to do with accessing it via
> Linux.
I'm guessing that the drive doesn't actually support SCSI UNMAP. I have
a T3 that reports all the right things in the bl/lbpv VPD pages but also
has lbpme set to 0.
Interestingly enough, my T3 does appear to
On Thu, Mar 15, 2018 at 12:19:11PM +0100, Douglas Gilbert wrote:
> On 2018-03-15 10:47 AM, Kashyap Chamarthy wrote:
> > On Wed, Mar 14, 2018 at 11:43:55PM -0400, Martin K. Petersen wrote:
> > >
> > > Kashyap,
> >
> > Hi Martin,
> >
> > > > Sorry, I didn't give you complete information — with
On 2018-03-15 10:47 AM, Kashyap Chamarthy wrote:
On Wed, Mar 14, 2018 at 11:43:55PM -0400, Martin K. Petersen wrote:
Kashyap,
Hi Martin,
Sorry, I didn't give you complete information — with the previous
`dmesg` output, I actually attached the SSD (Samsung T5) via regular USB
"A Cable".
On Wed, Mar 14, 2018 at 11:43:55PM -0400, Martin K. Petersen wrote:
>
> Kashyap,
Hi Martin,
> > Sorry, I didn't give you complete information — with the previous
> > `dmesg` output, I actually attached the SSD (Samsung T5) via regular USB
> > "A Cable".
> >
> > Now, I re-attached the SSD via
Kashyap,
> Sorry, I didn't give you complete information — with the previous
> `dmesg` output, I actually attached the SSD (Samsung T5) via regular USB
> "A Cable".
>
> Now, I re-attached the SSD via the "Thunderbolt" port on my other laptop
> (Lenovo T470s), it _does_ show "UAS". Refer the
On Wed, Mar 14, 2018 at 12:29:50PM +0100, Oliver Neukum wrote:
> Am Mittwoch, den 14.03.2018, 11:22 +0100 schrieb Kashyap Chamarthy:
> > I see. So I ran `dmesg -w`, as I attached the disk & see the following:
>
> UAS and no quirk for your device. It looks like it indeed just does
> not support
Am Mittwoch, den 14.03.2018, 11:22 +0100 schrieb Kashyap Chamarthy:
> I see. So I ran `dmesg -w`, as I attached the disk & see the following:
UAS and no quirk for your device. It looks like it indeed just does
not support TRIM.
Sorry
Oliver
On Wed, Mar 14, 2018 at 10:52:36AM +0100, Oliver Neukum wrote:
> Am Dienstag, den 13.03.2018, 12:50 +0100 schrieb Kashyap Chamarthy:
> > Earlier, I didn't know which list to email, so I wrote to Martin K.
> > Petersen (who pointed me to the lists when I asked where I can post
> > publicly), and he
Am Dienstag, den 13.03.2018, 12:50 +0100 schrieb Kashyap Chamarthy:
> Earlier, I didn't know which list to email, so I wrote to Martin K.
> Petersen (who pointed me to the lists when I asked where I can post
> publicly), and he made this observation on the above quoted text:
>
> "Linux can
On Tue, Mar 13, 2018 at 12:42:47PM +0100, Kashyap Chamarthy wrote:
> [Cross-posted to 'linux-scsi' and 'linux-usb' lists; please keep me
> Cced, as I'm not subscribed to either of them.)
[...]
> I was suggested to return this SSD. But the Interweb[%] claims Samsung
> T5 *does* have 'TRIM' (i.e.
[Cross-posted to 'linux-scsi' and 'linux-usb' lists; please keep me
Cced, as I'm not subscribed to either of them.)
I unboxed a brand new Samsung T5 SSD[*]. Then formatted it with EXT4
filesystem. I wanted to clean the disk of any existing software, so I
was reminded by a colleague to use
14 matches
Mail list logo
