This issue is not related to remaining/free space. It has something to do with drive's tracks/cylinders/heads/etc.
You can resize LUNs with <6G only up to 64G. LUNs with >6G up to 10x of its original size. Google for "netapp lun resize 10x".
> priv set diag > lun create -s 10m -t linux /vol/.../foo1 > lun geometry /vol/.../foo1 ... 10485760 device size (10 MB) 68718428160 max resize size (65535 MB)
> lun create -s 40g -t linux /vol/.../foo2 > lun geometry /vol/.../foo2 ... 42953867264 device size (40964 MB) 481028997120 max resize size (458745 MB)
Proper implementation should based on these rules either clone & resize or do a completely new LUN (create & copy?).
This issue is not related to remaining/free space. It has something to do with drive's tracks/ cylinders/ heads/etc.
You can resize LUNs with <6G only up to 64G. LUNs with >6G up to 10x of its original size. Google for "netapp lun resize 10x".
> priv set diag
> lun create -s 10m -t linux /vol/.../foo1
> lun geometry /vol/.../foo1
...
10485760 device size (10 MB)
68718428160 max resize size (65535 MB)
> lun create -s 40g -t linux /vol/.../foo2
> lun geometry /vol/.../foo2
...
42953867264 device size (40964 MB)
481028997120 max resize size (458745 MB)
Proper implementation should based on these rules either clone & resize or do a completely new LUN (create & copy?).