I suggest you take a look at the EMC Education Site.  They have an online tutorial called "ATMOS Foundations" that talks about it a little bit.  It is fleshed out even further in EMC's training course "ATMOS Implementation and Management" which gets into great detail about the constructs of ATMOS.  To answer your questions more directly, no, the ATMOS nodes do not have a traditional ext3 filesystem on the drives used by the storage service.  If it did, ATMOS would still be limited by the number of inodes in a traditional filesystem, not by the number of addressable objects.  Think of it this way:  the object layer sits down on raw disk devices and the MAUI code in ATMOS reads/writes to those objects, does replication, compression, etc.  It can assemble groups of objects for presentation via NFS and CIFS for traditional-looking filesystem access, as well.  Does this answer your questions?  Karl
Hi,  I know that Atmos is a object-based storage, it that another abstraction layered on top a underlying storage construct, like file system or raw LUN?  As I know, Atmos DELL server node runs a OS called CAP which is built on Redhat Linux Kernel. Then I think there mus be a file system like ext3 running on the Linux. So user files should be stored on this file system, right?  Simply there is another abstraction provides mapping mechanism between a object and its real content on the file system. I'm not sure about this.  Could anyone share some lights on this?  thank you!
How to understand the storage of Atmos object?