Unsolved
This post is more than 5 years old
2 Posts
0
1377
February 11th, 2014 07:00
fstrim fails on vmax thin-device
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
sauravrohilla
859 Posts
0
February 11th, 2014 08:00
Some key information missing in your question. There are some requirements for reclaim in linux:
1) Linux with rhel 6.2 with hotfix BZ805519 and rhel 6.3 or later. RHEL requires ext4 fs. Suse 11 SP2
2) Symm 5876.163.105 or later
from: page 14
http://www.emc.com/collateral/software/white-papers/h6730-virtual-provisioning-space-reclamation-wp.pdf
regards,
Saurabh
hornma
2 Posts
0
February 17th, 2014 03:00
Hi Saurabh,
sorry for my late answer. Herre are the missing information:
1) Suse Enterprise Linux Server 11 SP3 (
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)
2) Symm
I've read the white-paper. But still to no success. EMC support is trying to build a SLES test-machine and tries to reproduce the behaviour.
Since there is know answer regarding one of my questions, I will repeat it here:
- Does anyone here have a machine that is actually able to use fstrim on a mount-point?
If that's the case then it would be awesome if this person could shed some light on the behaviour. It doesn't matter if it's Red Hat either as I have a recent CentOS 6.5 test-machine here.
Thanks for your time and help.
Kind regards,
Markus