Re: asm versus ext3 filesystem on SAN

From: Stefan Koehler <>
Date: Fri, 26 Jun 2015 20:27:15 +0200 (CEST)
Message-ID: <>

Hi Sanjeev,
not quite sure about Pure Storage Flash Arrays, but why do you need to "relocate datafiles to free up space" in case of adding SAN storage to the clients? However in general for SAN devices you have two possibilities to extend the disk space / ASM / filesystem:
  1. Grow published LUN and resize it on client host (usually needs some manual steps in multipathing)
  2. Add new LUN to client host and expand accordingly

Both points can be done with ASM or EXT3 file systems (+LVM) - no need to relocate anything. EXT3 file systems can also be resized online and span over several LUNs with LVM.

Best Regards
Stefan Koehler

Freelance Oracle performance consultant and researcher Homepage:
Twitter: _at_OracleSK  

> msanjeevk <> hat am 26. Juni 2015 um 19:04 geschrieben:
> All,
> We have several custom databases (db size ranging from 40GB to 800GB ) on NAS as flat files and plan is to move them to SAN on Pure storage -
> concern here is whether to go with cooked filesystem(ext3) on SAN or configure them as ASM disks. If file system fills up we can add another
> filesystem on SAN but would have to take downtime to relocate datafiles to free up space as we are still on version 11gR2( - we are still
> not on 12c that has the online datafile move feature. ASM would provide flexibility with adding disks online.
> Would like to know if there are people in the group who are managing databases on SAN storage and how they are managing storage growth.
> Thanks,
> Sanjeev.

Received on Fri Jun 26 2015 - 20:27:15 CEST

Original text of this message