Re: thin provisioned LUN support & file system allocation policy

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



We have become confused and combined 2 independent issues...

UNMAP thin storage array provisioning is not SSD TRIM.

AFAIK the SSD trim will be handled just fine by sending the
small size (merged when appropriate) trim command.

The UNMAP is a big JBOD array problem and the solution(s)
are different.  As I said to one of Ric's early posts,
my opinion is

- expensive array vendors need to do this themselves
  because their whole thin provisioning thing is all
  about sharing on different host types with existing
  filesystems that use small blocks.

- linux filesystems that can do large allocation blocks
  would be able to be tuned at mkfs to the array geometry
  if the vendors give us the data... and we should only
  optimize those filesystems and forget about trying to
  fix it in the block layer or fix it with some kind of
  defrag/scanner.

jim

--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [SCSI Target Devel]     [Linux SCSI Target Infrastructure]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Samba]     [Device Mapper]
  Powered by Linux