Hi,

I have a question regarding space reclamation on vmax thin devices. The command fstrim fails with

------

s54kr242-mobileblade:~ # mount /dev/mapper/VMAX_418_blkreplay /mnt/blkreplay_unmap/

s54kr242-mobileblade:~ # fstrim -v -v -v /mnt/blkreplay_unmap/

fstrim: /mnt/blkreplay_unmap/: FITRIM ioctl failed: Die Operation wird nicht unterstützt

s54kr242-mobileblade:~ # uname -a

Linux s54kr242-mobileblade 3.0.13-0.27-default #1 SMP Wed Feb 15 13:33:49 UTC 2012 (d73692b) x86_64 x86_64 x86_64 GNU/Linux

------

Filesystem is ext3 and the device is mounted at the stated mountpoint.

I'm able to use fstrim with another thin-device on a box from another vendor.

------

s54kr242-mobileblade:~ # mount /dev/mapper/blkreplay_DX200_100_0 /mnt/blkreplay_unmap/

s54kr242-mobileblade:~ # fstrim -v -v -v /mnt/blkreplay_unmap/

/mnt/blkreplay_unmap/: 264027430912 bytes was trimmed

-------

Parameters in /sys/class/scsi_disk//thin_provisioning and /sys/class/scsi_disk//provisioning_mode show the following output:

-------

VMAX:

s54kr242-mobileblade:~ # cat /sys/class/scsi_disk/3\:0\:6\:0/thin_provisioning

0

s54kr242-mobileblade:~ # cat /sys/class/scsi_disk/3\:0\:6\:0/provisioning_mode

full

------

Other Vendor:

s54kr242-mobileblade:~ # cat /sys/class/scsi_disk/4\:0\:0\:0/thin_provisioning

1

s54kr242-mobileblade:~ # cat /sys/class/scsi_disk/4\:0\:0\:0/provisioning_mode

unmap

----------------

Maybe someone here can shed some light on why the vmax-device is not correctly identified.

Kind regards for any help!!

Markus